- SAP Managed Tags:
BRF+ - Business Rule Framework Plus
Introduction:
- BRF+ stands for Business Rule Framework plus which Provides a comprehensive application programming interface and user interface for defining business rules.
- It enables you to define business rules without the need of writing ABAP Code.
- BRF+ Function provides an interface between a business rule modelled with BRF+ and an application using that rule. The BRF+ function serves as a container for the entire business logic of a rule.
- BRF+ is not new and even not directly related to SAP S/4HANA, but with the release of SAP S/4HANA 1610, BRF+ gained more attention since it is launched as the go-to solution for some business processes. The most important ones are the changes in Output Management for purchasing and Billing.
- In order to use BRF+ with your SAP ECC system, your system must be on SAP NetWeaver 7.02 SP6 or above.
- BRF+ supports features such as simulation, trace, transport, XML, export and import.
- 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/4HANA is 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.
- Rules are Implemented as expressions which are assigned to the function. The rule input is known as “Context ”, and the rule output is called “Result”.
- It is a part of SAP NetWeaver ABAP Stack.
Key Benefits:
All output parameters can be automatically determined via a configuration activity based on BRFplus. The benefits are:
- You can send multiple messages to multiple recipients using multiple channels at the same time.
- You can configure anything without the need for ABAP exits.
- You can use each determination step on application-specific fields that can be extended.
- You can use predelivered content/determination rules to simply run output control out of the box.
- Extensibility via CDS is supported.
Important Note: Basis Team need to upload Standard XML Forms in SAP system. They import the forms by using BRF+ Transaction code.
If the forms aren't uploaded, we won't be able to see the Output Type in the OPD Transaction. We can get the details of Form from SAP Note: 2248229 with the help of Basis download the note.
Limitations in BRF+:
- Idocs are not fully supported by the New Output Management. Their use is restricted to business applications that previously used NAST.
- Only output types which can be mapped 1:1 to the NAST-KSCHL can use IDoc.
- Only business partner-based communication is supported, but no communication to logical systems.
- No ALE supports.
- BRF+ doesn't fully integrate with the document management features provided by earlier SAP systems like SAP script or Smart Forms.
- Compared to older output management solutions, error handling and debugging can be a bit more complex or less intuitive in BRF+.
- It requires better integration of monitoring tools and workflows to identify issues with output processes, especially when compared to more established NAST error handling.
NAST to BRF+ Conversion Overview: There are several updates and enhancements in SAP regarding the conversion from NAST to BRF+ for output management.
1. Mandatory Use of BRF+ for Certain Documents: With the release of SAP S/4HANA 1511, output management using BRF+ became mandatory for Purchase Orders. Similarly, in later versions, BRF+ is required for managing outputs of Sales Orders and Billing documents, replacing the traditional NAST-based output management.
2. Increased Number of Supported XML Forms: In earlier versions like SAP S/4HANA 1709, over 12 XML forms were supported. This number has significantly increased in subsequent versions, with SAP S/4HANA 1909 supporting over 20 XML forms. This expansion allows for a broader range of output types and formats to be managed using BRF+.
3. Simplified Configuration and Integration: The configuration process for BRF+ has been streamlined to reduce complexity. It allows for the easy import of XML files for output determination, simplifying the setup and customization of output types.
4. Integration with SAP Fiori and Other UI Technologies: BRF+ integrates seamlessly with SAP Fiori applications and other UI technologies like SAP GUI and SAP UI5. This integration ensures a consistent and modern user experience across different platforms.
In NAST, the configuration path that needs to be maintained is quite complex. The steps need to be followed are:
- Condition Table
- Access Sequence
- Condition Type
- Output Type
- Condition Record
For the BRF+ in S/4 HANA it is even simplified even business user can maintain Decision Table.
The steps need to follow are:
- Output Type
- Receiver
- Channel
- Printer Settings
- Email Settings
- Form Template
Activate or Deactivate SAP S/4HANA-Based Output Management:
We maintain this configuration because it enables the use of SAP S/4HANA-based output management for Purchase Orders (POs), which is necessary for integrating with other systems like the Ariba Network and managing output messages efficiently in the SAP environment.
- Even if you do not activate the specific step for SAP S/4HANA-Based Output Management related to integration with the Ariba Network, BRF+ (Business Rule Framework Plus) can still be used in SAP.
Configuration Path: SPRO→ IMG → Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network Application-specific settings → Define Message Output Control → Method 2: Use SAP S/4HANA-Based Output Management → Activate or Deactivate SAP S/4HANA-Based Output Management
If you need to activate select the Mode: New output management is active and click on save.
Configuration steps:
- Storage repository settings
- Manage Application Object Type Activation
- Define Output Types
- Assign Output Channels
- Define Rules for Determination of Master Form Template
- Assign Form Templates
- Assign Email Templates
- Define Business Rules for Output Parameter Determination
1. Storage repository settings: Configuration: SPRO > Cross-Application Components > Document Management > General Data > Settings for Storage Systems > Maintain Storage System
SOMU_DB is a standard content Repository for Output Management DB Storage. If you can’t find the standard content Repository, click on the create tab and maintain the data mentioned below:
Content Repository: SOMU_DB Storage Type: SAP System Version: 0047
If you want to customize, select the standard one and click on Copy as tab as shown change the content Repository name and click on save.
2. Manage Application Object Type Activation Configuration: SPRO –> IMG –> Cross-Application Components -> Output Control -> Manage Application Object Type Activation
If you can’t see the standard Application object type in the screen, just click on Entries and click on Help button and select the required Application object type as per the requirement and maintain status as active and click on save.
3. Define Output Types: Configuration: SPRO –> IMG –> Cross-Application Components -> Output Control -> Define Output Types
The standard configuration is already set up. If the standard option is not visible, you can add it by clicking on "New Entries." To modify the output type, select the standard one, click "Copy As," assign the output type to the Application Object Type, and then save the changes.
4. Assign Output Channels: Configuration: SPRO –> IMG –> Cross-Application Components –> Output Control –> Assign Output Channels
In this step we can assign output channels to application object type and output type.
5. Define Rules for Determination of Master Form Template Configuration: : SPRO –> IMG –> Cross-Application Components –> Output Control –> Define Rules for Determination of Master Form Template
This step is used to establish rules that determine which master form template should be applied based on specific conditions or criteria.
In the "Define Rules for Determination of Master Form Template" step in BRF+, we maintain the rules and conditions that link specific criteria, such as document type, application area, or other relevant factors, to determine the appropriate master form template to be used.
6. Assign Form Templates: Configuration: SPRO –> IMG –> Cross-Application Components –> Output Control –> Assign Form Templates
This step is used to link specific form templates to the rules or processes defined in BRF+. This step ensures that the correct form template is associated with a particular business scenario or document type based on the logic defined in the earlier steps, such as the "Define Rules for Determination of Master Form Template" step.
It enables the system to dynamically assign the appropriate form template for generating documents, reports, or outputs based on the conditions set in the rule framework.
After Maintaining the data click on save.
7. Assign Email Template: Configuration: SPRO –> IMG –> Cross-Application Components –> Output Control –> Assign Form Template
This step ensures that the correct form template is associated with a particular business scenario or document type based on the logic defined in the earlier steps, such as the "Define Rules for Determination of Master Form Template" step.
8. Define Business Rules for Output Parameter Determination: Configuration: Configuration: SPRO –> IMG –> Cross-Application Components –> Output Control –> Define Business Rules for Output Parameter Determination
I won’t see the option for Purchase contract. So, I need to add template related to purchase contract in BRF+ Transaction code.
In settings select User Mode: Expert
In the Tools tab, choose the XML import, add the standard XML form for the Purchase contract, and include the transport requests.
The Customizing Request will store all the configuration settings for BRF+ that have been maintained.
The Workbench Request will store the configuration settings for Output Types.
Now, the Purchase Contract option is visible in the Output Parameter Determination.
For each step, click on Edit Tab and Maintain the appropriate data and click on Activate button.
The system will display a pop-up tab like want to activate the Output Type click on yes.
It will remain empty because the Email Recipient will be selected from the vendor master data maintained during vendor creation.
All the configuration settings have been done. Now create the contract in ME31K Transaction code with the Agreement Type “WK.”
The Agreement Number – 4600000002
Go the Change mode in ME32K enter the Agreement Number and click on Message Tab as shown.
The status will display as In Preparation to set the status to complete, select the line and click on the send Output tab as shown.
The status will change to “To be Output”
After completion of this step come back and click on save the status will change to completed.
To check the print preview, click on the Display Document tab as shown.
In conclusion, BRF+ (Business Rule Framework Plus) for output management in SAP is a powerful tool that helps automate and control the way documents are generated and managed. It allows businesses to set up rules for different types of outputs, ensuring consistency and efficiency. By using BRF+, companies can reduce manual work, improve document formatting, and make smarter decisions on how to handle outputs. Overall, it helps streamline processes, making them faster and more flexible while improving business performance.
5 Comments
