Consignment#

Consignment inventory is physically on-site but owned by someone else — typically a supplier delivering just-in-time to the floor, or a customer whose material we’re building into their assemblies.

Two directions#

• Supplier consignment — supplier owns it until we consume it into a WO. On consumption, ownership transfers and an AP accrual is created.
• Customer consignment — customer owns it while we hold it. Consumption happens when we ship product built from it; no AP impact, but consumption events feed the customer usage report.

Data#

Consignment metadata sits alongside INVT — a location or a specific serial / lot is flagged as consigned, with a counterparty key. ConsignmentHelper is the central helper; ConsignRecHelper covers the receipt side; BcReceivingHelper handles bar-code / scanner-driven flows.

Business rules#

• Consigned stock never posts to the inventory-asset account on receipt.
• Consumption (issue-to-WO for supplier consignment, ship for customer consignment) is the trigger for any GL / AP effect.
• Cycle counting a consigned location produces a report — variances are settled with the counterparty, not written off internally.
• A part can be both consigned (in some warehouses / bins) and owned (in others). The reservation logic in Kitting must prefer owned stock unless a policy flag says otherwise.

Where it lives#