cancel
Showing results for 
Search instead for 
Did you mean: 

What does this error mean in idoc_apapter

Former Member
0 Kudos

Hi,

Im getting this error while doing a flat file to an idoc scenario.

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

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

Can anyone explain me what to do.

Thanks in advance,

Bhargav

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hello Bhargav,

You should not create any message interfaces refering to IDoc.Infact Idoc acts both like Message type and Messge interface.

In interface determination choose ALL radio button and choose Idoc itself instead of interface.Ty doing the configuration in directory without the Message Interface and Message Type for IDOC just base on IDOC .

Hope This is useful

With Regards,

Raju.

Former Member
0 Kudos

Hi,

i am replying based on what understand from previous replies....

why u have used external definitons?

or..

u need to import the idoc in imported objects..

u can use this structure in mapping

no need of creating interface for IDocs....

even in interface mapping u can directly select the idoc...

Regards,

Chaitanya.

Former Member
0 Kudos

I have created an external definition(imported the xsd) of the Idoc and created an Message Interface for the Idoc using this External definition.I have checked everything is correct.

prabhu_s2
Active Contributor
0 Kudos

no need to creatiing a MI for the idocs. u can directly use it in mapping part. check this

prabhu_s2
Active Contributor
0 Kudos

u can also refer this blog:

/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change

Former Member
0 Kudos

If i dont create a MI for idoc than how can i do interface mapping.Can u please explain in detail as im a newbie to this

prabhu_s2
Active Contributor
0 Kudos

refer to the link posted above. for idoc u dont req to create MI. U can diretly use it in mapping

Former Member
0 Kudos

Hi,

here are some useful links based on IDoc..Go through this....

IDOC - File scenario

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

configuring IDOCS

/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii

IDOC scenarios

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb...

Idoc related setting

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c...

For troubleshooting of IDOC-File check this blog:

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

regards,

vasanth

former_member184619
Active Contributor
0 Kudos

Hi Bhargav,

Follow thse seteps

1. If you are having a custom iDOC or standard IDOC in R/3. Just import it into IR under Imported IDOC under namepsace

2. No need to create External defination until unless there is some Occurance change for IDOC or something else.

3. You can use this IDOC directly in Message Mapping, Interface Mapping .. No nedd to Create MI

Check my posting in WIKI for File to IDOC where you can find how u can use it without interface mapping

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&

Regards

Sachin

prabhu_s2
Active Contributor
0 Kudos

have u created a MI WRT to Idocs?

santhosh_kumarv
Active Contributor
0 Kudos

Hi,

1.Have u loaded the metadata for IDOC in IDX5.

2.Check the Interface Determination and Message Interface(Inbound) pointing to the IDOC.

Regards

Santhosh

Former Member
0 Kudos

Santosh,

>>>"1.Have u loaded the metadata for IDOC in IDX5."

not IDX5,its IDX2

IDX5 is for monitoring of IDOCS

IDX2 metadata maintenance.

but its not mandatory to maintain metadata in IDX5,once you trigger Idoc it will load automatically.

Former Member
0 Kudos

Babu,

yes ... but if the Idoc was changed in R/3 and allready maintained in IDX2 then you have to import the new structure again.

You should also be sure that all IDoc changes are activated in the IDoc development.

Regards,

Gordon

Former Member
0 Kudos

just delete the metadata of the idoc in IDX2,

try to trigger once again