Modelling and Specifying ESR Content 
To make you application callable by services and to integrate it with other applications or business partners, execute the following tasks described below in the Enterprise Services Repository (ES Repository).
If you want to completely redefine and specify the business process, it makes sense firstly to define a process model in the ES Repository. SAP provides different process model types desgined for modelling integration. From the graphical display of a process, you can specify the interfaces, data types, mappings, and other ESR objects involved (top-down approach). The ES Repository provides an integrated tool environment which you can use to navigate seamlessly between models, interface objects, mappings, and other information required for describing the process.
If you use pre-defined ESR content delivered by SAP and want to build on top of it, you will probably only have to specify a part of the process yourself.
More information: Working with Enterprise Service Definitions of SAP
Example
The figure shows a process component interaction model that describes the communication between a service consumer and a service provider. The following assumes that the example case implements the application to be integrated on the provider side.
Procedure
Process Modelling
The ES Repository provides a modelling environment that is completely integrated into the ES Repository. As a result you can navigate from a model to all the other ESR objects involved in the modelled process. In this way you can develop new processes completely according to the top-down approach, navigate to all relevant interfaces, mappings, and data types, and specify further objects, if necessary. Different model types are available to you depending on the application use case. The model types intended for describing integration-relevant details are:
Integration Scenario Model
Represents an entire integration scenario and the connections between the process components involved.
Process Components Interaction Model
Represents the communication between two process components in detail (corresponds to a connection in an integration scenario model). With thismodel type you can display the interaction of all the interfaces, mappings, data types involved in the communication and navigate to the editors for these objects.
More information: Defining Process Components Architecture Models in the ES Repository
You can also work with a modeling environment that was already provided in earlier releases of SAP NetWeaver PI or SAP NetWeaver Exchange Infrastructure. For more information, see: Defining Process Integration Scenarios
NoteYou may want to use and enhance ESR content that was already developed on the basis if earlier releases of SAP NetWeaver PI. In this case, it is possible that process models exist in the form of process integration scenarios that you can build on top of.
End of the note.Define interface objects
With interfaces you define the details for communication between process components. Depending on a service interface, you define the message types and data types used.
More information:
Defining Mappings
If you differentiate the data structure between sender and receiver process components, use mappings for transformations between the outbound and target structure.
More information: Mapping Messages to Each Other Using Mapping Objects
Definings Objects for Preconfiguring Processes
In the ES Repository there are further options for preconfiguring your process. You can define the corresponding objects in the ES Repository and later, when you configure the process for your actual system landscape, use it as a configuration template.
More information: Adapter Objects
Tasks for Business-to-Business Processes
If you would like to integrate business partners and applications in the framework of business-to-business processes (B2B processes), use the procedures described above as a guideline. There are however additional concepts and tasks for B2B integration as described below.
The following application cases are handled below:
Integrating Business Partner on the Basis of Industry Standards
Integrated Smaller Business Partners and Subsidiaries
Integrating Business Partner on the Basis of Industry Standards
To integrate the applications of external business partners based on industry standard, use industry-specific business packages. Business packages are pre-defined ESR content packages which, together with special adapter types, are tailored to the integration based on a specific industry standard.
Business packages contain:
The ESR content predefined for process integration on the basis of industry standards
The technical adapters required to connect to the message protocol supported for the relevant industry standard (for example, the RNIF adapter).
More information: Structure of Business Packages
Essentially the same concepts and procedures are valid for this application case as described above.
The following additional tasks are required for intergation based on industry standards in the modeling and design task area:
Integrated Smaller Business Partners and Subsidiaries
You can integrate smaller business partners and subsidiaries using the SAP Partner Connectivity Kit (PCK). In the PCK, you can configure the required process integration content and the technical adapters. There are no further tasks in the modeling and design task area for this.