Results for “cross_reference”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_CROSS_REFERENCES_SRW_V is an Oracle E-Business Suite view owned by the APPS schema and classified under the INV (Inventory) product family. The ETRM documentation for this object identifies it with the description "10SC ONLY," indicating that it is a restricted, purpose-built view rather than a general-purpose reporting interface. Its status is VALID across the 12.1.1 and 12.2.2 releases, and it exposes a narrow, de-duplicated projection of the item cross-reference data maintained in the Inventory module.

The view returns only three columns — CROSS_REFERENCE_TYPE, CROSS_REFERENCE, and DESCRIPTION — and applies a DISTINCT operator to the result set. This design makes it suitable for lookup and validation scenarios where a consumer needs the set of distinct cross-reference type/cross-reference combinations without exposure to the full breadth of the underlying cross-reference table. It is not a primary reporting view for item cross-reference analysis; applications requiring item numbers, organization context, or vendor-specific attributes should query MTL_CROSS_REFERENCES directly or use other Inventory cross-reference views.

Underlying Base Objects

The view is defined over a single base object: MTL_CROSS_REFERENCES, accessed through a SYNONYM in the APPS schema. MTL_CROSS_REFERENCES is the Inventory table that stores cross-reference relationships between inventory items and external identifiers, such as manufacturer part numbers, vendor part numbers, competitor part numbers, and substitute items.

The view text is documented as:

• SELECT DISTINCT CROSS_REFERENCE_TYPE, CROSS_REFERENCE, DESCRIPTION FROM MTL_CROSS_REFERENCES

Because the definition is a simple projection with DISTINCT, the view carries no joins, no filters, and no aggregation beyond duplicate elimination. It inherits the security posture of the underlying table; any row visible in MTL_CROSS_REFERENCES is eligible to appear in the view, subject only to duplicate suppression on the three projected columns. The DISTINCT clause effectively collapses multiple inventory item rows that share the same type, cross-reference value, and description into a single output row, which is the principal behavioral difference between this view and its base table.

Key Columns

• CROSS_REFERENCE_TYPE — Identifies the classification of the cross-reference, for example manufacturer part number, vendor part number, or substitute item. This is the column most commonly used in search predicates, including searches keyed on the term "cross_reference_type."
• CROSS_REFERENCE — The external identifier value itself, such as the actual manufacturer or vendor part number string associated with the type.
• DESCRIPTION — Free-text descriptive information attached to the cross-reference record, typically a human-readable label or supplementary note.

Notably absent from the projection are the item identifier (INVENTORY_ITEM_ID), organization identifier (ORGANIZATION_ID), and any UOM or vendor columns present in MTL_CROSS_REFERENCES. Consumers requiring the item-to-cross-reference linkage must join back to the base table or to MTL_SYSTEM_ITEMS on the appropriate keys.

Common Use Cases and Queries

Typical usage centers on populating lookup lists, validating inbound interface values, and generating distinct value sets for cross-reference types. A representative query that enumerates the available cross-reference types is:

• SELECT DISTINCT CROSS_REFERENCE_TYPE FROM APPS.MTL_CROSS_REFERENCES_SRW_V ORDER BY 1;

A query that retrieves the distinct values for a specific type, useful for validation in an interface or conversion script, is:

• SELECT CROSS_REFERENCE, DESCRIPTION FROM APPS.MTL_CROSS_REFERENCES_SRW_V WHERE CROSS_REFERENCE_TYPE = :p_type ORDER BY CROSS_REFERENCE;

Because the view exposes no item or organization context, it should be treated as a reference-value source rather than a transactional reporting object. Where item-level detail is required, query MTL_CROSS_REFERENCES directly and join to MTL_SYSTEM_ITEMS. The "10SC ONLY" designation in the ETRM documentation further indicates that this view is intended for a specific restricted purpose within the 10SC context, and its use should be confirmed against the functional requirements of the implementation before it is relied upon in custom reporting.