This workflow can be used to understand what the impact will be if a particular object or number of objects are changed.
What may seem like a relatively small change could have a huge impact on both the transactions and the end user's. Understanding that impact before the change is made will help to plan how much regression testing will be required and whether any end users need to be re-trained because of the change.
The workflow needs the list of objects to be changed, as well as the usual two rfc destinations -
1. A QA system for the Where Used action
2. A Prod system for extracting usage and user information.
The results will show which used transactions/programs will be affected and also the users who have used those transactions/programs.