File to Idoc Scenario

Hello Gurus,

I am doing File to IDoc scenario, i got struck up with

the below error in SXMB_MONI

Could any suggest me what went wrong.

xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

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

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

<SAP:P1>MSGGUID 93F76F40F67711DC8752001A64268DE4: Tag HEADER found instead of tag IDOC BEGIN=</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: MSGGUID 93F76F40F67711DC8752001A64268DE4: Tag HEADER found instead of tag IDOC BEGIN=</SAP:Stack>

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

</SAP:Error>

Kind Regards,

Vijay

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (8)

Hi,

Thanks to everyone who has shared their valuable suggestions towards this thread.

I have solved this bug, the file which i have received has different namespace.when we added the namespace of receiving interface in the xml schema it solved my problem.

Thanks one and All.

Regards,

Vijay

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Are you using any conditions to generate the IDOC in you mapping. If yes then check those conditions by taking the message from payload and test your mapping.

Regards,

Sarvesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Have u edited the idoc recently. I think a proper copy is not imported. The problem could also be related to improper mapping of the Begin field

Regards,

Prateek

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Check the link..

Regards,

Phani

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Check the file which ur sending at the source and the mapping which you are doing. Check the xml struture at the source and the header field if any mapped to the Idoc structure..

Regards,

Nithiyanandam

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Import the IDOC meta data in IDX2

Check the same Problem

Regards

Seshagiri

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

In XI system, create a RFC destination and a port in transaction IDX1.

In IDX2, import the IDoc's metadata using port created in IDX1.

IDocs metadata is needed for IDoc adapter to convert IDoc into IDoc -xml format

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Could u please check out with the Communication channel montioring of the receiver adapter.. what is the error u got there

and also check whether have u configured the IDOC receiver with the required parameters, check once...

regards,

Kishore

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Kishore,

I see all my communication channels, except the receiver idoc communication channel...

Could you let me know wht could be the prob..?

Regards,

Vijay

Some misunderstanding!

Idoc and http adapter resides on ABAP stack and therefore cannot be monitored using RWB - Communication channel monitoring

Regards,

Prateek

Hi,

Thanks for all your inputs...i checked all the setting once again

and i dont see any error.as you have referred..

Can anyone tell me how to fix this

xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

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

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

<SAP:P1>MSGGUID BD701030F68A11DCA41B001A64268DE4: Tag HEADER found instead of tag IDOC BEGIN=</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: MSGGUID BD701030F68A11DCA41B001A64268DE4: Tag HEADER found instead of tag IDOC BEGIN=</SAP:Stack>

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

</SAP:Error>

Kind Regards,

Vijay

Hi,

According to this error, I think you have modified the idoc . here it is saying that IDOC segment is not present in the IDOC. Check that once

Try to Delete that idoc from the XI and complety .then re-import again

Regards

Seshagiri

Hi,

Thanks for your input , i tryed by deleting and reloading the same but i am getting the same errror.

Kind Regards,

Vijay

Are you getting an output payload ?

if not check your mapping......

Dear All,

Can anyone help on this... still i am getting the same error

i have tested mapping .. there are no errors ..

- <!-- 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_RUNTIME</SAP:Code>

<SAP:P1>MSGGUID EF35A760F7E311DC9612001A64268DE4: Tag HEADER found instead of tag IDOC BEGIN=</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: MSGGUID EF35A760F7E311DC9612001A64268DE4: Tag HEADER found instead of tag IDOC BEGIN=</SAP:Stack>

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

</SAP:Error>

Regards,

Vijay

Hi Vijay,

check the pay load after mapping it is not forming the xml what it is needed to from the IDOC.

there will be no mapping error but the out put payload will be null... since the error is Tag HEADER found instead of tag IDOC BEGIN

cheers,

Sunil.

Ask a Question

Top Q&A Solution Author

User

Count