This section tells the merchant how to configure Oracle Integration Cloud Service for this specific integration. The intent of this document is not to give the details on how to configure connections and integrations on Oracle Integration Cloud Service in general. Refer to the Oracle Integration Cloud Service documentation on how to configure connections and integrations.
The integration mappings and the files associated are available to the merchant in the form of packages. These packages once imported into the Oracle Integration Cloud Service infrastructure are ready to be used by the merchant.
The Commerce team already has a Commerce adapter available on the Oracle Integration Cloud Service. The generic SOAP adapter is a generic adapter provided by the Oracle Integration Cloud Service infrastructure for processing the SOAP based messages. As the Order Management Cloud sends the messages in SOAP format, this adapter is used.
The integration package, OracleCommerce-OrderManagementIntegration.par, is available on My Oracle Support. The package contains:
Connections:
Oracle Commerce Cloud: This is the connection to the Commerce Cloud admin server
Oracle Commerce Cloud Agent: This is the connection to Commerce Cloud agent server
Oracle Order Management Cloud: This is the connection to Order Management Order sync service
Oracle Order Management Cloud Events: This is the connection to Order Management events
Oracle Order Management Cloud Order Information Service: This is the connection to Order Management Order retrieval service
Lookup configuration: The mappings for the Return status, Carrier information and Shipping information are updated as part of the lookup configuration. The merchant would need to modify these as per the merchant needs and as configured on the Order Management system. Please refer to the integration settings to view the lookups used.
Integrations:
Order sync from Commerce to Order Management
Return sync from Commerce to Order Management
Order and Return status sync from Order Management to Commerce Cloud
Unpack the OracleCommerce-OrderManagementIntegration.par package. It unpacks into 3 inventory archives (IARs). Unpack each IAR and update the following constants. Update the following constants for Order sync from Commerce to Order Management flow and import using Oracle Integration Cloud Service mapper in Oracle Integration Cloud Service.
XSL location:
<Unpacked iar>/ icspackage/project/ORDE_SYNC_FROM_COMM_TO_ORDE_MGMT_01.00.0000/resources/processor_859/resourcegroup_755<xsl:variable name="SOURCE_SYSTEM" select="'ATG'" xml:id="id_2076"/><xsl:variable name="BUSINESS_UNIT_IDENTIFIER" select="'204'" xml:id="id_2077"/><xsl:variable name="LEGAL_UNIT_IDENTIFIER" select="'204'" xml:id="id_2078"/><xsl:variable name="FULFILLMENT_ORG_IDENTIFIER" select="'207'" xml:id="id_2079"/><xsl:variable name="INVENTORY_ORG_IDENTIFIER" select="'207'" xml:id="id_2080"/><xsl:variable name="UOM_CODE" select="'Ea'" xml:id="id_2081"/>Update the following constant for Return sync from Commerce to Order Management flow and import using Oracle Integration Cloud Service mapper in Oracle Integration Cloud Service.
XSL location:
<Unpacked iar>/icspackage/project/RETU_SYNC_FROM_COMM_TO_ORDE_MGMT_01.00.0000/resources/processor_52/resourcegroup_913<xsl:variable name="SOURCE_SYSTEM" select="'ATG'" xml:id="id_2076"/><xsl:variable name="BUSINESS_UNIT_IDENTIFIER" select="'204'" xml:id="id_2077"/><xsl:variable name="LEGAL_UNIT_IDENTIFIER" select="'204'" xml:id="id_2078"/><xsl:variable name="FULFILLMENT_ORG_IDENTIFIER" select="'207'" xml:id="id_2079"/><xsl:variable name="INVENTORY_ORG_IDENTIFIER" select="'207'" xml:id="id_2080"/><xsl:variable name="UOM_CODE" select="'Ea'" xml:id="id_2081"/>Note: The connection details that come as part of the integration package are empty. The details of the connection are to be filled by the merchant. Once the connection details are filled in and the connections are tested, enable the integration.
