cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Posting IDoc

arunneerolil
Contributor
0 Kudos

Hi All,

I am getting the following error while posting an IDoc from XI to R3 in (SXMB_MONI).

<?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">ATTRIBUTE_IDOC_METADATA</SAP:Code>

<SAP:P1>Basic type ORDERS02 does not exist</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: Basic type ORDERS02 does not exist</SAP:Stack>

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

</SAP:Error>

Where I should define ORDER02 basic type ?

Can anyone help.

Thanks in Advance

Chemmanz

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Chemmanz,

You define your basic type in your partner profile settings, and i think doing the same will solve your problem. Please go thru the following links to get a better idea about partner profile:

http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm

I hope this helps you solve your problem.

Regards,

abhy

PS: AWARD POINTS FOR HELPFUL ANSWERS.

bhavesh_kantilal
Active Contributor
0 Kudos

Hi Chemmanz,

When you get an error like <b>ATTRIBUTE_IDOC_METADATA</b>, what it means is that while posting the IDOC, the destination Message Type does not match with the IDOC that is expected to be sent from XI.

XI expects, <IDOC>--<ORDERS02> to be the beginning of your Destination Message ( after mapping execution ), but, I dont think that is being generated by your mapping and hence the error.

I would suggest that your check the mapping and the target message generated with the structure expected by your IDOC.

Regards,

Bhavesh

arunneerolil
Contributor
0 Kudos

Hi Bhavesh,

The IDoc coming out of XI looks like

<?xml version="1.0" encoding="UTF-8" ?>

- <ORDERS02>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>900</MANDT>

<DOCNUM>EDIDOC01</DOCNUM>

<STATUS>03</STATUS>

..

So it in the correct format.

Also it is working fine in development system.

Now we are in quality.

Regards

Arun

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

try looking at TCODE IDX2

if the XI imported orders02 metadata

Regards,

michal

bhavesh_kantilal
Active Contributor
0 Kudos

Hi Chemmanz,

Think Michal has hit the bulls eye here..

Regards,

Bhavesh

arunneerolil
Contributor
0 Kudos

Hi Michal,

In IDX2 i couldn't find ORDER02 basic type.

But it is available in the S/W design Object in integration repository.

Thanks & Regards,

Chemmanz

MichalKrawczyk
Active Contributor
0 Kudos

So import it into IDX2

create - then choose port from IDX1 and orders02

and you're done:)

Regards,

michal

Former Member
0 Kudos

Hi -

If it's not cached in IDX2, it should have retrieved it at runtime. Since it seemed to fail to import it into IDX2 at runtime, you'll probably run into an error when you manually try to do it in IDX2. If so, check that the user you are using in the corresponding SM59 destination has the proper authorization in the metadata source system. You can probably compare it to your DEV environment.

Incidentally, that's why it's good practice to try to manually import the metadata once in IDX2 prior to the first end-to-end execution.

Regards,

Jin