Search Results mtl_cross_references_pub

Overview

MTL_CROSS_REFERENCES_PUB is the public API package for cross-reference (xref) management within Oracle Inventory (INV) in Oracle E-Business Suite 12.1.1 and 12.2.2. Cross-references map an alternate identifier — such as a manufacturer part number, competitor part number, substitute item, or customer-specific number — to an internal inventory item and, where applicable, to a specific organization and supplier context. Because so many processes depend on resolving these alternate numbers consistently, the application exposes a thin public wrapper layer whose body delegates the substantive work to underlying private packages.

The package owner is APPS and its documented status is VALID. It is classified as a PUB (public) API, meaning it is the supported entry point intended for external callers, as opposed to the private package that holds the validation and DML logic. The body depends on ERROR_HANDLER, FND_API, and MTL_CROSS_REFERENCES_PVT, and on the standard SYS.STANDARD and PUBLIC.PLITBLM. No database object references this package, confirming that it is an inbound-only interface rather than a utility consumed internally.

Key Procedures and Functions

The documented public interface consists of a single program unit:

• PROCESS_XREF — The sole documented procedure in the package body. It serves as the public-facing handler for cross-reference processing, accepting caller-supplied xref data and routing it to the private package for the actual validation and persistence logic. Its design follows the standard EBS public/private pattern: the public procedure performs no direct business validation itself, instead ensuring that the call is made through a supported interface and that error handling is applied uniformly via FND_API and ERROR_HANDLER.

No other procedures or functions are documented, so the interface surface is intentionally narrow. Callers should treat PROCESS_XREF as the entry point and must not invoke MTL_CROSS_REFERENCES_PVT directly, since the private package is subject to change without notice across patch levels.

Tables Accessed

The documented table reference is PLITBLM, the standard Oracle Application Object Library (AOOL) PL/SQL index-by table type used for passing arrayed or list-based parameters into PL/SQL APIs. Its presence indicates that PROCESS_XREF is designed to accept bulk or collection-based cross-reference data rather than strictly single-row input, allowing a caller to submit multiple xref records in one invocation.

Importantly, the public body itself does not directly read or write MTL_CROSS_REFERENCES or MTL_CROSS_REFERENCE_TYPES. All inventory cross-reference DML is performed inside MTL_CROSS_REFERENCES_PVT, which the body calls. This separation keeps the transaction and validation logic in one place and preserves the integrity of the underlying base tables, which are shared by forms, import programs, and order-entry processes.

Usage Notes

In a typical EBS environment, cross-references are maintained through the Inventory or Order Management forms, which ultimately reach the private package. MTL_CROSS_REFERENCES_PUB is invoked when a supported programmatic path is required — for example, from a custom concurrent program, a PL/SQL wrapper script, or custom code that must create or update xref data while honoring the standard EBS validation, error-stack, and savepoint conventions implemented through FND_API.

Because the package is not referenced by any other database object, it is safe to conclude that no internal EBS process relies on it; changes to it will not ripple into unpublished dependencies. Developers should nevertheless call only PROCESS_XREF, handle the returned FND_API.G_RET_STS error status, and expect that the private package may be modified by Oracle patches. The typical invocation pattern is therefore: initialize the API context, populate the PLITBLM input structure, call PROCESS_XREF, and inspect the error stack via ERROR_HANDLER when the status indicates failure. This keeps custom integrations aligned with Oracle's supported interface and insulated from internal implementation changes across 12.1.1 and 12.2.2.