| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| NNIDoc -p <Configuaration File> error |
« View previous topic :: View next topic » |
| Author |
Message
|
| ryzor |
 Posted: Tue Oct 05, 2004 11:59 pm Post subject: NNIDoc -p <Configuaration File> error |
 |
|
Apprentice
Joined: 31 Dec 2001
Posts: 42
|
Hi Guys,
I use the following: NNIDoc -p RDCHEQUES.cfg command to load idocs created in WMQI2.1 into SAP - but my idocs goes to the failure queue which is specified in the config file - when i check the rdcheques.log i get the message: Error: IDoc based runtime exception thrown.
Wed Oct 6 09:31:07 2004
IDoc Message: CIDocDataSegment constructor(string):
does not form name or type of a segment
.....
i feel like the above message is really NOT descriptive - are there further steps that i can take to increase debugging,
here is the configuaration file i use.
# ------------------------------------------------------------
# NEON Link for SAP R/3 Inbound IDoc Processing
# configuration file.
# ------------------------------------------------------------
# Indicate that the NEONlink for R/3 should run in server mode
# To process outbound from R/3 IDocs, set to outbound
# To process inbound to R/3 IDocs, set to inbound
NN.LinkMode = inbound
# Specify method used to submit IDocs to R/3...set
# equal to 3 if connecting to a 3.x R/3 system or
# 4 for a 4.x R/3 system.
NN.InboundMethod = 4
# To batch IDocs in the link before submitting to SAP
# R/3, set the maximum batch size greater than 1.
# To send each MQSeries message as a single IDoc into
# SAP, leave this value set to 1.
NN.IDocBatchSize = 1
# Generate a report of every IDoc received...
NN.CreateIDocReport = false
# Trace IDoc processing
NN.IDocTrace = true
# Logging information
NN.LogFileName = rdreverse.log
NN.VerboseLog = true
# Specify the MQSeries queue manager name
MQS.QueueManagerName = POMQI101.ZA.QMGR
# Specify a queue to get IDocs from
MQS.GetQueueName = R3LINK.RDCHEQUESREV.INBOUND
# Specify a queue to put failed IDocs to.
MQS.ErrorQueueName = R3LINK.RDCHEQUESREV.FAILURE
# Maximum number of times to retry a message that
# has been rolled back to the get queue.
MQS.MaxBackoutCount = 1
# RFC destination; the value is cross-referenced
# with destinations listed in the saprfc.ini file
# Maximum number of times to retry a message that
# has been rolled back to the get queue.
MQS.MaxBackoutCount = 1
# RFC destination; the value is cross-referenced
# with destinations listed in the saprfc.ini file
RFC.Destination = NNIDOC_INBOUND
# SAP R/3 client code
RFC.ClientCode =
# SAP R/3 user name
RFC.UserName =
# SAP R/3 password
RFC.Password =
# SAP R/3 Language
RFC.Language = E
# Enable RFC tracing?
RFC.Trace = true
any guidence will be highly appreciated.
thanx - ryzor. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 06, 2004 5:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
IDoc Message: CIDocDataSegment constructor(string):
does not form name or type of a segment |
What this error message is trying to tell you is that you have a "malformed" IDOC. Your Idoc is probably getting checked either against the SAP definition or a definition you stored. As such the Idoc contains a segment that is not recognized.
Segments are being recognized by name, position, parent, hierarchy level etc... (check first 63 bytes EDI_DD40). Your segment identification does not correspond to anything that has been defined for this IDOC type. The name of the segment in the constructor method (String name) is not being recognized
Enjoy  |
|
| Back to top |
|
|
| ryzor |
| Posted: Wed Oct 06, 2004 10:59 pm Post subject: |
|
|
Apprentice
Joined: 31 Dec 2001
Posts: 42
|
Thanx fjb_saper for the quick reply,
i managed to get the right name in the right position ... but now i'm gettting the following error:
IDoc Number: 0000000000000001
IDoc Type: ORDERS04
IDoc Release: 45B
IDoc Segment Type: E1EDK01
IDoc Message: No such segment type found in metadata table
does this mean the idoc definition is not present in the SAP system?. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 07, 2004 12:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
ORDERS04 basic version does have segment E1EDK01.
Does your segment definition in EDI_DD40 match following: sorry not in list order
segment E1EDK01
mandatory yes
segno 1
parent none
hierarchy level 1
This is what my sap system tells me...
Make sure the mw you are using has downloaded the definition from SAP.
Make sure the IDOC name and all other attributes specified in EDI_DC40 match an existing IDOC in SAP. Make sure as well that the destination and source config as well as processing config on EDI_DC40 match a partner setup (WE20 in SAP) and match the IDOC TYPE + extended type.
Enjoy |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
