Skip to Content

Find filename of SAP B2B EDI file that failed

I have followed the blogs at https://blogs.sap.com/2012/09/27/b2b-edi-inbound-step-by-step-configuration/ and https://blogs.sap.com/2016/05/26/sap-pi-b2b-ansix12-inbound-scenario/ to setup EDI and TPM. Everything works fine. We have an interface that processes thousands of files an hour and we have an odd file or 2 that fails in the mapping. My question is how does one identify the file that failed ? There is nothing in the logs that tells me which file failed

The first part of the interface reads a file (I do set the filename dynamic parameter here so it shows up in PIMON) and sends it to an EDISeparator channel. This step is successful. The 2nd step involves an EDI Separator sender channel and an IDOC receiver comm channel. There is a mapping involved here and this is where the error occurs. How does one trace the filename from the error in pimon ?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jul 21, 2017 at 05:44 AM

    Anil,

    AFAIK the filename characteristic remains in 1st Flow i am not sure if this is passed to second flow once EDI_Separator interprets this.

    You may need to use some other value in the paylaod like PO number to have UDMS defined.

    Br,

    Manoj

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 21, 2017 at 07:13 AM

    I haven't worked with the B2B Addon hands-on when it comes to EDI but if it works anything like the Seeburger modules (which I presume it does), the filename would not be available after the interchange is split into individual messages. What will be available in the child messages is the original interchange control number, so you can use that as a correlation criterion. Also you could store the GUID of the interchange containing the failed message in the archive file name and link the failed child message back using the parent GUID.

    Regards,
    Patrick

    Add comment
    10|10000 characters needed characters exceeded