Using Predefined Integration Content
You have the option to start an integration development project using integration content predefined by SAP. There is a lot of predefined content already available that can be reused and which helps customers to save time and effort in their integration development projects. Typically, customers do not use predefined content 1:1 without adapting it to their needs. A typical use case is that customers use data types, service interfaces, and mappings provided by SAP and build their own process model based on these entities, enriched by interfaces and mappings developed on their own. Another option is to use a predefined process model (and all underlying entities) where only one side of the communication is specified, and to specify the other part of the communication at the customer side.
The central location to browse for predefined integration content is the Enterprise Services Workplace (ES Workplace). You can access the ES Workplace in SAP Community Network at https://www.sdn.sap.com/irj/sdn/explore-es .
The term enterprise service is used to emphasize the fact that the ES Repository contains services that were designed according to SAP's SOA design principles. Technically, this term summarizes interface objects. In this document, we intend to name these objects in particular, that is, as service interface, message type, or data type. Integration content published on the ES Workplace was designed based on integration scenario models and process components interaction models. In addition to this content, SAP also provides integration content that was designed based on "classic" process integration scenarios.
Before customers can use and enhance predefined content, they have to download it from SAP Service Marketplace and import it into the ES Repository installed in their landscape. The corresponding location on SAP Service Marketplace is the SAP Software Distribution Center at
http://service.sap.com/swdc
Download 
Support Packages and Patches Entry by Application Group SAP Content ESR Content (XI Content). 
Customer modifications of predefined integration content must not be executed in an imported SAP software component: They must be performed in a separate software component instead.
This avoids conflicts with subsequent SAP software updates since changes to an SAP software component will be immediately overwritten when SAP software updates are imported.
Therefore, to be able to use predefined integration content provided by SAP, you have to create an own software component version for your developments. The new software component version has to include the SAP software component (that contains the predefined content) as the underlying software component version. To do this, define a “based-on” relationship between the new software component and the SAP software component.
More information: Underlying Software Component Version
When you use process integration content for SAP applications, make sure that there is an unambiguous (1:1) relationship between the corresponding software component version in the ES Repository and the corresponding software component version in the SAP system. This is the same for the support package. This means, the versions of both, software component version and support package number, need to be kept in sync in ES Repository and the SAP system. They have to be installed and maintained synchronously.
More information: Managing Enterprise Services Delivered by SAP