cancel
Showing results for 
Search instead for 
Did you mean: 

Capture File Content Conversion Error and Send email to end user

Former Member
0 Kudos

For Mapping issues, I have leveraged capturing error through a UDF and invoking mail channel from within this UDF.

Now the next challange is to capture File Content Conversion errors in sender file channel and send an email to the legacy contact to send the corrected file again.

Your thoughts.....

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member187587
Contributor
0 Kudos

As a practice - Integration errors taking place in SAP PI platform are aimed for SAP PI technical personal rather then business users. there are many examples for that...(the post is too short to bare )

The sender business application requires some kind of quality of service for thier messages send to SAP PI. it is the task of the technical people to handle the faults according to the SLA and report them.

Business errors in SAP PI are only relevant when a ccBPM is used during some automatic business processing where a business user intervene is needed as part of the process. in this case the kind of data describing the error will be more of business nature rather then technical.

A file adapter is a common but primitive case.using the file adapter you usually have no end point to report back.

In case where a Web Service exposed by SAP PI is consumed by an external application, it is possible to return Validation errors for example (taking place in the AE) and send them directly to the sender business system. this is an example where an error can be handled on application level of the sender business system and not on SAP PI platform.

ambrish_mishra
Active Contributor
0 Kudos

Totally agree with you Nimord. Mandatory fields missing in a record should be validated at source system and handled there and not PI.

Muniyappan
Active Contributor
0 Kudos

Hi Vicky,

You have to go for alert configuration as mentioned by hareesh.But you can not expect alerts for only FCC related error. you will get alerts related to all adapter engine error. because you don't have any error code or category for Adapter Engine while defining alert rule.

Even 7.31 for file adapter you have File adapter status Processing Error,Channel Inactive, Channel not initialized.

you can not go for UDF also error will raise before message hitting message mapping.

you get generic alerts  and go to system and check what went wrong.

Regards,

Muniyappan.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

If there is data issue and that causing conversion error then it is problem with sender system.You need to deal with them. Triggering alert for those failed messages make sense for the maintenance purpose. But you might also need to configure correctly based on the requirement to avoid these errors. If the sender system changes business requirement and violates the business agreement then you have to modify your structure for the permanent fix.  If you do java class to handle the conversion on the sender side and convert the data to xml and use file sender to poll xml, then you might have to do trigger alert things outside pi.  IMO, that does not give any solution.

ambrish_mishra
Active Contributor
0 Kudos

Hi Vicky,

This functionality specific to FCC error and sending the mail to legacy owner will not be simple as triggering an email through a UDF in mapping. It will probably require querying XI_AF_MSG_AUDIT and writing custom functionality to access and relay the error as an email to third party owner.

Hareesh's suggestion to utlilize standard CCMS alert mechanism is robust and standard way of sending alert emails. This will send generic emails on different kind of message failures at adapter level or integration engine layer and can be propagated to a specific mailing groups.

Hope it helps!

Ambrish

former_member184720
Active Contributor
0 Kudos

Hi Vicky,

You can setup the alerts right? whenever there is failure in the channel alert will be generated and you can even configure the mail recipients so that business will get notified.

Alert configuration: http://scn.sap.com/docs/DOC-3804

There is no need to write the UDF too to handle that mapping failures unless you need some customization.

Regards,

Hareesh

Former Member
0 Kudos

The problem is that the errors generated by Alertcatdef and RWB alerts are very technical and business may not be able to make much sense of it.

former_member184720
Active Contributor
0 Kudos

Then the best way is to go for the java mapping i.e. do the content conversion using java mapping but not in the sender channel. This way you can get the field which is causing the issue and of course you can generate alert in whatever the way you want.

But if you have more channels, want a generic and standard solution i would always prefer standard RWB/CCMS alerts. It won't take much time to support team/any one to let business know what is wrong with the failed file.

Thanks.

Regards,

Hareesh