ProComp Model

Posted on Apr. 14, 2010 at 09.32 PM - Kuala Lumpur, Malaysia

A model-driven development of services is an important aim of service development in a service-oriented architecture for business applications (Enterprise SOA). To this end, the Enterprise Services Builder (ES Builder) offers a modeling environment where you can create various models in the Enterprise Services Repository (ES Repository).

A model-driven service development provides the following advantages:

1. A process should be part of a model-driven process whereby services of new applications are adapted in cooperation with other development departments. No more design objects are created for a model that has not yet been approved. In this way, the model acts as a basis for discussion until it is released for use as a template.
2. Depending on the modeling, you can work out which design objects are necessary in the ES Repository for your application.
3. Models are a good way of documenting the whole process of an application and make it easier to enhance software later.

We use SAP process component model (SAP ProComp model) to model which data the process component works with and which service interfaces are to be offered, as shown below:

Notes:

• Material is the business object
• Material_Out is the service interface
• MaterialFile is the service operation which is contained in the service interface
• Sender_Component is component where this interface belongs to
• For each of the objects in the model, we need to define the assignment into a specific namespace
• We can use the create assignment context menu for each objects in the model to create the objects in the ESR

The advantage of having this model, is that it can be used as a template to create design objects in ES. However, as it does show the interaction with other process component, it can not be used to create configuration objects in the integration builder.

Life is beautiful! Let's make it meaningful and colorful!