Show TOC

Background documentationOverview of Modeling Locate this document in the navigation structure

 

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

  • 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.

There are two modeling environments in the Enterprise Services Repository:

  • Process Components Architecture Models

    SAP works with this environment to create models for applications in the SAP Business Suite. These models are shipped to customers. You can create your own models in the ES Repository.

    More information: Basics of Process Component Architecture Models

  • Process Integration Scenarios

    This modeling environment in the ES Repository was part of previous SAP NetWeaver PI releases and continues to be supported in the latest release. It concentrates on the modeling of the exchange of messages between application components.

    More information: Process Integration Scenarios