Publish Inventory On-Hand Balances to an External System

You can publish the inventory on-hand balance snapshots from Oracle Inventory Management to an external system.

Perform these steps in Oracle Inventory Management:

1. Configure the external system lookup.

   Use the ORA_INV_BALANCES_INV_EXTERNAL lookup to define the external systems that can receive inventory on-hand balance snapshots.

   Oracle Warehouse Management is the default external system. When adding another external system, use a numeric lookup code greater than 0.

   Configuration	Details
   Lookup name	ORA_INV_BALANCES_INV_EXTERNAL
   Seeded external system	Oracle Warehouse Management
   Reserved lookup code	0, reserved for Oracle Warehouse Management
   New external system lookup codes	Numeric values only, for example 1 or 2

   After the lookup is configured, the external system appears in the External System parameter list for the scheduled process.

2. Submit the Publish Inventory On-Hand Balances to an External System scheduled process.

   Use the following parameters:

   Parameter	Definition
   External System	Select the external system to which the on-hand balances will be sent.
   Organization	Select the organization for which the on-hand balance snapshot will be generated.
   Publish from Date	Specify the date from which on-hand balances will be considered. Use this field to include the data from a period prior to the last successful publication date.
   Items to Publish	Select Nonserial Controlled Items, Serial Controlled Items, or Both.
   Full Publish	Yes: Select to publish all records regardless of the Publish from Date. No: Select to publish only the changes in item balances since the last successful publication.

3. Generate the on-hand balance snapshot.

   After the scheduled process is submitted, Oracle Inventory Management retrieves the inventory on-hand data based on the selected parameters, writes the data to a pipe-separated values file, compresses the file into a ZIP file, and uploads the ZIP file to WebCenter Content.

   The generated output is a standardized flat-file snapshot. The PDF describes the output as a CSV .psv file, and the example file is pipe-separated. For implementation, treat the generated data file as a pipe-separated values file inside a ZIP archive.

4. Validate the scheduled process completion.

   Confirm that the scheduled process completes successfully and that the generated ZIP file is available on WebCenter Content for the selected external system.

5. Schedule the process as needed.

   Define the schedule based on reconciliation frequency, inventory volume, and downstream processing capacity. This is a snapshot-based reconciliation flow, so the cadence should align with the business reconciliation windows rather than the real-time transaction processing.