Exception handling for Inbound IDoc

[Former Member]

Hi,

I have a Flat File to IDoc Scenario. Flat file is an EDI 210 message. I will serialize and tranform EDI210 into IDoc.

I want to capture the exceptions from the flat file during serialization. My schema will have exception structure.

How do i deal with the exception. Do i display the exception in XI or should i send it to SAP system(Receiver)? What is the best approach?

Note : I believe IDoc does not have any exception structure.

Kindly Advice.

Thanks & Regards,

Gowri

[Former Member]

Hi Gowri,

In this case whenever you get Mapping Exception , you can raise an Exception with the help of BPM and you can send the status to the RFC. But with the help of BPM.

For a Simple case refer:

http://help.sap.com/saphelp_nw2004s/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm

If you want you can do it without a BPM

and throw an exception in case any of the values is missing:

have a look at this weblog on how to throw exceptions

in a nice way:

/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping

Also just go through <a href="/people/sap.user72/blog/2005/02/23/raising-exceptions-in-sap-xi-mapping Exceptions in SAP XI Mapping</a> and see if it helps you solve the problem.

Also go through these links:

http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f2243d711d1893e0000e8323c4f/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/5d/2166e6a91d11d188de0000e8216438/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/05/bb223905b61b0ae10000000a11402f/content.htm

Please do let know if it helped.

Regards,

Abhy

[Former Member]

Hi Gowri,

we got a similar problem.

Imagine: If you display all your mapping and routing problems in SXMB_MONI you got a lot of work!

We do it that way: The incoming messge triggers a BPM. There we got a exception branch for mapping errors.

If the mapping goes wrong we send a ALEAUD01 Idoc to the SAP system to inform the relevant people.

Mapping errors occur in two cases:

a) wrong input message

b) wrong mapping

After testing enough no b)-errors should occur!

In this cases it is better to inform other employees.

Regards Mario

[Former Member]

Hi Mario,

I guess, Thatz the only way to do it. SAP XI database is going to be filled up with error message. Have you taken care of that?

Could you please share BPM exception handling part(may be a screenshot).

Thanks,

Gowri

[bhavesh_kantilal]

Gowri,

How and where is the error to be recorded?

One option, make the validation in the FILE ADAPTER using Adapter Modules and filter valid andinvalid Records.

Or, Do the same in the mapping and contruct separate IDOC and error message and send them out using a BPM.

Rather than sending an Error IDOC to the R3 system and then using APplication Ack's this option of filtering good and bad records in mapping should be a better approach.

Regards,

Bhavesh

[Former Member]

Hi Bhavesh,

I agree with on filtering the records into good and bad records. After collecting the bad records, how do i deal with it?

Should i display them in XI monitor or send it to SAP system?

If i choose the option of sending it to SAP system, then i have to set the acknowledgement part. Please correct me if i am wrong. Acknowledgement will be sent for both good and bad records. If so, i don't want to choose this option.

Thanks,

Gowri

[bhavesh_kantilal]

Gowri,

<i>

After collecting the bad records, how do i deal with it?

Should i display them in XI monitor or send it to SAP system?</i>

The choice is a purely business and requirements issue.

If you want, you can send it back to the Application System as a file, or , send an Email, or, just ignore the error records. What is the client requirement?

http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm

Regards,

Bhavesh