Skip to Content

Dynamic E-mail Determination Using New Features from SAP GRC NFE 10.0 and PI 7.1 Onwards


In my other article about Migrating GRC NFE B2B PI Mail Interfaces from 1.0 to 10.0 I suggested an approach to migrate your existing B2B mail interfaces. However, with SAP Process Integration 7.1 onwards it is much simpler. It is still relying on the approach described by described by Henrique Pinto in his article Using  SAP PI Lookup API and Dynamic Configuration in SAP GRC NFE Outbound B2B Interface for Dynamic E-mail Determination but you don’t have to do any lookups in PI because the email address can be pre-populated on the GRC NFE system. I don’t go into details for all preparation steps since they are already described in the aforementioned article.


First, you have to implement the BAdI /XNFE/EMAIL_B2B_OUT on the SAP GRC NFE ABAP system. The screenshot below shows a dummy implementation. This BAdI just writes an email address into an attachment.


NetWeaver Developer Studio

In the NWDS you have to create a Java Mapping that extracts the email from the additional attachment that you created in the BAdI implementation. The example below is named and it is designed to run as a stand-alone java mapping after the official java mapping from the PI standard content.

import java.util.Collection;
import java.util.Iterator;
 * This class is an PI Java Mapping which extracts the email
 * from an additional attachment for Dynamic Configuration
 * @author Denny Schreber
public class AttachmentReader extends AbstractTransformation {
    InputAttachments inputAttachments = null;
    OutputAttachments outputAttachments = null;
    DynamicConfiguration conf = null;
     * This method is for testing purposes only.
    public static void main(String[] args) throws Exception {
        InputStream in = new FileInputStream("C:/Testdaten/b2b_nfe_new.xml");
        OutputStream out = new FileOutputStream("C:/Testdaten/b2b_mail_out.xml");
        new AttachmentReader().execute(in, out);
     * @param tf_in             The incoming message
     * @param tf_out               The transformed message
     * @return                     void
     * @throws StreamTransformationException
    public void transform(TransformationInput tf_in, TransformationOutput tf_out)
            throws StreamTransformationException {
        inputAttachments = tf_in.getInputAttachments();
        outputAttachments = tf_out.getOutputAttachments();
        conf = tf_in.getDynamicConfiguration();
        this.execute(tf_in.getInputPayload().getInputStream(), tf_out
     * @param in                 The incoming message
     * @param out               The transformed message
     * @return                     void
     * @throws StreamTransformationException
    public void execute(InputStream in, OutputStream out)
            throws StreamTransformationException {
        // getTrace().addInfo("JAVA Mapping Called");
        Attachment attachment;
        String email = "";
        String aid;
        if (inputAttachments.areAttachmentsAvailable()) {
            Collection<String> attachments = inputAttachments.getAllContentIds(true);
            Iterator<String> it = attachments.iterator();
            // assuming only one attachment
            while (it.hasNext()) {
                aid =;
                attachment = inputAttachments.getAttachment(aid);
                email = new String(attachment.getContent());
            // Fill the dynamic configuration for the “to” field in the mail
            // adapter
            DynamicConfigurationKey key = DynamicConfigurationKey.create(
                    "", "THeaderTO");
            conf.put(key, email);
        // return the stream without doing anything
        int c;
        ByteArrayOutputStream baos = new ByteArrayOutputStream();
        try {
            while ((c = != -1)
        } catch (Exception e) {
            throw new StreamTransformationException(e.getMessage());

If you have an older Support Package in your PI system take care that SAP Note 1641548 is deployed. Otherwise, the attachment with the email address will not be removed and send with your mail.

However, another (not recommended) option would be to extend the Java Mapping from the standard content. When you use the graphical mapping you can run into namespace issues which will render the NF-e xml invalid.

Enterprise Services Repository

In the Repository, you have to import the Java Mapping under Imported Archives in your own SWCV. Then, copy the Operation Mapping NTB2B_procNFe_TO_procNFe / namespace from SWCV SAPBO SLL-NFE 10.0  into your SWCV and add the new Java Mapping as the second step after the ProxyNamespaceCleaner. (I’m assuming you have a dependency created between the SWCV). Here, you have to select the “Read Attachments” option in order to allow the Java mapping to access the attachment.


Finally, save and activate all your changes.

Integration Directory

In the Integration Directory you have to change the generated Interface Determination and select your new mapping from your SWCV. Save and activate.


Please take care that your email communication channel has the option “Keep Attachments” under General and “Use Adapter-Specific Message Attributes” under the Advanced tab selected. Furthermore, you have to use the MessageTransformBean to rename the attachment.



In the PI monitor, you can see how the additional attachment with the mail address is removed after the mapping.


In the end, the mail recipient should get an email with the NF-e as attachment called NFe.xml.

You must be Logged on to comment or reply to a post.
  • Denny, thanks for this great content.

    I was wondering if this solution should work for GRC 10.0 running with PI 7.0.

    We have different options in Interface Mapping (such as the Read Attachment checkbox).

    Tks again!

    Rafael Vieira.

    • Hi Rafael,

      To my knowledge no: PI 7.0 does not have the “new” mapping api which allows to access attachments from Java mappings. That the Interface Mapping has the “Read Attachments” checkbox is also new to me, which SP of PI 7.0 are you using?


      Denny Schreber

      • PI 7.01, SP06.

        Some people say we cannot use the previous solution proposed by NFe team (by using the RFC lookup) but this Javamapping, as you said, wouldn’t work on PI 7.01. Not sure, now, how to proceed.


        Rafael Vieira.

    • Hello Rafael, I am currently working on upgrading Nfe from 1.0 to 10.0. We are using PI 7.02 EHP 11.  We enabled the BADI to get the email as a additional attachment, but we are not able to access it in UDF. Is there any other way to  read the additional attachment, the check box you are talking about, where can I find that. 

      Please help


      Bhasker Appala

      • Hello Bhasker,

        I’ve seen guys configuring the dynamic email determination by using the BADI, just like you did.

        I’m using the RFC lookup option and it’s working fine.

        Let me know if you need any further details regarding the solution I’m using.

        Best regards,

        Rafael Vieira.

  • Denny,

    Thank you for the wiki, was really excellent.

    After doing this implementation, the e-mail always arrives as an attachment to email. That is, an e-mail arrives, you have another email attached and inside the annex is XML.

    I do not know what’s going on, this could be the problem of the e-mail exchange?

    Helped others posting the wiki, but if not asking too much, please help me again.

    Thank you.

  • Denny,

    How would you handle the issue if the email address has not been maintained (for example, business simply forgot to maintain the email address). Do you raise the error message in PI or BADI?

    Also, is there a way to identify the “event” (this BADI is called during NFE and also CC-e events).. Is it possible to identify whether it is the original NFE or CC-e event?


    • Hi Krish,

      That depends what approach is better suited for your environment but how about using a default mail that someone would receive in the error case and can take appropriate action on it.


      Denny Schreber

  • Hi Denny,

    I have a few questions:

    Is it possible to use this solution for the CTB2B scenario?

    I meant, is the BADI  /XNFE/EMAIL_B2B_OUT also accessed when we have a Cancel NF-e Out? Is it necessary to make any changes in the java mapping source code?

    Thanks in advance,


    • Hi Daniela,

      Yes, it works for CTB2B and ETB2B as well. Remember that the Cancellation web service will be decommissioned soon and replaced with the Cancellation Event.


      Denny Schreber