Search Results mtl_conversion_id_s

Overview

The APPS.MTL_LOT_UOM_CONV_PKG package body is a stored PL/SQL unit in the Oracle E-Business Suite Applications schema that governs unit-of-measure conversions specific to lot-controlled inventory. Its primary business function is to maintain the conversion definitions that allow a lot or lot-class to be transacted in a unit of measure that differs from the item's primary stocking UOM. This capability is essential in process manufacturing and other environments where material is received, stored, or issued in bulk quantities (for example, kilograms or liters) while being tracked at the lot level, and where the conversion relationship varies by lot class rather than by item alone.

The package is classified as an OTHER API and is documented as VALID in the ETRM repository for release 12.1.1 and 12.2.2. It operates as a table-handler style package: rather than exposing high-level business transactions, it provides the low-level data manipulation and locking primitives that other EBS components rely upon to manage lot UOM conversion records.

Key Procedures and Functions

The package body exposes four documented procedures, each responsible for a distinct data-maintenance operation against the underlying conversion table:

• INSERT_ROW — Creates a new lot unit-of-measure conversion record. It is the entry point for defining a conversion relationship between a lot UOM class and a target unit of measure, generating the surrogate key required for the new row.
• UPDATE_ROW — Modifies the attributes of an existing lot UOM conversion record, such as the conversion factor or associated descriptive values, without changing the record's identity.
• DELETE_ROW — Removes an existing lot UOM conversion record, typically invoked when a conversion definition is no longer valid for a given lot class.
• LOCK_ROW — Acquires a row-level lock on a conversion record to guarantee serialized access during concurrent maintenance, preventing lost updates when multiple sessions attempt to modify the same definition.

These procedures follow the standard Oracle EBS table-handler convention of separating insert, update, delete, and lock concerns, allowing callers to compose them into higher-level transactions while maintaining consistent locking behavior.

Tables Accessed

The package operates against three documented objects, all referenced through APPS synonyms:

• MTL_LOT_UOM_CLASS_CONVERSIONS — The central table holding the lot UOM class conversion definitions. The INSERT_ROW, UPDATE_ROW, and DELETE_ROW procedures read and write this table directly, making it the primary persistence target of the package.
• MTL_CONVERSION_ID_S — The sequence used to generate unique primary key values for newly inserted conversion records. This dependency is directly relevant to the user's search term mtl_conversion_id_s, confirming that conversion identifiers are sourced from this sequence during row creation.
• FND_DUAL — The Oracle Applications dual table, commonly used within EBS packages to evaluate expressions, retrieve sequence values, or perform single-row queries in a controlled fashion.

In addition to these tables, the package body references standard EBS infrastructure such as FND_API, FND_MESSAGE, FND_MSG_PUB, APP_EXCEPTION, and STANDARD, which support error handling and message-stack management during these operations.

Usage Notes

MTL_LOT_UOM_CONV_PKG is a foundational, low-level package and is not intended for direct end-user invocation. It is typically called by Oracle Inventory and lot-control forms or by higher-level application APIs that manage lot UOM class conversions on behalf of the user. Custom extensions that need to programmatically create or maintain lot-level UOM conversion definitions should call the documented procedures rather than issuing direct DML, ensuring that the conversion ID sequence is populated correctly and that row locking and message handling follow EBS conventions.

The ETRM metadata indicates the package is referenced by one other package, while it is not referenced by any database object at the schema dependency level. Its dependencies on MTL_CONVERSION_ID_S and MTL_LOT_UOM_CLASS_CONVERSIONS should be respected in any cloning, patching, or customization activity, as these objects must remain synchronized with the packaged logic.