Configure Reference Tables and Global Variables - SAP S4/HANA

These steps are required before using the SAP S4/HANA Accelerator. They include the configuration of:

• Reference Tables (Partners and Products)
• Global Variables

Configure Reference tables (Partners)

Configure the Cleo-provided Reference Table using the steps described below.  Additional information can also be found in Viewing and Editing Reference Tables in CIC Cockpit.

1. Run CreateSapHanaPartnerRefTableBPS.bps (in Project com.customer.booster.cim.saphana, package com.customer.booster.cim.saphana.partner). To verify if the setup is complete, always refer to the Auditor logs, which will display step-by-step information. Errors (such as driver issues or connection issues) are displayed in the auditor logs, in which case you must take necessary corrective action before running the BPS again. 

• If the process ends successfully, a table named SapHana_Partners will be visible in the Cockpit. You should now manually add the _partner id and _partner name for the corresponding customer records (shown below).
• Note the significance of the columns:
  • _partner name captures the partner name the partner is identified.
  • _partner id captures the EDI X12 id assigned to a partner. E.g., an 850 X12 TP document would have sender id as the trading partner id (located in ISA06).
  • SoldToParty id is the SAP-assigned id for the customer entity record.

Configure Reference tables (Products)

Run the CreateSapHanaProductsRefTableBPS Business Process (in Project com.customer.booster.cim.saphana, Package com.customer.booster.cim.saphana.products). To verify if the setup is complete, always refer to the Auditor logs, which will display step-by-step information. Errors (such as driver issues or connection issues) are displayed in the auditor logs, in which case you must take necessary corrective action before running the BPS again. 

If the process ends successfully, the table SapHana_Products will be visible in the Cockpit.

You should then launch the LaunchProductsBPS Business Process (in the package com.customer.booster.cim.saphana.products). This will pull all the records from ERP and insert the product details into the SapHana_Products reference table.

Configure Global Variables

• SAPVault: This variable contains the vault entry name assigned to the SAP Connector.
• SleepInterval: This variable contains the sleep time (in milliseconds). This timer is used to retry certain APIs that are throttled.
• HttpErrorCodesToBeIgnoredForTicketCreation:  This is used to identify HTTP error codes that need to be flagged as ‘successful job flows’ in the cockpit. If not mentioned here, the error codes would be flagged as failed jobs in the cockpit. In case a SAP S/4HANA API request is throttled (i.e., with HTTP 429 Too Many Requests error), the execution waits as per the time period configured in Global Variable - SleepInterval, and the API request is made again. Since we have a retry logic for throttled requests implemented in the accelerator, these jobs need not be marked as failures, and hence this global variable is configured with the default value of the throttling error code (429). Default value: 429
• B2BCloudGV: Configure B2BCloudAdminEmail (receiver) and B2BCloudHostEmail (sender) variables in com.cleo.b2bcloud.core.B2BCloudGV. These are resolved during failures, and emails are triggered.