Easy Enhancement Workbench
The Easy Enhancement Workbench is a development tool with which SAP applications (called Business Objects in the following document) can be extended in a simple manner.
Customer enhancements to a Business Object are defined via wizards. The Workbench then does all development work for the user; databank tables, screens and application logic are created automatically. Finally the customer enhancement is included in the SAP standard.
This also allows users without ABAP knowledge the simple possibility of extending the SAP standard.
An extension created using the Easy Enhancement Workbench does not differ technically from one created manually. In both cases transportable ABAP objects are created and the same Customer Exits, Business Transaction Events or BAdIs are implemented
The difference lies exclusively in the manner in which the objects required are created. The automation offered by the Easy Enhancement Workbench is achieved by template objects that are adapted to the extension definition and created by a generator.
The functionality of the Easy Enhancement Workbench is therefore only available for specially prepared Business Objects, mainly from the CRM environment.
The type of extension is also predefined In most cases the customer is offered the possibility to add user-defined databank tables or fields.
In most cases the extension takes place system-wide. For example, when extending a Business Object in the CRM the data exchange to the connected SAP system is extended and a new table is also created in the SAP system.
The system landscape must be set up in order to be able to use system-wide generation. The system landscape must be set up in order to be able to use system-wide generation.
Cross-application components →General application functions → Easy Enhancement Workbench →Maintain system landscape.
Structure of the Easy Enhancement Workbench
To make use of the Easy Enhancement Workbench as simple as possible, we returned to the well-known concept of the ABAP Workbench; the screen allocation and navigation are identical.
The hierarchy of the object list is adapted to the structure of a customer project:
The project is at the highest level. A project combines several enhancements and offers the possibility of defining the project documentation and community. All generated objects belonging to a project are transported together; it is not possible to transport an individual enhancement. Additionally, the package (development class) of the generated objects is determined in the project.
Enhancements are displayed at the next level. An enhancement refers to a business object and an enhancement type. The definition of the enhancement takes place via business-object-specific wizards. Enhancements can also be documented.
When an enhancement has been defined and generated, the object type PostProcessing typically appears at the next level. These are activities that must be executed manually by the user. An enhancement is only considered to be ready when it has been generated correctly and all required PostProcessing activities have been executed.
In order to facilitate monitoring of the generation and to make the technical flow transparent, all generator calls are displayed as tasks in the object list. After an enhancement has been generated all generated objects in a task are visible and can be displayed by double-clicking them.
Additionally, all described object types have an error log that permanently stores errors that have occurred and displays them
The Easy Enhancement Workbench is a development tool with which SAP applications (called Business Objects in the following document) can be extended in a simple manner.
Customer enhancements to a Business Object are defined via wizards. The Workbench then does all development work for the user; databank tables, screens and application logic are created automatically. Finally the customer enhancement is included in the SAP standard.
This also allows users without ABAP knowledge the simple possibility of extending the SAP standard.
An extension created using the Easy Enhancement Workbench does not differ technically from one created manually. In both cases transportable ABAP objects are created and the same Customer Exits, Business Transaction Events or BAdIs are implemented
The difference lies exclusively in the manner in which the objects required are created. The automation offered by the Easy Enhancement Workbench is achieved by template objects that are adapted to the extension definition and created by a generator.
The functionality of the Easy Enhancement Workbench is therefore only available for specially prepared Business Objects, mainly from the CRM environment.
The type of extension is also predefined In most cases the customer is offered the possibility to add user-defined databank tables or fields.
In most cases the extension takes place system-wide. For example, when extending a Business Object in the CRM the data exchange to the connected SAP system is extended and a new table is also created in the SAP system.
The system landscape must be set up in order to be able to use system-wide generation. The system landscape must be set up in order to be able to use system-wide generation.
Cross-application components →General application functions → Easy Enhancement Workbench →Maintain system landscape.
Structure of the Easy Enhancement Workbench
To make use of the Easy Enhancement Workbench as simple as possible, we returned to the well-known concept of the ABAP Workbench; the screen allocation and navigation are identical.
The hierarchy of the object list is adapted to the structure of a customer project:
The project is at the highest level. A project combines several enhancements and offers the possibility of defining the project documentation and community. All generated objects belonging to a project are transported together; it is not possible to transport an individual enhancement. Additionally, the package (development class) of the generated objects is determined in the project.
Enhancements are displayed at the next level. An enhancement refers to a business object and an enhancement type. The definition of the enhancement takes place via business-object-specific wizards. Enhancements can also be documented.
When an enhancement has been defined and generated, the object type PostProcessing typically appears at the next level. These are activities that must be executed manually by the user. An enhancement is only considered to be ready when it has been generated correctly and all required PostProcessing activities have been executed.
In order to facilitate monitoring of the generation and to make the technical flow transparent, all generator calls are displayed as tasks in the object list. After an enhancement has been generated all generated objects in a task are visible and can be displayed by double-clicking them.
Additionally, all described object types have an error log that permanently stores errors that have occurred and displays them
No comments:
Post a Comment