Skip to Content

SAP FEH Mail Alerts for ABAP Proxy(Inbound) in ECC

In case of Asynchronous Inbound Proxy Interfaces there is often a case where the Interface fails in the ECC system due to issues like Master data not being maintained, incorrect data received from legacy leading to conversion issues eg: Character in Amount or Quantity field, which needs to be continuously monitored through the XML Monitor transaction SXI_MONITOR or SXMB_MONI

SAP has introduced Forward Error Handling (FEH) for Proxy interfaces which also provides the option for sending Email Alerts via the Error and Conflict Handler (ECH) in the Post Processing Office (PPO) Framework whenever the Interface goes into Error. The First part of the Configuration for FEH has been explained in the detailed and informative blog by Michal Krawczyk hence this blog purely deals with the Email alert configuration in ECC.

Below are the detailed steps to be followed to enable this Alert mechanism in ECC –

Disclaimer: Please use Software component and Business process already configured for FEH. Given below is just an example taken for explaining the steps.


1.     1. The first step in this configuration is to ensure that the standard BADi implementation /SAPPO/ORDER_CR_NOTIFY_DEFAULT of BADi  /SAPPO/ORDER_CREATE_NOTIFIY is active(it is normally active) as can be seen below:

FEH Step 1.png

2.    2.  In the Configuration Transaction SPRO, go to Define Worklists and give one of the below names as per your module:

             FEH Step 2 a.png

               FEH Step 2 b.png

3.     3. Go to Assign Worklist to Business processes and create a record for your respective interface. Please note that this is the same Software Component and Business process created for FEH configuration

            FEH Step 3 a.png

              FEH Step 3 b.png

4.    4. Go to Process Notifications for Orders in Worklist and create a record as below for your respective Interface

     FEH Step 4 a.png

       FEH Step 4 b.png

5.    5. After SAVE into customizing request, Choose the record and click on Printworkbench Settings and enter details as below and SAVE:

          FEH Step 5 a.png

            FEH Step 5 b.png

6.    6. The same priority maintained here needs to be maintained at the Business Process level, which needs to be done in Assign Priority to Business   

          Processes as below:

    FEH Step 6 a.png

      FEH Step 6 b.png   

7.    7. After this, Users need to be maintained in the Worklist defined(ZBP0). This is a one time activity that has to be done in every system(No transport request is created on saving these changes). Transaction code is /SAPPO/WL_CHANGE and execute, you would see your Component along with the Worklist wherein Users can be dragged and dropped as can be seen below:

          FEH Step 7.png

SAP also provides an option of assigning a complete Organizational Unit in which case all the users assigned to the group would get the Email alert notification. Email would be sent to the Email ID maintained in User settings as below:

       FEH Step 7 b.png

8.     8. After this, test your FEH with one failure scenario if an Email is triggered to your ID(your User ID needs to be maintained in the worklist) an Email in the below format should get triggered:

     FEH Step 8.png


On completing the initial Configuration settings for the PPO mail alert, the interfaces were tested to check if they trigger an email to the Users maintained in the above mentioned user list, but there was an issue due to which the EMAIL was not getting triggered:

On contacting SAP it was learnt that there are some settings related to the MAIL functionality that need to be altered. There were two suggestions given by SAP for the same:

Please refer to the following customizing activity:
Cross-Application Components
–General Application Functions
—-Print Workbench
——Define Shipping Control

Here the attribute “Storage Mode” is set to value “Print and archive” for Dispatch Control MAIL.

Please remark that the system does not support storage modes “Print and archive” or “Archive only” in this PPO-notification scenario.

As a result PPO orders are generated without triggering a mail notification.

To resolve this issue please choose storage mode “Print only” in the customizing activity mentioned above.

Configuration for the Print Workbench General Setting was done as suggested as can be seen below:

FEH Issue 1.png

However, this is a general setting for all documents using the print workbench with MAIL.

Alternatively you could adjust the PPO-specific application form /SAPPO/NF_NOTIFICATION_COLL which gets called in your PPO notification scenario via transaction EFRM:

-Choose Tx EFRM


-Choose Change

-Double Click DOCUMENT in the hierarchy shown on the left

-Choose Storage Mode “Print only”

Also Configuration for the Print Workbench PPO Setting in /SAPPO/NF_NOTIFICATION_COLL was done as per alternate method suggested as can be seen below:

FEH Issue 2.png

Also, the Priority maintained in ‘Print Workbench Settings’ and that assigned at the Business Process level should be the same else there is some standard check that fails resulting in NO mail trigger.

You must be Logged on to comment or reply to a post.
  • Hi Vijay,

    Thanks for posting, we have just started using FEH and had problems setting up the notifications.

    The system I am using is ECC 6 ENHP6 Patch 6 and the form /SAPPO/NF_NOTIFICATION_COLL doesn’t exist in the system. Did you activate anything or do anything in particular to get this form or was it already in your system? What version system are you running?



    • Hi Chris,

      Assuming you checked the package for Cross Application Component, we have the same details i.e. ECC 6.0, Level 6, ENHP6 and the release is 731. We did not explicitly perform any steps for activating this.

      Could you please check transaction EFRM, enter Application Form as /SAPPO/NF_NOTIFICATION_COLL. The only thing i can think of is we did this step right at the end i.e. after all the FEH settings were in place. Also Error and Conflict Handler was already active.

      Glad to help.



      • Hi Vijay,

        I checked EFRM and it advises the object doesn’t exist. I have ECH working and items going to PPO, just can’t get the notification working as we don’t have the form templates.

        You don’t have AIF or similar products installed do you? I checked one of our CRM boxes and it has the /SAPPO/NF_NOTIFICATION_COLL form but ECC doesn’t have it.

        Thanks again


        • Hi Chris,

          No, we do not have the AIF installed since this is the first place we went to check for Mail Alerts.

          The master table for the standard Form is EFRM. I checked this table and the creation date of this form reads 2010 hence this most likely is Basis activity. The print workbench package is EEPW, so someone from Basis would need to check on the details of the update in this package. Also since you mention it is present in the CRM box and not in ECC, a comparison between the two systems might help.

          Hope this helps.



          • I ended up logging a message with SAP for this one and the solution was to copy/reference the form from client 000 to the relevant client.

            Not sure how our dev and production systems got out of sync as it was visible in prod but not dev.

            Anyway, if anyone else has this issue SAP recommended using the reference method from the following help document to make the form available in the dev client:


            Within the above link navigate to:

            Application Forms –> Administration and Transport –> Using References


          • Hey Chris! Nice to hear from you, more importantly that you have the solution 🙂 .. Thanks for Sharing the solution.. thats very thoughtful of you.. (i know how the helplesness feeling when no one can help and SAP coolly says you should have done this.. been there too 😉 )

            Thanks again.



  • Hi Vijay,

    Thanks for the detailed blog –

    1. Can we customize PPO Alert mail subject and error content in mail body? IF yes do you know how to do that?



    • Hi Chirag,

      We are ABAPers… anything is possible for us… atleast the Client seem to think so… 😉

      Yes. If you noticed we chose the standard Form for the email in the ‘Process Notifications for Orders in Worklist’ node in SPRO. Instead of that we’ll have to configure our custom form in the EFRM transaction

      Well how that’s done is something i’m still to explore since the client just wanted an Alert for now.. Not much help to you but will let you know if i find something..



  • Hi Vijay,

    The ECH configuration is working as expected and creating PPO.

    I did all required configurations to trigger alert emails as advised above. After assigned the user ID for work list and run the interface i am getting following popup to confirm and it leads to short dump (As we can’t action when message coming from PI).

    however even i run the same payload from sproxy and confirm PRINT from pop-up still it’s not generating emails.


    If i remove user from worklist no popup prompting and no email generating.

    Can some one please advise is something more need to do?


    • Hi Siva,

      I’m guessing you have all the Print settings in place including maintaining MAIL in the Print workbench settings. When we were struggling with the configuration, though we did face quite a number of Issues but we didn’t encounter an issue like you mention above. Hope you have also checked the issues portion maintained after the Configuration.
      Its been more than 2 years and there maybe additional settings required. I’ll try to check from my end but we are currently not using PPO with this client. Not much help but PPO is one complex yet useful feature.


  • Hi All,

    I’ve tried configuring this, but no email is generated.

    Will the email can be seen in SOST? How to check or troubleshoot if the email is generated?

    Thank you,

    Suwandi C.

    • Hi Suwandi,

      Hope you have all the configurations in place including the PPO configuration mentioned by Michal Krawczyk. There can be many reasons for no Mail trigger a few of which i have mentioned above that we faced.
      Other small ones are email ID needs to be maintained for the User IDs in question. Also, there was one specific issue that i remember. What happenend was during testing we had used a Worklist and during each run a set of users kept getting emails, so Basis for a few weeks just shut the email send from SAP. Please also check with the Basis team.
      Unfortunately, its been quite sometime that i used this feature now, i guess there should be an SOST record for the mail send but i do not clearly remember checking this.

      Hope your issue gets resolved soon.