Common Code Point Isolation Framework - Keep ABAP Development Objects separate for easy maintenance

In an organization, there are different development objects/points like User Exits, BADIs, Enhancement spots, etc, which are provided by SAP with intention to fine-tune the technical run of a business process, to customer needs. However, many of these exit points are common to multiple business areas, and having code belonging to different internal teams in this central/common point creates dependencies, transport locking, high testing efforts, and plethora of other problems in general. At Microsoft, we developed a custom ABAP Framework, called 'Service Isolation Framework (SIF)', which uses dynamic programming to evaluate based on available context variables, AND, based on rules specified in a custom configuration table (Hierarchical Cluster view) to identify the service line/business area, and then use OO-ABAP / Custom BADIs to route the execution flow to development objects under specific team ownership, result in breaking of un-necessary dependencies between teams, avoiding transport object locks, and minimizing the need for massive testing. Furthermore, it also allows performance measures and getting insights on areas of improvement to act on.

[frankberwanger]

Nice. Can you provide the source code of your split framework class?