Results for “inv_object_genealogy”

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

Overview

The APPS.INV_OBJECT_GENEALOGY package body is an Oracle Inventory component responsible for resolving and maintaining the object genealogy model that underlies lot, serial, and WIP entity tracking. Genealogy in Oracle EBS establishes the parent-child relationships between items and their associated transactions, enabling traceability across receiving, manufacturing, and shipping activities. This package supplies the runtime logic used to identify the type of a genealogy object, retrieve its descriptive attributes, and populate the hierarchical tree structures (both upward and downward) that trace an object back to its source or forward to its descendants.

The package is classified as OTHER in the ETRM metadata for release 12.2.2 and is owned by APPS. Its header comment (INVOGENB.pls 120.10) indicates that it has been maintained across multiple EBS releases, including 12.1.1 and 12.2.2, primarily to support serial and lot genealogy inquiry functions delivered through Oracle Inventory.

Key Procedures and Functions

The package exposes twelve documented entry points. The most foundational are described here.

• GETOBJECTTYPE — Determines the genealogy object type for a given object identifier by probing MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, and WIP_ENTITIES. It returns a numeric code identifying whether the object is a lot, a serial number, or a WIP entity, and returns NULL when no match is found.
• GETOBJECTINFO — Returns the full descriptive attribute set for a genealogy object, including object name, description, type name, expiration date, primary unit of measure, inventory item identifier, object number, material status, and unit number. It supports debug tracing via the INV_DEBUG_TRACE profile option.
• GETOBJECTNUMBER — Retrieves the identifying number associated with a genealogy object.
• GETSOURCE and GETTRADINGPARTNER — Return the originating source and trading partner information for an object, supporting supply-chain traceability.
• GETTRANSACTIONINFO — Provides transaction-level details associated with a genealogy object.
• INV_POPULATE_PARENT_TREE and INV_POPULATE_CHILD_TREE — Populate the upward (parent) and downward (child) genealogy hierarchies, respectively, assembling the structure used by tree-based UI displays.
• INIT — Performs package-level initialization of working structures.
• GETJDATA and SET_ROWLIMIT — Support data retrieval and constrain the number of rows returned during tree assembly.

Tables Accessed

The package references a broad set of Inventory, WIP, Order Management, and Receivables tables through APPS synonyms. Core genealogy data resides in MTL_OBJECT_GENEALOGY, with object identity resolved through MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, and WIP_ENTITIES. Item and parameter context is drawn from MTL_SYSTEM_ITEMS_KFV and MTL_PARAMETERS. Transactional context comes from MTL_TXN_REQUEST_HEADERS, MTL_TXN_REQUEST_LINES, MTL_PHYSICAL_INVENTORIES, and MTL_CYCLE_COUNT_HEADERS. Costing linkage is provided by CST_COST_UPDATES. Customer and trading partner references use HZ_PARTIES and HZ_CUST_ACCOUNTS, while sales order context is drawn from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. Temporary tree staging uses MTL_GEN_TEMP.

Usage Notes

INV_OBJECT_GENEALOGY is invoked from the Inventory serial and lot genealogy inquiry forms, where it drives the display of parent and child traceability trees. It is also referenced by eight other packages, indicating reuse across inventory, WIP, and order-related genealogy queries. Debug output can be enabled by setting the INV_DEBUG_TRACE profile option, which routes trace messages through INV_TRX_UTIL_PUB.TRACE. Custom extensions requiring genealogy lookups should call the public functions rather than querying MTL_OBJECT_GENEALOGY directly, ensuring consistent object type resolution and row limits.