In this blog I will explain how to build the Generic EM WebUI profiles to hide the profile items using BRF+.
BRF+ Scenarios for EM Web interface transactions:
BRF+ custom controls are useful when the single EHT and AOT used in multiple business contracts.
Using BRF+ decision table EM webUI selection, display and event message profile items can be hidden dynamically. With this new design multiple EM WebUI profile generation is not required. Accordingly the unused configured fields can be removed dynamically, when it is exposed to various external partners and used by various business entities.
How to build BRF+ application for EM WebUI interface transactions?
Why BRF+ , Why not EM filter profile ?
Standard EM filter profile determines the event handler components that are to be displayed to the user, but not to remove the empty configured fields (filtered) being displayed in EM webUI.
Designing Selection profile control using BRF+
Step1: Design the generic DDIC structure using selection profile and security role
Structure components: User Profile Identifier
Selection Profile
Configured Field
Role Name
Output : result indicator
Step 2: Design the BRF+ data object using the structure defined in step1 .
Step3: Build BRFplus selection profile decision table using the objects defined in step 1
BRF Decision table elements = selection profile DDIC structure
Result object = Yes/No field indicator
Step 4: Create the BRF plus function object with top expression as decision table and output as result indicator.
Step5: Create the decision table entries as shown below
Create entries with user profile, selection profile, configured field , user role and maintain the relevancy indicator.
Step 6: Create enhancement in FM /SAPTRX/UC_GET_USERPROFILE and apply the below steps to validate the selection profile items when it is triggered by user WebUI selection.
Designing display profile control using BRF+
Execute all the steps (mentioned above) for selection profile; and replace the selection profile with Display profile (/SAPTRX/UCDPID).
Decision table view
Designing Event Reporting Message profile control using BRF+
Similarly follow the steps as of selection profile, replace the selection profile with event message Profile (/SAPTRX/UCEVTRID) and configured field with event code (/SAPTRX/EVENT_CODE).
Decision table view
Alternatively above mentioned BRF+ solution can also be achieved using custom SPRO configuration enabled with user role mapping. DDIC DB view is required between AGR_USERS and newly created custom table. This view can be used in FM /SAPTRX/UC_GET_USERPROFILE enhancement by applying the same logic.
Note: DDBV (Dynamic Database View) can be used in BRFplus, if EM is running on HANA environment.
Using BRF+ decision table TM AOT extractor functions can also be generic in future along with the addition of few configuration elements and key/org data maintained in the BRF+ application.
How to use BRF+ in TM/EM integration and event propagation
BRF+ decision tables can be used in TM/ECC EM data extractors using document type/KDS with single AOT/EHT integration as follows:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |