New prebuilt integration for inventory reconciliation using file-based processing

WMS supports serial-level inventory reconciliation by fetching ERP on-hand and serial number information through the File-Based processing flow. We’ve improvised ERP-to-WMS inventory reconciliation for serial-tracked items by introducing a dedicated prebuilt integration for serial-number data. In 26D, WMS uses a separate ERP serial inventory payload to process serial number details more efficiently and support serial-level reconciliation between WMS and ERP Inventory. The reconciliation process captures inventory details by item, quantity, ERP bucket, batch, attribute, serial number, and serial count combinations. .

For serial-tracked items,

  • WMS introduces erp_inv_summary_serial_list prebuilt integration to receive serial-level inventory information from Fusion.
  • The integration uses the ERP On-Hand Reference Number (erp_on_hand_ref_nbr) and Run Number (run_nbr) to associate serial data with the corresponding inventory synchronization run.
  • After WMS receives the ERP on-hand and serial information, WMS links the serial tracked records with the related ERP inventory summary data and compares them with WMS inventory records. Customers can then review serial-level Inventory Discrepancies in Reconciliation Workbench.

How Does This Work:

  1. WMS fetches ERP on-hand inventory information from ERP.
  2. WMS supports a separate ERP serial number payload for serial-tracked inventory.
  3. The serial payload captures item, quantity, ERP bucket, batch, attribute, serial number, and serial count details.
  4. WMS compares ERP inventory and WMS inventory to identify serial-level discrepancies.

Introducing ERP Job Reference Number in ERP Inventory Summary and ERP Serial Number Payloads

When ERP sends inventory summary and serial number information to WMS, WMS needs a reference number to identify the reconciliation run used to compare ERP inventory with WMS inventory. In the prebuilt integration flow, OIC may not have the WMS run number context when sending data back to WMS.

To address this, WMS is now enhanced to accept the ERP job reference number in the ERP Inventory Summary and ERP Serial Number payloads:

  • Introducing a field 'erp_job_reference_nbr' in both the ERP Inventory Summary interface and the ERP Serial Number interface. This reference number helps WMS identify the ERP job associated with the inventory data and link the payloads to the correct reconciliation run.

NOTE: User must send either run_nbr or erp_job_reference_nbr in the ERP Inventory Summary and ERP Serial Number payloads. If both are sent together, WMS fails the interface with an error.

When the ERP integration trigger type is PREBUILT, WMS updates the wms_erp_inv_discrepancy_hdr with the erp_job_reference_nbr after the Generate Inventory Summary schedule job runs using the following API:  POST.../entity/wms_erp_inv_discrepancy_hdr/set_erp_job_reference_nbr

This helps WMS compare the correct ERP on-hand information against the correct WMS inventory balance.

  • The prebuild integration API also includes include_serial_nbrs and partial_sync_flg to determine whether serial number details are required or indicate the inventory synchronization is a partial sync, where it captures only the updated inventory from the previous run instead of fetching the entire ERP on hand.

Configure the ERP Inventory Summary Integration

When users run the Generate Inventory Balance Snapshot schedule job, WMS invokes the Fetch Item Quantity Summary integration to retrieve ERP on-hand inventory details. This integration is version-based, therefore, customers need a way to control which integration version WMS should call, especially when the WMS version and integration package version are not upgraded at the same time. To supports this, a new company-level parameter is erp_inventory_summary_integration_version is introduced to define the ERP Inventory Summary integration version used by the Fetch Item Quantity Summary integration package.

Example 1: A customer upgrades WMS to 26D and uses the 26D ERP Inventory Summary prebuilt integration. The company parameter erp_inventory_summary_integration_version is set to lgf26d. WMS invokes the 26D integration when the Generate Inventory Balance Snapshot schedule job runs. The FBDI based ERP on hand summary is available only from 26D.

Example 2: If customer wants to continue using a previous integration package version, then set erp_inventory_summary_integration_version to lgf26C. WMS invokes the integration version configured in the company parameter.

NOTE: 

  •   WMS uses the erp_inventory_summary_integration_version company parameter to determine which ERP Inventory Summary integration version to invoke.
  •   The default value is lgf26d. Customers can configure version, such as lgf26C, in this parameter for the 'Fetch Item Qty Summary integration package'.
  •   When the parameter to lgf26d, WMS invokes the 26D FBDI-based integration to fetch the ERP on-hand summary.
  •   If the parameter contains an invalid value, WMS does not invoke the integration.

Steps to enable and configure

  1. The prebuilt ERP Inventory Summary Serial List integration must be configured as part of the ERP-to-WMS inventory reconciliation integration.
  2. Ensure required Inventory integrations are configured.
  3. Configure the company parameter erp_inventory_summary_integration_version = lgf26d to use the 26D integration version.

NOTE: You can set the parameter to different supported version only when your integration package requires it.

  1. Configure the generate_erp_inv_summary_trigger_type = prebuilt, to involve the prebuilt integration.

NOTE: For a non-oracle system, users can set the parm value to non-Oracle

  1. Run the Generate Inventory Balance Snapshot schedule job.
  2. Ensure ERP Inventory Summary and ERP Serial Number payloads use the correct reference value:
    1. Use run_nbr, or
    2. Use erp_job_reference_nbr.

NOTE: Do not send both run_nbr and erp_job_reference_nbr in the same ERP Inventory Summary or ERP Serial Number payload.