on 01-19-2006 6:41 AM
Hi ,
I have a scenario where I am doing message splitting of source file to multiple idocs.I am also doing content conversion on the source channel.
I am NOT using a BPM, but am using PACKAGING to do the splitting.
Is there any configuration I need to do in the IDOC side?or in Interface determination?
During end-to-end testing, I get the following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER"><b>ATTRIBUTE_WRONG_INTF</b></SAP:Code>
<SAP:P1>MI_ZSDCONTRACT01_IN</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:<b>Stack>Unable to interpret IDoc interface MI_ZSDCONTRACT01_IN</b></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help!
regards,
Jithesh
hi Jitesh,
<SAP:Stack>Unable to interpret IDoc interface MI_ZSDCONTRACT01_IN</SAP:Stack>
We once got this same error.
It can be because the Message interface of your repository does not refer an IDOC.
The message type for the message interface should be that of an Idoc.
Hope that helps.
Regards,
Jesse.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jitesh
Pbm is that the Message interface name for your external definition is different from the IDOC message name..
Change the name of MI to that of IDOC as ZSDCONTRACT01 and assign the messagetype(multiple occurence) ZSDCONTRACT01 as the Inbound message type..Now check the interface determination..You should see your Interface mapping!!
Lemme know if this solves ur pbm!!
Regards
Sriram V.
Hi Sriram,
Yup..It works!
regards,
Jithesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah... Sounds like you have created a message interface using an IDoc as message type... You don't have to!
You just have to use the IDoc (in the imported objects ns) both as message type (for message mapping) and as message interface (for interface mapping), otherwise R/3 will not recognize it as MI_someIDoc, but just as someIDoc
Is that clear?
Hope I helped you.
Alex
Hi Alex,
The problem is ., when I use packaging, I need to use a modified version of the IDOC schema, and this is what U se in mapping. So I am using my modified schema in my message mapping, and the IDOC in int.determination.the inbound interface is my IDOC, and in Interface mapping(which I have done using my modified schema, I do not get to see it on the list(no objects found)
regards,
Jithesh
Could u suggest me on what i can do?
Jithesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah... Sounds like you have created a message interface using an IDoc as message type... You don't have to!
You just have to use the IDoc (in the imported objects ns) both as message type (for message mapping) and as message interface (for interface mapping), otherwise R/3 will not recognize it as <i>MI_someIDoc</i>, but just as <i>someIDoc</i>
Is that clear?
Hope I helped you.
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
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.