IDOC Runtime Error

[justin_santhanam]

Hi All,

I have the below issue while posting the IDOC, I would appreciate if anyone has solutions for it. I personally implemented this before, but now I forgot how I did...

The source is file and target is IDOC. I changed the occurrences of IDOC to 0..1 . If my condition doesn't satisfy then I should not create IDOC and send data to ECC...

when I look my output of the mapping it has

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

<MATMAS05 />

but I got the following error

ATTRIBUTE_IDOC_RUNTIME
MSGGUID 4A06070F2D4600D7E10080000AF0606B: Tag found instead of tag IDOC BEGIN= 

Thanks,

Raj.

[Former Member · Accepted solution]

Hi Raj,

Did you change the structure of IDOC recently?

have a look at it?

It could be issue with the IDOC meta data or incoming file structure.

Check if you can see the source payload from incoming File properly.

do let us know about the solution, if you solve it youself.

Check your RFC destination, IDX1 and IDX2.

Thanks,

Venkat.

Edited by: Venkat Anusuri on May 11, 2009 3:50 PM

[justin_santhanam · Accepted solution]

Venkat,

I appreciate your help!

I found the issue, this was something to do with Interface mapping. I changed the occurrenc in message mapping but forgot to do the same for Interface mapping as well.

Now I have the following error.

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category> 
  <SAP:Code area="MAPPING">GENERIC</SAP:Code> 
  <SAP:P1>Split mapping created no messages</SAP:P1> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Split mapping created no messages</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

Which is perfectly correct. It is showing errored flag in SXMB_MONI, is there anyway we can show this as Checkered(successful) flag, like the one we are doing in receiver determination condtion (If no receiver found, End Message Processing without error(Restart not possible))

Any ideas or other thoughts?

Thanks,

raj.

[Former Member · Accepted solution]

Raj,

Split mapping creates no messages.. this is not a error.

Open your MM and check..

when you use Multi mapping, the nodes will be...

Messages

Message1

......

Message2

......

Message3

....

If you see, the occurrence of Message1,2,3 are 1...1 not 0...1.

When you execute mapping and due to conditions, if PI couldnt generate even one target mapping, then it will throw this error message.

I did a work around in my scenario for the same.

Just repeat the target segment one more time...

map with with a constant ""

then do not map underlying segment(should have 0...unbounded).

If you have a File on the receiver side, it is a good idea , because you can select do not process for empty messages.

Else empty message will be processed on the target side.

Regards,

Venkat.

[prateek · Accepted solution]

The error essentially means that the message structure which should be output of the multimapping is blank. With this blank structure, the flow could not be proceeded. It should have atleast have one empty message with no values to make it correct. But then what is the condition you want to achieve?

Regards,

Prateek

[justin_santhanam · Accepted solution]

Prateek,

I understood all the errors and know everything how it works. But I was wondering if we can make the messages to be shown as succesfull. In our scenario we might get lot of errors so we don't want everytime to cancel the messages. It will be really big pain..

we were decided to use the BPM to solve the issue. Thanks for your help!

raj.