1. Online Help
  2. Inventory Discrepancy in Reconciliation Workbench

Inventory Discrepancy in Reconciliation Workbench

You can now consolidate Inventory Discrepancies into one single record per SKU by ignoring Batch/Expiry/Attributes (A to O), reducing duplicate lines, and speeding up reconciliation. The discrepancy computation rules to control how WMS compares inventory balances from WMS and ERP. This helps you reduce duplicate discrepancy lines when an item is tracked with batch, expiry, or inventory attributes in WMS, but not tracked the same way in ERP.

When you define a discrepancy rule, WMS can ignore selected inventory attributes during comparison, add the quantities together for the SKU, and show a consolidated discrepancy result in the Inventory Discrepancies Redwood screen. You can now:

  • Create an Item Summary Rule with the new rule type, Discrepancy computation.
  • Choose which inventory attributes WMS should ignore while comparing WMS and ERP balances. Ignore items that exist in ERP but do not exist in WMS.
  • Use the item_summary_discrepancy_rule parameter in the Generate Inventory Balance Snapshot scheduled job.
  • Add the Discrepancy Rule column in the Inventory Discrepancies Redwood screen to see which rule was used.
  • Generate an Inventory Summary Run Number output file in JSON format so non-Fusion ERP systems can send inventory balances using the correct run number.
  • Configure ERP Cloud SaaS app authentication using either basic authentication or OAuth client credentials.

Before you begin, ensure sure you understand how the rule applies:

  • A discrepancy computation rule applies to all items in the scheduled job run.
  • You cannot apply the rule to only selected SKUs because selection criteria are disabled for this rule type.
  • WMS uses the discrepancy rule only when the scheduled job generates inventory discrepancies.
  • If you leave item_summary_discrepancy_rule blank, WMS retains the existing discrepancy behaviour.
  • If you enter a valid discrepancy rule, WMS uses that rule while comparing WMS and ERP inventory balances.

To Create a Discrepancy Computation Rule, do the following:

  1. Open the Item Summary Rule UI and create a new rule.
  2. In the Type field, select Discrepancy computation.
  3. Review the Summary Type field. WMS disables it for this rule type.
  4. In Ignored Inventory Attribute List, select the attributes you want WMS to ignore during discrepancy comparison, such as batch, expiry, or inventory attributes A to O.
  5. Select Ignore non-existent items if you want WMS to skip items that exist in ERP but do not exist in WMS.
  6. Save the rule.

After you save the rule, run the Generate Inventory Balance Snapshot scheduled job.

Generate Inventory Discrepancies with the Rule

  1. Open the Generate Inventory Balance Snapshot scheduled job.
  2. Enable inventory discrepancy generation for the run.
  3. In item_summary_discrepancy_rule, enter the valid discrepancy computation rule name.
  4. Run or schedule the job.

WMS generates the WMS inventory summary and ERP inventory summary as usual. When it compares the two balances, it applies the discrepancy rule.

For example, if WMS has 5 units in BATCH01 and 5 units in BATCH02, but ERP has 10 units without batch tracking, WMS can ignore batch during comparison. If the total quantity matches, WMS does not show a discrepancy for that SKU.

View the Rule Used for a Discrepancy

  1. Open the Inventory Discrepancies Redwood screen.
  2. Add the Discrepancy Rule column to the grid.
  3. Review the rule shown for the run number.

The column is hidden by default, but you can add it when you need to trace how WMS calculated the discrepancy.

Share the Run Number with a Non-Fusion ERP

  1. Open Output Interface Configuration.
  2. Select the Inventory Summary Run Number interface type.
  3. Configure the endpoint for the output.
  4. Save the configuration.

When the Generate Inventory Balance Snapshot job runs, WMS generates a JSON output file that includes details such as facility, company, run number, WMS summary rule, and discrepancy rule. A non-Fusion ERP can use the run number when sending its inventory summary back to WMS.

Configure ERP Cloud Authentication

For ERP Cloud SaaS app configuration, WMS supports basic authentication and OAuth client credentials.

Use basic authentication when only the basic authentication parameters are populated.

Use OAuth when these values are populated:

  • App Parm3: Client ID
  • App Parm4: Token URL
  • App Parm5: Scope
  • App Parm8: Client Secret

WMS uses OAuth when all required OAuth values are available for the ERP Cloud SaaS app.