Search Results init_transaction

Overview

INV_GENEALOGY_REPORT_GEN is an Oracle E-Business Suite PL/SQL package owned by APPS that provides the underlying utility layer for the Inventory genealogy detailing engine. Its role is to assemble and format the attribute data that describes the complete lineage of inventory objects — lots, serial numbers, and their associated transactions — so that the genealogy report can present a traceable view of material movement, transformation, and disposition across the supply chain.

The package spec is declared with AUTHID CURRENT_USER, meaning that execution privileges and name resolution are evaluated against the invoking schema rather than the package owner. The header comment identifies the package as "utilities used by the detailing engine (both inv and wms versions)," confirming that a single shared specification serves both the Oracle Inventory and Warehouse Management System implementations. The package was originally created in July 2005 and its most recent shipped revision dates to March 2013 (version 120.4.12020000.2).

Key Procedures and Functions

ETRM documents a single public program unit on this specification:

• GENEALOGY_REPORT — The principal entry point of the package and the only documented procedure or function. It drives generation of the genealogy output, drawing on the record type definitions declared in the specification to shape the report data. Parameter details are not enumerated in the documented metadata.

Although not separately documented as callable units, the specification declares several strongly typed records that the report logic depends upon and that callers may reference directly:

• item_info_rec_type — item identifiers, descriptions, shelf life, retest interval, primary and secondary units of measure, and organization code/description.
• lot_attributes_rec_type — lot number, parent lot, status, grade, retest and expiration dates, hold date, source origin, initial quantity and UOM, the init_transaction and init_date fields, document, supplier, organization, item, and sampling event identifiers.
• serial_attributes_rec_type — unit and serial numbers, status, state, receipt and ship dates, job, operation, step, current lot, and WIP context including wip_entity_id, operation_seq_num, and intraoperation_step_type.
• work_order_header_rec_type — assembly item and description, wip_entity_id, and production item identifier.

The init_transaction element within lot_attributes_rec_type is the field that records the transaction type associated with a lot's originating movement, and it is the attribute that surfaces when users search on that term.

Tables Accessed

The package reads from the following tables (accessed through APPS synonyms):

• MTL_OBJECT_GENEALOGY — the core genealogy relationship table linking parent and child objects; it is the primary data source for lineage traversal.
• MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS — lot and serial attribute sources.
• MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS — item descriptive flexfield and organization-level setup.
• MTL_TRANSACTION_TYPES — resolves transaction type names such as the init_transaction value.
• GMD_SAMPLING_EVENTS, GMD_SAMPLES, GMD_EVENT_SPEC_DISP, GMD_SAMPLE_SPEC_DISP — process manufacturing sampling and specification data.
• WIP_ENTITIES — work order context for produced assemblies.
• WSM_LOT_SPLIT_MERGES — lot split and merge history used to reconstruct lineage where lots are divided or combined.
• FND_USER — user identification, typically for audit or responsibility context.

Usage Notes

INV_GENEALOGY_REPORT_GEN is an internal utility package rather than a standalone user-facing program. It is normally invoked from the genealogy detailing engine, which in turn is driven by the Oracle Inventory genealogy report and the corresponding WMS reporting flow. Because no other packages reference it (referenced by 0), it is effectively a leaf dependency invoked directly by the reporting layer.

Typical invocation occurs through the concurrent program that produces the lot and serial genealogy report, where the detailing engine calls this package to populate the record structures and return formatted attribute rows. Custom extensions that need to reproduce genealogy output — for example, to embed lot lineage in a downstream label, quality record, or integration file — may call the package directly, but such callers must supply the organization and object identifiers expected by the detailing engine and must respect the AUTHID CURRENT_USER semantics, ensuring the invoking schema holds the required privileges on the underlying MTL, GMD, WIP, and WSM tables.