on 08-30-2015 4:48 AM
Hi Experts,
I have configured an IDOC to EDI scenario, where we have used EANCOM as our target structure. When we trigger an IDOC from ECC some messages are getting failed in our PI with the below error
"MP: exception caught with cause java.lang.RuntimeException: Can not find Segment Elements for messageVersion 01B, message subversion 000000, message agency UN, segment S_UNB, newFirstlevelElement C_S001, currentIndexLevel1 0 "
PFB screenshot
We have maintained all the modules properly in the receiver communication channel.
PFB screenshot
But when we resend the same file explicitly or When the adapter retries again by itself, the file is reaching the destination automatically.
PFB screenshot
When we trigger a new IDOC, it is reaching the destination without any error.
We have properly configured the B2BIC and all the subversion's are available for EANCOM.
Need your guidance here.
Regards,
Ragulan
Hi Raghu,
Can you answer the below questions.
Have you imported the B2B content for both EANCOM and Edifact ?
What is the message type of the message ?
Thanks,
Appala
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have a similar error and opened a ticket at SAP. Keep you posted on progression.
Kind regards,
Dimitri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dimitri,
Is there any Updates from SAP ? even i have received the same error.
Error :
MP: exception caught with cause java.lang.RuntimeException: Can not get
Segment Elements for messageVersion TEMP, message subversion 000000,
message agency UN, segment S_UNB, newFirstlevelElement C_S001,
currentIndexLevel1 0: Failed to set the parameter 1 of the statement
>>SELECT IDX,COMP FROM B2B_EDI_CTRL_SEG WHERE (MESSAGEVERSION = ?)
AND (SEGMENT = ?) AND (MESSAGESUBVERSION = ?) AND (MESSAGEAGENCY = ?)
AND (CTRL_KEY = ?)<<: Cannot assign a
>>java.lang.String<< object of length 4 to a parameter with JDBC type >>VARCHAR(3)<<.
Regards,
Hitesh R,
Hi,
In fact, yes...
My control key associations were all built using .*
But I need to mention the sender.receiver party and/or component, namespace and interface.
I did that and it works now.
So, please make sure to add up details onto your control key associations.
Concerning your latest post, please do have a look at the data. Seems like you have another error too.
Kind regards,
Dimitri
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.