Search Results get_miss_num

Overview

APPS.MTL_SECONDARY_INVENTORIES_PKG is the server-side PL/SQL package responsible for maintaining the MTL_SECONDARY_INVENTORIES table, the master data store for subinventories in Oracle Inventory. A subinventory is a logical (and often physical) subdivision of an inventory organization, such as a receiving area, a staging location, a quarantine area, or a floor stock bin. Because so many downstream Inventory transactions (material issue, receipt, transfer, move order, on-hand query) resolve a transaction against a valid subinventory, this package provides the low-level, table-maintenance entry points that the Oracle Inventory forms and other packages call when a subinventory definition is created, queried for uniqueness, or changed.

The package is classified in ETRM as an OTHER API rather than a public interface API. It is intended primarily for internal use by the Oracle Inventory application. Nevertheless, its procedure signatures are documented, and it forms the transactional backbone for subinventory setup. The header comment records a WMS enhancement that added status control, default locator status, default cost group, and LPN-controlled flag support to the insert path.

Key Procedures and Functions

• CHECK_UNIQUE — A function that validates whether a proposed secondary inventory (subinventory) name is unique within the given organization. It takes a ROWID (in/out), the subinventory name, and the organization ID, and returns a numeric result. This is the uniqueness guard invoked before an insert or rename.
• COMMIT_ROW — Commits the current transaction, persisting the subinventory row changes made through this package.
• ROLLBACK_ROW — Rolls back the current transaction, discarding uncommitted subinventory changes.
• INSERT_ROW — Inserts a new subinventory row. It accepts a ROWID (in/out) and the full set of subinventory attributes, including name, organization, audit columns, description, disable date, ATP code, availability/reservable/locator types, picking and dropping order, the material, overhead, resource, outside processing, expense, and encumbrance accounts, quantity-tracked and asset-inventory flags, source type and source subinventory/organization, requisition approval type, the 15 descriptive flexfield attributes, and preprocessing, processing, and postprocessing lead times. WMS-related columns (status, default locator status, default cost group, and LPN-controlled flag) are also accommodated.
• LOCK_ROW — Acquires a row-level lock on the target subinventory record to serialize concurrent updates.
• UPDATE_ROW — Updates an existing subinventory row with modified attribute values.
• DELETE_ROW — Removes a subinventory definition.
• STATUS_HISTORY — Maintains and processes subinventory status history, reflecting changes to the status control associated with the subinventory.
• GET_MISS_NUM — The procedure referenced in the originating search. It is associated with the package's numeric sequence or missing-number handling logic, used to obtain the next sequence value required for subinventory-related identifiers or status history entries.

Tables Accessed

The package operates against a single documented table, MTL_SECONDARY_INVENTORIES, accessed through its APPS synonym. All insert, update, delete, lock, uniqueness validation, and status history operations are directed at that table. This table stores one row per subinventory per organization and is the authoritative source for subinventory attributes consumed throughout Inventory and Order Management.

Usage Notes

MTL_SECONDARY_INVENTORIES_PKG is invoked primarily by the Oracle Inventory subinventory maintenance forms when a user creates, updates, or deletes a subinventory, and by other application packages that need to programmatically manage subinventory definitions. ETRM records that it is referenced by two other packages, confirming its role as a shared, lower-level component. Customizations and extensions that must insert or update subinventory rows should call INSERT_ROW, UPDATE_ROW, or DELETE_ROW rather than issuing direct DML, so that CHECK_UNIQUE validation, locking, audit column population, and status history are consistently applied. In Oracle EBS 12.1.1 and 12.2.2 the table and package structure are materially the same, with the WMS-related columns present in both. Because the package is classified OTHER, Oracle does not guarantee API compatibility across releases, so custom callers should validate signatures after any upgrade.