Results for “inv_globals”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

INV_GLOBALS is a foundational PL/SQL specification package in the Oracle E-Business Suite Inventory module, declared with AUTHID CURRENT_USER and owned by the APPS schema. Its principal business role is to act as a centralized repository for application-wide constants and session-level global variables used throughout Oracle Inventory and its dependent modules. Rather than scattering literal transaction type identifiers, organization identifiers, and control-mode flags across individual packages, the Inventory development framework consolidates them here so that all calling programs reference a single, authoritative definition.

The package header in the ETRM metadata shows the source lineage header INVSGLBS.pls 120.1, dated 2005, underscoring that this is long-standing core infrastructure carried forward into both 12.1.1 and 12.2.2. The most prominent content evidenced by the search term g_sourcetype_wip is the block of Transaction Type constants, which map friendly names to the numeric TRANSACTION_TYPE_ID values stored in the inventory transaction tables. These include G_TYPE_XFER_ORDER_WIP_ISSUE (35), which corresponds to the WIP-related source type used when material is issued from a transfer order to a Work in Process job, along with adjacent constants such as G_TYPE_XFER_ORDER_ISSUE (63), G_TYPE_XFER_ORDER_SUBXFR (64), and G_TYPE_TRANSFER_ORDER_STGXFR (52). The g_sourcetype_wip naming convention reflects the MTL_TRANSACTION_TYPES source type column, which distinguishes WIP, Purchasing, Sales Order, and Inventory-originated movements.

Key Procedures and Functions

ETRM documents eleven callable units in this package. Their purposes are as follows:

  • GET_ENTITIES_TBL — Used by the generator utility to retrieve defined entity constants, preventing the overriding or duplication of existing entity values during code generation.
  • IS_ISSUE_XFR_TRANSACTION — Evaluates whether a given transaction qualifies as an issue or transfer movement, returning a boolean-style result for downstream branching logic.
  • INIT_CONTROL_REC — Initializes the package's control record, resetting session globals such as organization, call mode, and maximum line number to a known state.
  • EQUAL — Provides a generalized equality comparison helper used consistently across Inventory validation routines.
  • SET_ORG_ID — Establishes the current operating organization identifier in the package global, ensuring transaction context is set before processing.
  • SET_PJM_ORG_ID — Sets the project manufacturing (PJM) organization context, supporting Project Manufacturing-enabled Inventory flows.
  • NO_NEG_ALLOWED — Determines whether negative balances are prohibited for the current context, enforcing Inventory negative-balance control policy.
  • LOCATOR_CONTROL — Returns the locator control setting in force, governing whether a locator must be supplied for a transaction.
  • GET_LEDGER_INFO — Retrieves ledger and accounting-period information required for costing and accounting entries.

Tables Accessed

The documented table references are limited but meaningful. HR_ORGANIZATION_INFORMATION is queried to resolve organization classification details — for example, confirming whether an operating unit is a valid Inventory or Project Manufacturing organization when SET_ORG_ID or SET_PJM_ORG_ID executes. PLITBLM is the standard Oracle PL/SQL index-by table type (table of BINARY_INTEGER) dependency generated by the PL/SQL compiler and exposed through a synonym; it underpins the associative array parameters and internal collections used by the package. No transactional DML against inventory balances is performed here.

Usage Notes

INV_GLOBALS is referenced by 123 other packages, making it one of the most heavily depended-upon headers in the Inventory schema. It is typically invoked indirectly: Oracle Inventory forms, concurrent programs, and the transaction processor call the setters before performing work and read the type constants when classifying movements such as the WIP issue described above. Custom extensions should call INV_GLOBALS rather than hard-coding transaction type numbers, since the constants guarantee compatibility across 12.1.1 and 12.2.2 and insulate custom code from numeric shifts. Because the package is AUTHID CURRENT_USER, callers execute under their own schema privileges, and any custom code invoking it must hold the appropriate grants on the referenced objects.