X12 880 - SAP S/4 HANA

A search is performed on SAP S/4HANA for unprocessed grocery products invoice records. If a record is found, a matching outbound route is searched for. If a match exists, then the SAP S/4HANA Grocery Products Invoice JSON is translated to an EDI 880 and sent to the trading partner.  

This section explains how to configure the integration between SAP S/4HANA to retrieve the Grocery Products Invoices and transform it to an EDI X12 880 format for the Trading Partner integration. 

Configure

1. Process Schedulers: The LaunchGroceryOrderInvoicePS runs every 1 hour. To adjust these settings, refer to Creating and Defining Process Schedules.
2. SAP S/4HANA.  If the Grocery Products Invoice is supposed to be converted to EDI and then sent to the Trading partners from all the available grocery products invoices in SAP S/4HANA, then you should configure the custom field BillingDocument/CIC_Status with a Pending value, and the Grocery status flag should be set to YES.
3. Outbound Route. Outbound Route. In the Shipment source payload, SoldToParty identifies the Trading Partner to whom the 880 should be sent.  SoldToParty is used in the look-up against the table SapHana_Partners to find the trading partner name. Update the Outbound Route settings by providing the appropriate Outbound route BPS in the settings of the transaction spreadsheet.
4. EDI Enveloper. The X12 880 envelope details and the trading partner endpoint to which the X12 880 has to be sent should be configured in the partner profile in 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 LaunchGroceryProductsInvoiceBPS.
• Automatically run the Scheduler LaunchGroceryProductsInvoicePS.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 Outbound EDI validation rules.

Customize

1. You can change the frequency at which Grocery Products Invoices are retrieved from SAP S/4HANA by adjusting the LaunchGroceryOrderInvoicePS scheduler (in the com.customer.booster.cim.saphana.grocery.invoice package). By default, the scheduler retrieves grocery product invoices every 1 hour. To change these settings, refer to Creating and Defining Process Schedules.

2. Add more details to the X12 880 from the SAP S/4HANAInvoice.

• 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