CGPL / IBOM framework
BOL/Genil framework was primarily for Oneorder Dcouments (Read Sales and Service). When Marketing functionality came into picture it was felt that since it would be primarily hierarchical based structure so a Pure BOL/Genil was perhaps not suited/scalable to all Marketing future obejcts and hence a new Framework CGPL came into being which was later enhanced by IBOM layer to make it more generic.
Internal Business Object Model (IBOM) is the counterpart technology to any external Business object model used to
implement the access to the underlying business logic of a BSP or SAP web-based application
A Short Background
The basic idea of the IBOM was developed during the ESA (Enterprise Service Architecture) feasibility study of CRM where it was evaluated how migrate CRM objects to the ESA architecture.
The approach in ESA is having one ESA proxy class for exactly one business object where the whole business logic functionality is covered. That means that the complete data handling for the business object, for all its dependent objects as well as for all associations to other existing business objects is handled in one class, the proxy class.
Here, the idea to build a counterpart of the external business object model internally too was conceived. That is to build an internal business object model and to publish the external business object model on top of it. In between the proxy class and the internal business object model there was a need of a generic layer that delegates the calls automatically using business object model Meta information.
This approach has the following advantages:
• It is a transparent internal BO model.
• the technical implementation of each node doesn’t matter
• the implementation of a node can be re-used in case the access mechanism is the same (e.g. assignments of campaigns & trade promotions)
• enhance able with generic functionality (e.g. CGPL framework used in marketing applications)
• general mapping mechanism between external and internal attributes possible
• abstraction of the complexity of the proxy class interface
• internal BO model is independent from the external BO model as well as the proxy class
• reducing the effort for integrating the application business logic to proxy class
• well-defined implementation framework (each node is implemented the same way)
One Disadvantage:
• Overhead for the generic access logic evaluating the business object model Meta information.
Credits : Harshit Gupta(SAP Mentor) , Sudipta Sarma (SAP LABS)
Internal Business Object Model (IBOM) is the counterpart technology to any external Business object model used to
implement the access to the underlying business logic of a BSP or SAP web-based application
A Short Background
The basic idea of the IBOM was developed during the ESA (Enterprise Service Architecture) feasibility study of CRM where it was evaluated how migrate CRM objects to the ESA architecture.
The approach in ESA is having one ESA proxy class for exactly one business object where the whole business logic functionality is covered. That means that the complete data handling for the business object, for all its dependent objects as well as for all associations to other existing business objects is handled in one class, the proxy class.
Here, the idea to build a counterpart of the external business object model internally too was conceived. That is to build an internal business object model and to publish the external business object model on top of it. In between the proxy class and the internal business object model there was a need of a generic layer that delegates the calls automatically using business object model Meta information.
This approach has the following advantages:
• It is a transparent internal BO model.
• the technical implementation of each node doesn’t matter
• the implementation of a node can be re-used in case the access mechanism is the same (e.g. assignments of campaigns & trade promotions)
• enhance able with generic functionality (e.g. CGPL framework used in marketing applications)
• general mapping mechanism between external and internal attributes possible
• abstraction of the complexity of the proxy class interface
• internal BO model is independent from the external BO model as well as the proxy class
• reducing the effort for integrating the application business logic to proxy class
• well-defined implementation framework (each node is implemented the same way)
One Disadvantage:
• Overhead for the generic access logic evaluating the business object model Meta information.
Credits : Harshit Gupta(SAP Mentor) , Sudipta Sarma (SAP LABS)
Posts
Post a Comment