cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to interpret IDoc interface ZSHIPDEL_packageRD

Former Member
0 Kudos

Hi,

I am doing a file-xi-idoc scenerio.

I've exported my custom idoc as an xsd and modified the schema to allow for multiple idocs to be generated for each file - as per note 814393.

However I get the following error message at runtime (Call Adapter):

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>

<SAP:P1>ZSHIPDEL_packageRD</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to interpret IDoc interface ZSHIPDEL_packageRD</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

Has anyone else experienced this error?

Regards

leenor

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I have found how to solve this problem:

In the Integration Directory/Interface determination, you must use the real Idoc definitition rather than your interface pointing to the modified XSD. It doesn't prevent you from using the mapping that generates multiple Idoc.

Former Member
0 Kudos

I have a scenario exactly like the above one.

My file structure is like

TransactionDetailList

TransactionDetail (1:N)

Transaction_Type (0:1)

Transaction_Date (0:1)

Add_Revise_Cancel_USER_ID (0:1)

Add_Revise_Cancel_Date_Time (0:1)

My IDOC has the below structure,

ZIDOC_BDS_DIVERSION

IDOC

ZSEGL_DIVERSION_HEADER

SEGMENT

NOMNR

NOMIT

EVENT_DATE

ZSEGL_ DIVERSION_ITEM

SEGMENT

WHO_PAYS_DIVERSI

LOCID

DEST_CITY

so i have to generate multiple idocs in the target side.

I have created external defination based on my IDOC.Defined mapping between File and the external defination crerated from the IDOC. also defiined interface mapping between file and external defination.

In the Integration Directory ->Interface Defination, I have used the actual Idoc as Inbound interface for which there is no mapping as we have not defined anything for this. This is exactly what you have defined above.

I am getting the following errors like,

"Error: MSGGUID A5EE4A305B4111DABFBE0002551F08EE: Tag TransactionDetailList found instead of tag IDOC BEGIN="

Please let me know if I am missing some steps while configuring or I have to do something else.

Thanks & Regards,

Mukesh

Former Member
0 Kudos

Hi Ieenor

How did you solve this? I got the same problem.

Thanks

Gregory

Former Member
0 Kudos

Did you create your own message interface ? If yes, you should not. Because for IDoc interface you should use the default IDoc structure only (no need to define any objects in the integration builder other than importing).

regards

SKM

Former Member
0 Kudos

It works fine if I want to use the unmodified idoc schema.

But when I use the modified schema as recommended in note 814393, I get the error.

To be clear the file contains multiple delivery documents were as the IDOC can only handle 1. So instead of using BPM to split the message, I am trying to get the IDOC adapter to generate multiple IDOCs by modifing the imported IDOC schema.

Please refer to the note 814393 for details.

rg

leenor

Former Member
0 Kudos

At this point all I can suggest is to redo the OSS note and check your mapping.

regards

SKM

Former Member
0 Kudos

thanks, but I've managed to solve it