Search Results insert_serial
Overview
INV_SERIAL_EO_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Oracle Inventory (INV) application module. The "EO_PVT" naming convention indicates an entity-object private layer, meaning the package is not intended as a public integration interface but rather as an internal worker that supports the public serial-number APIs. Its source header carries a "noship" designation, confirming that it is a stub or supporting package rather than a standalone deliverable. The package encapsulates the low-level logic required to validate, create, update, and remove records in the serial number repository, shielding callers from the direct DML operations and validation rules that govern serialized inventory. It handles serials for both lot-controlled and non-lot-controlled items, and it supports serial ranges spanning a from-serial and to-serial number. Because it is classified as a private API (PVT), it is invoked exclusively by Oracle's own public APIs and forms rather than by external customizations, and it exposes only a small, focused set of procedures.
Key Procedures and Functions
- PREPROCESS_SERIAL — Performs pre-validation on a proposed serial number before insertion, using the inventory item, organization, lot, parent lot, revision, and serial range as inputs. It returns an indicator of whether the serial is new, allowing the caller to decide whether an insert is warranted.
- DELETE_SERIAL — Removes a serial number, or a range of serial numbers, from the serial repository for a given inventory item and organization.
- INSERT_SERIAL — Creates a new serial number record. Its signature follows the standard Oracle API conventions, exposing module and validation control parameters (API version, initialization of message list, commit flag, validation level) alongside the serial attributes: inventory item, organization, serial number, initialization/completion/ship dates, revision, lot number, locator, subinventory, transaction source, and unit vendor.
- UPDATE_SERIAL — Modifies the attributes of an existing serial number record.
- ROSETTA_TABLE_COPY_IN_P0 / _P1 / _P2 and ROSETTA_TABLE_COPY_OUT_P0 / _P1 / _P2 — A family of six helper procedures that marshal PL/SQL collections into and out of the technology-stack table types used by the public API layer. The P0 variants convert character data, P1 converts numeric data, and P2 converts date data, using the
char_tbl,number_tbl, anddate_tblcollection types declared in INV_LOT_API_PUB.
Tables Accessed
The package reads and writes MTL_SERIAL_NUMBERS, the base table that stores every serialized unit tracked by Oracle Inventory. INSERT_SERIAL and DELETE_SERIAL perform the insert and delete DML against this table, and PREPROCESS_SERIAL queries it to determine whether a serial already exists. PLITBLM is referenced as part of the package's supporting infrastructure and is associated with Oracle's PL/SQL table and message-handling utilities used for collection manipulation and error reporting. All access is performed through APPS synonyms, consistent with the private API classification.
Usage Notes
Because INV_SERIAL_EO_PVT is a private entity-object package, it is not called directly by customer code. It is invoked indirectly through the public serial number APIs and through the Oracle Inventory serial entry forms and concurrent processes that create and maintain serial numbers. Custom integrations that require serial creation should call the supported public interface rather than this package. The "noship" header and the absence of any dependent packages in the documented metadata reinforce that this is an internal implementation unit whose procedures may change between patch levels; any direct reference to INSERT_SERIAL or its siblings should be treated as unsupported and subject to breakage across releases such as 12.1.1 and 12.2.2.
-
PACKAGE: APPS.INV_SERIAL_EO_PVT
12.1.1
-
PACKAGE: APPS.INV_SERIAL_EO_PVT
12.2.2
-
APPS.INV_SERIAL_EO_PVT SQL Statements
12.1.1
-
APPS.INV_SERIAL_EO_PVT SQL Statements
12.2.2
-
APPS.WMS_TASK_LOAD SQL Statements
12.2.2
-
APPS.WMS_TASK_LOAD SQL Statements
12.1.1
-
APPS.INV_RCV_COMMON_APIS SQL Statements
12.1.1
-
APPS.INV_RCV_COMMON_APIS SQL Statements
12.2.2
-
PACKAGE: APPS.WMS_TASK_LOAD
12.1.1
-
PACKAGE: APPS.WMS_TASK_LOAD
12.2.2
-
PACKAGE BODY: APPS.INV_SERIAL_EO_PVT
12.2.2
-
APPS.INV_SERIAL_EO_PVT dependencies on JTF_DATE_TABLE
12.2.2
-
APPS.INV_SERIAL_EO_PVT dependencies on JTF_DATE_TABLE
12.1.1
-
PACKAGE BODY: APPS.INV_SERIAL_EO_PVT
12.1.1
-
APPS.INV_SERIAL_EO_PVT dependencies on INV_LOT_API_PUB
12.2.2
-
APPS.WMS_TASK_LOAD dependencies on INV_MOBILE_HELPER_FUNCTIONS
12.2.2
-
APPS.WMS_TASK_LOAD dependencies on INV_MOBILE_HELPER_FUNCTIONS
12.1.1
-
APPS.INV_SERIAL_EO_PVT dependencies on INV_LOT_API_PUB
12.1.1
-
PACKAGE: APPS.INV_RCV_COMMON_APIS
12.1.1
-
PACKAGE BODY: APPS.INV_RCV_COMMON_APIS
12.1.1
-
PACKAGE BODY: APPS.WMS_TASK_LOAD
12.1.1
-
PACKAGE: APPS.INV_RCV_COMMON_APIS
12.2.2
-
PACKAGE BODY: APPS.INV_RCV_COMMON_APIS
12.2.2
-
PACKAGE BODY: APPS.WMS_TASK_LOAD
12.2.2
-
APPS.INV_RCV_COMMON_APIS dependencies on FND_MSG_PUB
12.2.2
-
APPS.INV_RCV_COMMON_APIS dependencies on FND_MSG_PUB
12.1.1
-
APPS.WMS_TASK_LOAD dependencies on FND_MSG_PUB
12.1.1
-
APPS.WMS_TASK_LOAD dependencies on FND_MSG_PUB
12.2.2
-
APPS.WMS_TASK_LOAD dependencies on FND_MESSAGE
12.1.1
-
APPS.WMS_TASK_LOAD dependencies on FND_MESSAGE
12.2.2
-
APPS.INV_RCV_COMMON_APIS dependencies on INV_MOBILE_HELPER_FUNCTIONS
12.1.1
-
APPS.INV_RCV_COMMON_APIS dependencies on INV_MOBILE_HELPER_FUNCTIONS
12.2.2
-
APPS.WMS_TASK_LOAD dependencies on FND_API
12.2.2
-
APPS.WMS_TASK_LOAD dependencies on FND_API
12.1.1
-
APPS.INV_RCV_COMMON_APIS dependencies on FND_API
12.2.2
-
APPS.INV_RCV_COMMON_APIS dependencies on FND_API
12.1.1
-
APPS.WMS_TASK_LOAD dependencies on WMS_TASK_LOAD
12.2.2
-
APPS.WMS_TASK_LOAD dependencies on WMS_TASK_LOAD
12.1.1
-
APPS.INV_RCV_COMMON_APIS dependencies on INV_RCV_COMMON_APIS
12.1.1
-
APPS.INV_RCV_COMMON_APIS dependencies on INV_RCV_COMMON_APIS
12.2.2