Search Results inv_consigned_validations_grp




Overview
Explore in AI Chat

Overview

INV_CONSIGNED_VALIDATIONS_GRP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an API of type "GRP" (a grouping package). It belongs to the Oracle Inventory (INV) module and serves the consigned inventory business flow — the process by which a buyer holds supplier-owned stock at a warehouse or shop floor location and only takes ownership (and incurs payment liability) at the point of consumption or transfer of control. The package encapsulates validation and quantity-derivation logic used during consigned inventory transactions, helping subledger and receiving processes determine correct consigned, planning, and shortage quantities before transaction processing proceeds. Its status is VALID in both 12.1.1 and 12.2.2 ETRM repositories, indicating a supported, non-obsolete object in the 12.x code line. The "GRP" suffix and the small documented procedure count suggest it is a helper/validation grouping rather than a top-level transaction entry point such as INV_TXN_MANAGER_PUB or a public API package.

Key Procedures and Functions

The ETRM metadata documents five procedures/functions in total, of which three are named: GET_CONSIGNED_QUANTITY, GET_PLANNING_QUANTITY, and GET_PLANNING_SD_QUANTITY. Their documented purposes are quantity retrieval/derivation helpers:

  • GET_CONSIGNED_QUANTITY — Returns the consigned quantity associated with a given inventory item/location context, i.e., the quantity currently held on consignment by the supplier. Used to establish the on-hand consigned balance before validations or ownership transfer logic is applied.
  • GET_PLANNING_QUANTITY — Returns the planning quantity, the quantity considered for planning and supply/demand netting purposes. It allows planning processes to treat consigned stock appropriately (for example, including it in available-to-promise or MRP considerations depending on configuration).
  • GET_PLANNING_SD_QUANTITY — Returns the planning quantity restricted to the shipping/delivery ("SD") dimension, enabling planning calculations that discriminate by shipping/consigned context.

The remaining two documented procedures are not named in the ETRM excerpt; they are presumed internal validation helpers invoked by the three visible functions. No parameter lists are documented, so parameter signatures should not be assumed.

Tables Accessed

The ETRM metadata explicitly documents no direct table references for INV_CONSIGNED_VALIDATIONS_GRP; it records only dependencies on the APPS.FND_API package and the SYS.STANDARD package. FND_API is the standard Oracle Application Object Library API utility package (used for API-level error/return status handling), and STANDARD is the PL/SQL built-in package. This indicates the package is a thin, self-contained computation layer rather than a table-writing package. Its table access, where required, is almost certainly indirect via views/synonyms such as MTL_ONHAND_QUANTITIES, MTL_SUPPLY, or consigned-inventory views maintained by Oracle Inventory — but these are not confirmed by the documented metadata and should be verified by source inspection before being relied upon.

Usage Notes

INV_CONSIGNED_VALIDATIONS_GRP is referenced by one other package, INV_CONSIGNED_VALIDATIONS_GRP (the package body, consistent with the ETRM "[Package Body]" subobject) and by RCV_QUANTITIES_S — the Receiving Quantities PL/SQL package. This reference by RCV_QUANTITIES_S is significant: it confirms integration with the Oracle Purchasing/Receiving consigned quantity calculation flow, where receiving validations must compare ordered, received, and consigned quantities. There is no documented reference from a Forms-triggered path or from a public concurrent program in the ETRM excerpt. Practically, the package is invoked as a helper inside consigned inventory/receiving transaction processing rather than being called directly by end users or custom extensions. Customizations requiring consigned quantity or planning quantity derivation should call the documented functions only after confirming their signatures from the deployed package specification, since the ETRM metadata lists function names without parameter details.