Is your Firefighter Controller reviewing every activity in detail? Does he/she review the most critical business transaction codes?
Firefighter controller log review is the same challenge for one of our clients. The FFID logs will be regularly reviewed, but they want to segregate the FFID usage from the most critical transaction code usage for detailed analysis. They have identified around 100 transaction codes as part of this exercise, and any use of these transaction codes by the FFID must be subjected to additional review after reviewing by the FF Controller.
Due to the lack of routing conditions, the standard process ID – Firefighter Log Report Review Workflow (SAP_GRAC_FIREFIGHT_LOG_REPORT) doesn’t meet this requirement and needs additional customization.
Is there a way to automate firefighter controller log review? Yes, of course. This is what we delivered:
In order to maintain the custom transaction codes, we created a custom table and a TMG. As a result, our customer does not have to modify the Decision table every time.
- A BRF+ DB lookup has been created.
- Custom BRF+ decision tables have been created to return the value.
- Created two different MSMP paths with appropriate stages
- Defined MSMP routing conditions according to business needs
The review and approval process is now fully automated, and if the user has executed any critical transaction codes, the Log review request is assigned to the “Internal Review Board (IRB)” after the controller review.
Are there any additional automations that can be performed with the FF Log Review?
Additionally, an enhancement can be provided to identify if the user has entered any critical transaction codes on the Reason code screen.
ToggleNow also implemented BOT-based automation to review logs. Get in touch with our SMEs today! Visit our automation stories to know various automations that are delivered by ToggleNow team.
