SAP PI 7.1 offering to create Models in the Enterprise Service Repository.
SAP Modelling uses ARIS models, modeling focuses on design and ensures reusability, naming conventions, and scalable interaction and integration scenarios. The aim of Modelling is to model business process flows. The model helps you to understand and then to implement the process flows or to enhance an implementation that already exists.
In a service-oriented architecture of business applications, you ideally initially model your application prior to implementation. This means that you can answer fundamental questions such as what components the application comprises of, which services the individual components offer, and how the various different components interact with each other before you begin implementation. A governance process ensures that by using models, all services are always identified and defined in the same way, thus avoiding redundancies.
The models are not system-landscape-specific. Later on, they provide useful information when implementing services, as well as during any configuration that may be required. Furthermore, the models document different aspects of a business process, increase understanding of applications across departments and businesses thereby reducing costs when applications need to be changed or enhanced in a later release.
Business Object: A business object (BO) represents a specific view of data of a well-defined and outlined business area. BOs are identified in such a way that there are no overlaps. Process Component:
Process components group business objects (BOs). A BO belongs to exactly one process component.
An operation is assigned to exactly one BO. Each BO can have more than one operation.
Groups all process components that will later be installed together on the system. To enable these process components to run, it is sometimes necessary to configure the process components of other deployment units, even if this is not ideal.
Different type of models:
Process component model:
The model contains information about what Service Interfaces are used . A Process Component Interaction model shows how different Process Components relate to each other, for instance the message flow between Process Components. The process component model (SAP ProcComp model) is used to describe the inner workings of a process component. You use one or multiple BOs to model the data, you define the operations and service interfaces that the process component uses to access the data/BOs, and you define the operations that are used to access other process components data.
Integration Scenario Models:
Integration scenario models describe which process components belong to which deployment units and how the process components interact with each other in an end-to-end scenario. The integration scenario models give a better understanding of the whole process.
Process Component Interaction Model:
Process component interaction models (SAP ProcComp interaction model) describe the communication between two process components in detail. The model shows all involved BOs, service interfaces, operations, and message types. A process component interaction model can only be used for an Enterprise Service Interaction and there can be none, one, or multiple process component interaction models assigned to one Enterprise Service Interaction.
Business Object Map:
Business object maps (SAP entity map), or business object template maps, aggregate business objects or business object templates in a model for overview purposes. A business object map is an entity map, which is a structured directory of all entities of the main entity types. An entity map for a given application is a structured directory of all deployment units, process components, and business objects in the application. Business object maps are defined for all major applications and are shipped as ESR content.
Integration Scenario Catalog:
Integration scenario catalogs (SAP Scenario Catalog) group and structure all the integration scenarios of a solution and thereby represent the business starting point for process modeling. The contained scenarios and their variants are clustered using integration scenario groups. You can navigate from a catalog to all contained elements. reference: