This business package supports Process Integration on the basis of the industry standard Chem eStandards, which is part of the Chemical Industry Data Exchange (CIDX) organization.
Process Integration Content in this software component represents interfaces of Chem eStandards as they are defined in the documentation of the standard.
You can access this documentation at http://www.cidx.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. There is exactly one process integration scenario for each CIDX transaction in software component CIDX. Naming convention: <Transaction Name> Example OrderCreate End of the example. |
Service Interface |
Describes the industry standard interface. The service interface references an external definition that describes the schema. Naming convention: <Transaction Name> |
External definition |
Describes the data structure. The external definition contains the uploaded CIDX schema. Naming convention: <Name of the root element in the schema> Example CustomerSpecificCatalogUpdate End of the example. |
Communication channel template |
Contains the technical details about inbound or outbound processing of the message using the CIDX adapter. Naming convention: <Role>_<Activity>_<Transaction Name> Example Buyer_Send_ OrderCreate End of the example. |
ESR Content in this software component represents the mapping from SAP standard interfaces (ERP) to industry standard interfaces.
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 CIDX transaction in software component CIDX ERP. The role refers to the application component that the application represents. End of the note. Naming convention: <Transaction Name>_<Role Name> Example OrderCreate_Buyer End of the example. |
Operation mapping |
Describes the mapping between the source and target interface Naming convention: <Name of source interface>_<Name of target interface> Example DesadvDelvry03_ShipNotice In this case, the source interface is the IDoc DESADV.DELVRY03 and the target interface is the industry standard interface ShipNotice. End of the example. |
Message mapping |
Describes the mapping between the source and target message The same naming conventions apply as for operation mappings. |
Mapping template |
Describes part of a mapping that can be used for defining a message mapping Naming convention: <Outbound Service Interface>_<IDoc Segment>_<Target Service Interface>_<CIDX-Segment> |