Results for “item_identifier_type”

50+ results




Overview
Explore in AI Chat

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

Overview

The OE_AK_ITEM_IDENTIFIER_TYPE_V view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and defined within the ONT – Order Management product. It is a seeded, VALID view in both EBS 12.1.1 and 12.2.2. Its purpose is to present a consolidated, normative list of valid item identifier types — the values used to classify item cross-references such as UPC codes, customer part numbers, competitor part numbers, and internal identifiers. The view functions as a validation and List-of-Values (LOV) source for Oracle Order Management and related modules that allow users to select an item identifier type on order entry, pricing, or cross-reference setup screens. Because it normalizes the union of two distinct data sources into a simple two-column projection, it also serves as a stable reporting and integration endpoint: external systems and custom reports query the view rather than the underlying tables, insulating them from schema-level changes to the base objects.

Underlying Base Objects

The documented base objects referenced by this view are MTL_CROSS_REFERENCE_TYPES (exposed as a SYNONYM) and OE_LOOKUPS (a VIEW over the lookups infrastructure). The view text is a UNION of two branches:

  • The first branch selects CROSS_REFERENCE_TYPE twice from MTL_CROSS_REFERENCE_TYPES, supplying both the code and its meaning from the canonical cross-reference type inventory table.
  • The second branch selects LOOKUP_CODE and MEANING from OE_LOOKUPS, filtered to LOOKUP_TYPE = 'ITEM_IDENTIFIER_TYPE' and restricted to the lookup codes INT (internal) and CUST (customer), and further constrained by ENABLED_FLAG = 'Y'.

The UNION de-duplicates identical rows, yielding a single authoritative list combining the physical cross-reference type definitions with the enabled lookup-based identifier types. OE_LOOKUPS itself resolves lookup values maintained through the application's lookup administration layer, meaning the view reflects both setup-driven and reference-data-driven sources. This design ties the item identifier domain back to the mtl_cross_reference_types table that users commonly search for when investigating cross-reference configuration.

Key Columns

  • ITEM_IDENTIFIER_TYPE — The identifier type code. In the first half it maps to CROSS_REFERENCE_TYPE from MTL_CROSS_REFERENCE_TYPES; in the second it maps to LOOKUP_CODE from OE_LOOKUPS (values such as INT and CUST). This is the value stored on transactional and setup records referencing an item identifier.
  • ITEM_IDENTIFIER_TYPE_MEANING — The user-facing description corresponding to the code above, sourced from CROSS_REFERENCE_TYPE or MEANING respectively. It is the display text presented in LOVs and reports.

Common Use Cases and Queries

Typical uses include populating LOVs, validating identifier types during order import or interface processing, and building cross-reference reports. To list all available identifier types with meanings:

  • SELECT ITEM_IDENTIFIER_TYPE, ITEM_IDENTIFIER_TYPE_MEANING FROM APPS.OE_AK_ITEM_IDENTIFIER_TYPE_V ORDER BY ITEM_IDENTIFIER_TYPE;
  • To confirm a specific code is enabled: SELECT 1 FROM APPS.OE_AK_ITEM_IDENTIFIER_TYPE_V WHERE ITEM_IDENTIFIER_TYPE = :p_code;
  • To join against item cross-references: SELECT v.ITEM_IDENTIFIER_TYPE_MEANING, x.cross_reference FROM MTL_CROSS_REFERENCES x, OE_AK_ITEM_IDENTIFIER_TYPE_V v WHERE x.cross_reference_type = v.ITEM_IDENTIFIER_TYPE;

Because the view already filters disabled lookups and distills the identifier domain, it is the recommended source for any validation, LOV, or reporting requirement involving item identifier types, rather than querying MTL_CROSS_REFERENCE_TYPES and OE_LOOKUPS separately.