Mapping values from the payload in the standard error message in PI 7.31

[nitindeshpande]

Hi,

I am working on files that are very large and when such a file fails with some error ,it becomes very difficult to track exactly for which record it is failing.

For example if the file has 6000 records and the problem is at 641st record,it takes a lot of time to identify which is the 641st record even with Notepad++.

One of the ways this can be taken care is if we can add any unique value from the record say "employee id" and add it in the error  that we receive in the alert message.

Please let me know if any one has handled a similar situation or implemented any other solution to reduce delays in error analysis.

[Former Member]

Hi Nitin

You can add payload values in the alert message in the message mapping using the function module SALERT_CREATE. But you have to know the condition before you call the RFC. The error you are getting is not a generic error because it is not always that one file will fail for only one wrong values.

You have to find out the error from editor only. You can try editor like EditPad pro, text pad , even notepad++ also helps.

[nitindeshpande]

Hi Indrajit,

Thanks for your response.

We have a dual stack installation but we have developed the Interface using only java stack.

In this case if we use SALERT_CREATE and define container variables in ALRTCATDEF,will it work?

Also the source xsd for all the Interfaces is same ,so we were thinking when a message fails at say Record[50],then we can take the 50th employee id and display it in the alert.

Do you have an idea if this is possible?

Nitin