Search Results customer_contact_id




Overview
Explore in AI Chat

Overview

APPS.ICX_LOV_DUMMY_V is a lightweight, dictionary-defined view in the Oracle E-Business Suite (EBS) Applications (APPS) schema. It exposes three synthetic identifier columns derived from the SYS.DUAL pseudo-table, providing placeholder values that conform to the contact identifier naming conventions used elsewhere in the Oracle iProcurement, iSupplier, and Internet Computing Architecture (ICX) product family. In Oracle EBS 12.1.1 and 12.2.2, the view is registered in the ETRM metadata repository under owner APPS, with DUAL documented as the sole referenced base object.

The view does not store business data. Its purpose is structural and referential: it allows Application Object Library (AOL) list-of-values (LOV) definitions, Oracle Forms LOV records, and dependent view or synonym definitions to reference a discoverable object exposing the columns CUSTOMER_CONTACT_ID, INTERNAL_CONTACT_ID, and SUPPLIER_CONTACT_ID without binding those references to a production contact table. This decoupling is useful during form validation, LOV metadata compilation, and integration testing, where the column shape must exist even though the contact values themselves are supplied at runtime by a different source.

Underlying Base Objects

The view is defined exclusively over SYS.DUAL, the single-row, single-column Oracle kernel table. Because DUAL contains exactly one row with the value 'X' in its column DUMMY, the view always returns exactly one row. The concatenation expressions DUMMY||'1', DUMMY||'2', and DUMMY||'3' evaluate to the character strings 'X1', 'X2', and 'X3' respectively. No join, filter, or access to application tables is involved, so no APPS transactional table is read when the view is queried.

The ETRM metadata lists no other base tables, which confirms the view is self-contained and carries no foreign-key or lookup dependency on customer, supplier, or HR contact tables. This is significant when reviewing dependency chains, since changes to contact-related base tables cannot invalidate ICX_LOV_DUMMY_V.

Key Columns

  • CUSTOMER_CONTACT_ID — Exposes the expression DUMMY||'1', yielding the literal 'X1'. It occupies the identifier position associated with a customer contact, allowing code or metadata that searches for the term customer_contact_id to resolve to a valid column without returning real customer contact data.
  • INTERNAL_CONTACT_ID — Exposes DUMMY||'2', yielding 'X2'. Represents the internal (employee) contact identifier slot.
  • SUPPLIER_CONTACT_ID — Exposes DUMMY||'3', yielding 'X3'. Represents the supplier contact identifier slot.

All three columns are character-valued because of the concatenation, and none is a true numeric ID despite the _ID suffix. This distinction matters when the view is used as a placeholder in type-checking or metadata-only contexts.

Common Use Cases and Queries

Typical scenarios include verifying that an LOV or dependent object definition resolves correctly, populating test harnesses for iProcurement contact selection, and confirming column-name references during EBS 12.1.1 to 12.2.2 upgrades. A simple verification query is:

  • SELECT customer_contact_id, internal_contact_id, supplier_contact_id FROM apps.icx_lov_dummy_v; — returns one row: X1, X2, X3.
  • SELECT customer_contact_id FROM apps.icx_lov_dummy_v WHERE customer_contact_id = 'X1'; — exercises predicate handling on the target column.
  • SELECT COUNT(*) FROM apps.icx_lov_dummy_v; — confirms a single-row result, useful in automated validation scripts.

Because the view returns only placeholder values, it must never be used to drive production contact lookups, joins to real contact tables, or data extracts intended for business reporting. Its legitimate role is confined to metadata resolution, dependency validation, and test scaffolding within the Oracle EBS 12.1.1 and 12.2.2 technical stack.