Search Results preprocess_serial

Overview

INV_SERIAL_EO_PVT is a private (PVT) PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It provides the core serial number processing logic used by the Inventory module to validate, create, and maintain serial number records associated with inventory items and lots. The package forms part of the serial number entity object layer, sitting beneath the public INV_SERIAL_API_PUB interface and providing the internal pre-processing, insert, update, and delete operations that public APIs and forms rely upon. Because it is classified as a private package, it is not intended for direct customer invocation, though it is extensively called by Oracle's own application code and, in practice, by custom extensions that need finer control over serial processing than the public APIs expose. The header identifies the source as INVSNEOS.pls with a version of 120.1, and the package is marked "noship," indicating it is an internal, non-shipped entity object.

Key Procedures and Functions

The package exposes ten documented procedures, beginning with PREPROCESS_SERIAL, which performs validation and preparation work for a serial number before it is inserted or updated. It accepts inventory item, organization, lot, parent lot, revision, and serial number range parameters, and returns an x_is_new_serial flag that informs the caller whether the supplied serial already exists. This flag is the pivot on which downstream insert-versus-update decisions are made, and it is the procedure most commonly referenced when searching on "preprocess_serial."

• DELETE_SERIAL — removes serial number records for a given inventory item, organization, and serial number range.
• INSERT_SERIAL — creates new serial number records, accepting the standard API control parameters (API version, initialization message list, commit flag, validation level) plus item, organization, serial, date, revision, lot, locator, subinventory, transaction source, and vendor attributes.
• UPDATE_SERIAL — modifies existing serial number records, applying the same attribute set used by INSERT_SERIAL.
• ROSETTA_TABLE_COPY_IN_P0 / OUT_P0 — convert a character table (JTF_VARCHAR2_TABLE_1000) to and from INV_LOT_API_PUB.CHAR_TBL.
• ROSETTA_TABLE_COPY_IN_P1 / OUT_P1 — convert a number table (JTF_NUMBER_TABLE) to and from INV_LOT_API_PUB.NUMBER_TBL.
• ROSETTA_TABLE_COPY_IN_P2 / OUT_P2 — convert a date table (JTF_DATE_TABLE) to and from INV_LOT_API_PUB.DATE_TBL.

The Rosetta procedures are bulk-collection adapters that allow the API to pass PL/SQL tables between the JTF and INV_LOT_API_PUB typing conventions, supporting set-based processing of serial and lot data.

Tables Accessed

The package reads from and writes to MTL_SERIAL_NUMBERS, the base table that stores every serial number tracked in Inventory, including item, organization, lot, revision, current locator, subinventory, transaction source, vendor, and the serial number itself. All insert, update, delete, and validation logic ultimately targets this table. The second documented table, PLITBLM, is an Oracle Applications internal message table used by the FND message stack to accumulate errors and warnings generated during API processing. Its presence confirms the package uses the standard error-handling framework, with return status, message count, and message data populated on completion or failure.

Usage Notes

INV_SERIAL_EO_PVT is invoked primarily from within Oracle's own Inventory code, including the serial number entry forms, the receiving and shipping flows, and the public serial number APIs that wrap this entity object. The documented metadata records zero packages referencing it directly, which understates actual usage because references typically occur through dynamic or indirect calls rather than declared dependencies. Custom developers generally interact with this package when they need to bypass or extend the standard public API, for example to pre-validate a serial number before committing a transaction or to determine whether a serial already exists prior to choosing an insert or update path. Invocation follows the standard EBS API convention: pass a validation level, pass an initialization message list, and inspect the return status and message count on completion. Because it is a private package, direct calls carry upgrade risk, and Oracle does not guarantee the signature of PREPROCESS_SERIAL or the other procedures across releases. The parameters involving dates and vendors feed into initialization, completion, and ship date tracking and vendor sourcing attributes on MTL_SERIAL_NUMBERS. Any custom code should therefore be tested carefully after applying patches, and the public serial number API should be preferred wherever it provides equivalent functionality.