Search Results build_assembly_lot_serial_tbl

Overview

INV_OA_GEN_PVT is a private PL/SQL package in the Oracle E-Business Suite Inventory (INV) module, owned by the APPS schema. The _PVT suffix indicates that the package is intended for internal use within the Inventory application and is not a public, supported API. Its source header (INVOAGES.pls 120.1, last modified 2005/10/10) places it in the Oracle Application Generator (OA Framework / OAG) generation layer, where packages supply data structures and helper routines that support Oracle Application Framework user interfaces and their underlying data retrieval logic.

The package centres on lot and serial number attributes for assemblies. It defines a record type, assembly_lot_sel_rec_type, containing a Lot_number (VARCHAR2(80)) and a serial_number (VARCHAR2(30)), and a collection type, assembly_lot_sel_tbl_type, which is an array of those records indexed by BINARY_INTEGER. These structures hold lot/serial selections associated with assembly transactions. The lot number length was increased to 80 characters to accommodate a change tracked under bug B4625329.

Key Procedures and Functions

The documented procedures in the package are:

• BUILD_ASSEMBLY_LOT_SERIAL_TBL — The principal routine requested by the search term build_assembly_lot_serial_tbl. It populates the assembly_lot_sel_tbl_type collection and returns standard API status outputs (x_return_status, x_msg_count, x_msg_data) together with the populated assembly lot/serial table. It is the core logic for assembling lot and serial attribute data.
• ROSETTA_TABLE_COPY_IN_P1 — A generated "Rosetta" conversion routine that copies data from OA Framework JTF_VARCHAR2_TABLE_100 collections (the table types used to pass multi-row data between the middle tier and the database) into the package's internal assembly_lot_sel_tbl_type collection. This is the inbound direction of a PL/SQL-to-Java data marshalling pattern.
• ROSETTA_TABLE_COPY_OUT_P1 — The corresponding outbound routine, copying data from the internal assembly_lot_sel_tbl_type back into JTF_VARCHAR2_TABLE_100 collections so the results can be returned to the OA Framework layer.
• build_assembly_lot_serial_tbl (overloaded) — A second form of the build routine that accepts JTF_VARCHAR2_TABLE_100 parameters directly, allowing callers to invoke the build logic with OA Framework-style inputs rather than the strongly typed record collection.

These four entries represent the documented procedure surface. No parameter lists are reproduced here beyond what the source excerpt shows.

Tables Accessed

The package is documented as referencing the following objects through APPS synonyms:

• MTL_ALLOCATIONS_GTMP — A global temporary table used to stage allocation data during processing. The build routine likely reads staged lot/serial allocation rows from this table when constructing the assembly lot/serial collection.
• PLITBLM — A PL/SQL index-by table (associative array) construct used internally to hold temporary row sets during validation or lookup processing.

Usage Notes

Because this is a _PVT package, it is not part of the public Inventory API surface and should not be called directly by customer extensions; Oracle reserves the right to change or remove it without notice. It is invoked internally, typically from OA Framework pages, controllers, or their supporting AM (Application Module) and EO/VO logic where users select or maintain lot and serial attributes for assemblies. The Rosetta routines confirm that data is passed across the JDBC boundary as JTF_VARCHAR2_TABLE_100 collections, a hallmark of OAF integration. Custom code that requires equivalent functionality should instead use Oracle's supported public lot/serial APIs; the metadata indicates the package is referenced by zero other packages, reinforcing its narrow, presentation-layer role.