Skip to Content
Author's profile photo Former Member

Output Management via BRF+

With SAP S/4 HANA a new Output Management approach is in place. The complete configuration differs from the configuration that is used when output management is based on NAST (condition technique). The configuration is based on BRF+. In SAP S/4 HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For the form determination rules (along with other output parameters) BRF+ functionality is used.

  Output management based on NAST is not available for new documents in SD Billing from 1511 and is extended to sales order management from 1602. Similarly, output     management using BRF+ is mandatory for Purchase order from 1511.

Prerequisites –

  • Uploading XML for importing output determination application in BRF+ (Ref note 2248229).
  • BRF+ is active and usable
  • Background RFC configuration has been set up
  • Adobe Document Server is available – ADS needs to be implemented to allow SAP to fetch PDF properties for rendering output form
  • KPRO has been maintained – KPRO allows to store PDF attachments on physical location.

Steps for uploading XML –

Note 2248229, provides decision tables for new output management. We need to download XML files to local drive and import them using below steps.

Transaction code BRF+ or BRFPLUS

BRF+ workbench will be displayed. For importing output application, we need to change layout to “Expert” mode. Follow below steps –


a) Select user mode as “Expert”.

b) Save this settings.

Steps to import –    

a) Download zip files from SAP note 2248229 and save them on your local machine   

b) Next, we need to select Import XML under the Tools menu.  


c) Select relevant file in below screen.        


d) Specify Customizing request.    

e) Click on “Upload XML File” button.    

f) Uploaded application will now be available under Repository tab. 


Configuration –

Below configuration steps are relevant for all application areas (Sales Order, Purchase Order, Billing Documents and Outbound Delivery)

  SPRO Node for output configuration (IMG Path –> Cross Application Components)      

1) Define Output types –   

     Output Control -> Define Output Types    


2) Assign Output Channels –

     Output Control -> Assign Output channels      In this activity assign output channels to output type. 

3) Define Determination of Form Master Templates –    

Output Control -> Define Determination of Form Master Templates     

The master form template contains static data (such as a logo and footer) that is applied to each form page and is determined based on configuration setting maintained.      


a) Enter a rule ID, preferably an ID that indicates the logic of the rule.

b) Enter an ordinal number to specify the position of the rule in the determination sequence.     

c) Following parameters are optional –

    • Organization Type
    • Organizational unit
    • Channel
    • Sender country
    • Form Template

    During document output, the master form template is determined by comparing each defined rule with the current data provided by the application. If a parameter is not      defined (no value entered), this parameter is considered as a match, and else, system determines the rule where all parameters match. Master form template is used      corresponding to this rule.

Business Rules for Output Determination –

Below configuration steps are relevant for all application areas (Sales Order, Purchase Order, Billing Documents and Outbound Delivery)

SPRO – > Cross-Application Components -> Output Control -> Define Business Rules for Output Determination (Transaction: OPD)

In this Customizing activity, you can define how the system determines output parameters during document processing. You can define business rules for the determination of output parameters, such as output types, recipients, and form templates. 

Following determinations are available –

Determination Number of Matches Result Example
Output Type Multiple Output Type to be used Output BILLING_DOCUMENT can be determined on the basis of billing document type (F2).
Receiver Multiple List of Receiver Roles Receiver roles (SP, SH, RE, RG) are determined for the determined output type (BILLING_DOCUMENT).
Channel Multiple List of Output Channels Channels (EMAIL, PRINT and IDOC) are determined.
Printer Settings Single Output devices and number of copies Output device (LOCL) for channel PRINT
Email Settings Single Sender Email address and Email Template Sender email address & Email template (SD_CI_DEFAULT_EMAIL_TEMPLATE)  is determined for output type.
Email Receiver Multiple List of Email roles(To, Cc, Bcc) and email addresses Email addresses for roles (To, Cc, Bcc) are determined for output type. This step is optional and system uses receiver email address in case step is not maintained.
Form Template Single Form Template name and language Form template (SD_CI_STANDARD_DE) is determined with following options:  Output type, Receiver, Channel, Recipient language, Sender Country, Recipient Country and document category.
Output Relevance Single Can the document be output based on the defined condition (Yes/No)? Output to be issued only when billing document is successfully passed to accounting.

Example of maintenance of Channel determination –

  • Select Rules for relevant document, example BILLING_DOCUMENT.
  • Select determination, example Channel to be used for triggering output type.
  • Input parameters could be changed by adding input columns to determination table. Each determination table consists of input columns (condition columns) and result columns. You can add new input columns via the table settings.
  • Maintain relevant input combination to determine the channel needed. Multiple channel can be selected for the same combination.


After changes, click on Save and Activate.

Output processing –

  • Output determination is performed in document based on determination rules defined for Output type, receiver role, channel, form template, receiver email address and email template withe status as ‘In Preparation’. Default data can be changed in the document.

                  Overview Screen:                     


             Detail Screen: 

  • Processing of output –

           Only two dispatch times are available in new output management system.

    • Immediately (1)

                    Output is processed as soon as document is saved. If no errors, output type status changes to “Successful”. In case of errors, output will be in “Error” status.                     Errors can be viewed by clicking log button.

    • Scheduled (2)

                    Output is processed using new transaction introduced VF31F for billing document.               


  • Email output in SOST –

          Invoice copy is sent as PDF attachment.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Abhishek Kumar
      Abhishek Kumar

      Hi, Thank you for this blog.

      Can we also configure "Reminders and Urging Letters (Expediters)" using  output management via BRF+ for vendor reminder emails, if the delivery date of a material is coming up or past due?

      Please suggest.

      Thank you.


      Author's profile photo avinash kavi
      avinash kavi

      Hi There,

      thanks for detailed overview of output functionality using BRF+.

      My question is related to object 'Purchase Order'.

      My question is, in ECC system we had NACE technique of output management and there we had control over whether message should be triggered for create or change event of the purchase order.

      Is something similar covered in BRF+ for output determination as well??


      Appreciate response.


      Author's profile photo Umesh Patil
      Umesh Patil

      Thanks  for the detailed information on BRF+.

      I wanted to know if is it possible to have editable Email body for the outputs which we setup using BRF+ so that a note is added by user. Currently user is sending mails to multiple recipients  and also adding a note to the email.  Using BRF+ we can send mails to multiple recipients. But is it possible to add email body every time a mail is sent?

      Author's profile photo Praveen Kumar Singh
      Praveen Kumar Singh



      Thank you for the blog, just one query is XML import client dependant? Because I am facing an issue with two different clients.

      Author's profile photo Avika Srivastava
      Avika Srivastava


      Thanks for this great blog.

      my question is we have 2 output

      1- order confirmation

      2- order confirmation change

      i want second one should trigger when any changes made in sales order. How to achieve this.



      Author's profile photo Jayanth Shettigar
      Jayanth Shettigar

      Hello Sir,


      What is the use of Output relevance in BRF+ OPD ? We can add filters in Output type in drop down and also in Output relevance we can add filter. I wanted to use requirement routine to create Output in Sales Order but now in S4 we are using BRF+ instead of NACCE so wanted to understand where to configure those rules.


      Thanks in advance!


      Jayanth S