Business Package for RosettaNet

This business package supports Process Integration on the basis of the industry standard RosettaNet.

Contents of the Software Component ROSETTANET

ESR content (Process Integration content) in this software component represents RosettaNet partner interface processes (PIP). You can access the documentation for this industry standard at http://www.rosettanet.org.

The following table provides an overview of which object types (ES Repository) represent which parts of the industry standard. Furthermore, the naming conventions used are broken down into their different parts.

Object Type	Description and Naming Convention
Process Integration Scenarios	Describes the process independently of the application that is mapped with the industry standard. The role of the application component corresponds to the role in the business operational view (see Business Operational View in the PIP specification). There is exactly one process integration scenario for each RosettaNet PIP in software component ROSETTANET. Naming convention: <PIP Name> Example PIP0A1 End of the example.
Action	Represents a business activity within a PIP. Naming convention: <Name of the Business Activity in the Business Flow Diagram> (see Business Operational View in the relevant PIP specification) Example Distribute Notification of Failure End of the example.
Service Interface	Represents the business action in the business operational view Naming convention: <Business Action Name> (see table Business Action –Business Document Mapping in the relevant PIP specification ® Column Maps To Business Document in BOV)
External definition	Represents the structure of the exchanged data Naming convention: <Name of root element in corresponding DTD file> You can download the DTD file together with the PIP specification from the RosettaNet Internet site. Example Pip0A1FailureNotification End of the example.
Communication channel template	Contains the technical details about inbound or outbound processing of the message using the RNIF adapter. Naming convention: <Role>_<Send/Receive>_<Name of the service interface> Example Buyer_Receive_PurchaseOrderConfirmationAction End of the example.

Contents of Software Component ROSETTANET ERP

ESR Content in this software component represents the mapping from SAP standard interfaces (ERP) to the industry standard RosettaNet.

Object Type	Description and Naming Convention
Process Integration Scenarios	Describes the process depending on the application that is mapped with the industry standard, and depending on the role (Buyer or Seller). Note There are two role-specific process integration scenarios for each RosettaNet PIP in software component ROSETTANET. The role refers to the application component that the application represents. End of the note.
Action	See entry in table Contents of Software Component ROSETTANET.
Operation mapping	Describes the mapping between the source and target interface Naming convention: <Name of source interface>_<Name of target interface> Example OrdersOrders05_PurchaseOrderRequestAction End of the example.
Message mapping	Describes the mapping between the source and target message The same naming conventions apply as for operation mappings.