X12 856 - SAP S/4 HANA

A search request is performed on SAP S/4HANA to look for any unprocessed shipment records. When a record is found, it is parsed, and the matching outbound route is searched. If a match is found, the SAP S/4HANA Shipment JSON is translated to EDI 856 and sent to the trading partner.

This section explains how to configure the integration to:

• retrieve the shipment records
• transform the EDI X12 856 format for the Trading Partner integration.

Configure

1. Configure BP Schedulers: LaunchOutboundDeliveryPS is scheduled to run every 1 hour. See Creating and Defining Process Schedules for more details.
2. Configure SAP S/4HANA: If the shipment record is to be converted to EDI and sent to trading partners from all available outbound deliveries in the SAP S/4HANA, then the custom field OutboundDelivery/CIC_Status should be configured with the value Pending. The field value updates to Completed once the flow runs successfully. 

3. Configure the Outbound Route.

   In the outbound delivery source payload, SoldToParty identifies the Trading Partner to whom the 856 is to be sent. This is used in the look-up against the table “SapHana_Partners” to find a trading partner name; if name does not match the tpname (during project creation with the wizard), then you must update the Outbound Route to reflect the matching name. 

4. Configure the Enveloper. The X12 856 envelope details and the trading partner endpoint to which the X12 856 has to be sent should be configured in the partner profile on CIC Cockpit. (Network>Partners>Transactions>Settings.)

Run the Flow

1. Before proceeding, ensure that the following Projects have been deployed. If any of these Projects are already deployed and remain unmodified, there is no need to redeploy them. Similarly, if any of these Projects were not checked out to your Workspace, they can be skipped from the deployment process.

• com._customer_booster.cim.saphana
• com._customer_.cim.saphana
• com.cleo.customer.edi
• com.cleo.b2bcloud.core
• com.cleo.b2biaas.clarify
• com.cleo.cic.cim.cockpit.rulesets
• com.cleo.cic.cim.schemas
• com.cleo.cic.cockpit.core
• com.cleo.cic.connector.saphana
• com.cleo.cic.pt.api
• com.cleo.cic.pt.edi.schemas
• com.cleo.cic.util

2. Run the flow either manually or automatically:

• Manually run the Business Process flow by launching LaunchOutboundDeliveryBPS.
• Automatically run the Scheduler LaunchOutboundDeliveryPS.sched to execute the flow based on the specified interval.

3. Monitor the flow by using the following

• CIC Studio Auditor log entries
• CIC Cockpit views: Messages, Jobs, Dashboard>Charts

In case of errors: If any of the processing steps fail, a ticket is created with the details; the same is visible in the CIC Cockpit's Message and Job views with the Issue Flag.  Below is an example of a job error.

For Outbound EDI validation use cases, see Validation Rules in the Transformation Settings object for Outbound EDI validation rules.

Customize

1. Change the intervals of how often Item Fulfillments are retrieved from the SAP S/4HANA

   The LaunchOutboundDeliveryPS BP Scheduler (in the com.customer.booster.cim.saphana package) is configured to retrieve shipment records every 1 hour. You can change the schedule to run more or less frequently. Steps to do this are described in Creating and Defining Process Schedules.

2. Add more details to the X12 856 from the SAP S/4HANA Outbound Delivery.

• The values that are being mapped are documented in the Integration Design Spec template.
• Contact Cleo support if you need any assistance while adding additional rules.