X12 940 - SAP S/4 HANA

A search request is performed on SAP S/4HANA for any unprocessed warehouse shipping records. If a sales order record is found, it is parsed based on location code and a matching outbound route is searched for. If a match occurs, the SAP S/4HANA Warehouse Shipping Order JSON is translated to EDI 940 and sent to the trading partner.

This section explains how to configure the integration between SAP S/4HANA to retrieve the warehouse shipping records and transform the EDI X12 940 format for the Trading Partner integration. 

Configure

1. Configure Schedulers: LaunchWarehouseShippingOrderPS is scheduled to run every 1 hour. To adjust these settings, refer to Creating and Defining Process Schedules.
2. SAP S/4HANA. If the sales order is to be converted to EDI 940, then sent to the third-party logistic partners from all the available sales orders in SAP S/4HANA, then configure the custom field SalesOrder CIC STATUS  with a status of Pending. Note: a second custom filter (for example, SOWHFilter = true) used to fetch a sales order to process as EDI 940 to third-party logistic partners must be determined by the customer.
3. Configuration of Outbound Route.

• The Warehouse Sales Order source payload uses SOLD TO PARTY to identify the Trading Partner the 940 is sent. If the record is a sales order, then warehouse location will be used in the look-up against the table SAPHANA_PARTNERS to find the partner id. If the trading partner name doesn't match the tpname, then you must update the Outbound Route to reflect the matching name in the spreadsheet.

4. Configure the EDI Enveloper. The X12 940 envelope details and the trading partner endpoint to which the X12 940 has to be sent should be configured in the partner profile in CIC Cockpit. (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 LaunchWarehouseShippingOrderBPS.
• Automatically run the Scheduler LaunchWarehouseShippingOrderPS.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.  

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

Customize

1. You can change how often Invoices are retrieved from SAP S/4HANA. The LaunchWarehouseShippingOrderPS.sched Scheduler (in com.customer.booster.cim.saphana package) retrieves invoices every 1 hour. You can change this to run more or less frequently. To adjust these settings, refer to the steps in Creating and Defining Process Schedules.
2. Add more details to the X12 940 from the SAP S/4HANA Sales Order.

• 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.