What is BRM?
SAP NetWeaver Business Rules Management (BRM) empowers organizations to streamline decision management in Business Process by means of Rules. It Enables Business users to maintain conditions on their own, thereby reducing dependency on IT support.
Implementation
SAP NetWeaver BRM is part of Composition environment (CE) and for customers having SAP Process Orchestration (SAP PO) it is part of PO JAVA stack.
Offerings
- Rules Composer
- Rules Manager
Tools
Business Rules are composed using SAP NetWeaver Developer Studio (NWDS) àRules Composer
Note: SAP NWDS can be download from SAP’s Wiki page here
Use Cases
Few most common Use Cases of SAP NW BRM in SAP Process Orchestration are:
- Routing Rules
Within routings, Business rules can provide additional data. Such as use in Extended Receiver Determination or Extended Interface Determination conditions.
- Mapping Look-Ups
Within mapping step, Business rules can be used to enrich/fetch external system data with effective performance as compared to other options such as Table or RFC look-ups.
BRM can be used to replace Value Mapping and other such Lookups.
- SAP NetWeaver Business Process Management (BPM)
SAP BRM rules can be used within SAP NW BPM to enrich process data or to provide decision criteria for Conditional steps.
What’s Next?
In our next few series of blog we will look at various Design and Maintenance aspects of SAP NetWeaver Process Orchestration Business Rules Management.
- Design and Development of Rule using Rules Composer.
– Build and Deploy rule.
- Access rule from Enterprise Services Repository design artifacts.
- Security and Authorization of BRM rules.
- Testing deployed Rule.
- Rules Manager and rule maintenance.
- Change Log and Version History in Rules Manager.
