Results for “customer_contact_id”

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

Overview

ICX_LOV_DUMMY_V is a database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides within the ICX product family, which corresponds to Oracle iProcurement. The object is documented in the E-Business Suite Technical Reference Manual (ETRM) with a status of VALID but carries an explicit description of "Obsolete." This classification indicates that the view is retained solely for backward compatibility and is no longer referenced by supported application code paths within the current release.

The view is a static, single-row construct. Rather than querying transactional or master data, it derives all of its column values from the DUAL table using literal string concatenation. Its historical purpose was to serve as a placeholder List of Values (LOV) source for contact identifier fields, providing the iProcurement user interface with a structurally valid but functionally empty record set during development or in configurations where no real contact data source was required. Because it returns constant values rather than querying application tables, it has no role in production reporting, data integration, or business intelligence workloads. Functional users and implementers should treat any reference to this view as a legacy artifact.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: DUAL, owned by SYS. The view definition is:

• SELECT DUMMY||'1' CUSTOMER_CONTACT_ID,
• DUMMY||'2' INTERNAL_CONTACT_ID,
• DUMMY||'3' SUPPLIER_CONTACT_ID
• FROM SYS.DUAL

Because DUAL contains exactly one row, the view always returns exactly one row. Each output column is formed by concatenating the DUAL.DUMMY pseudo-column (the character literal 'X') with a numeric suffix, producing the fixed values 'X1', 'X2', and 'X3'. No joins, filters, or subqueries are present. Consequently, the view has no dependency on any APPS transactional table and cannot reflect any change in application data. There is no relationship to customer, supplier, or HR contact tables; the naming of the columns is suggestive only and carries no referential meaning.

Key Columns

The view exposes three columns, all of type VARCHAR2 by virtue of the concatenation operation:

• CUSTOMER_CONTACT_ID — Returns the constant value 'X1'. Historically represented the identifier slot for a customer-side contact in an LOV.
• INTERNAL_CONTACT_ID — Returns the constant value 'X2'. Historically represented the identifier slot for an internal (employee) contact.
• SUPPLIER_CONTACT_ID — Returns the constant value 'X3'. Historically represented the identifier slot for a supplier-side contact.

None of these columns are key-flexfield enabled, none participate in foreign key constraints, and none carry validation against a lookup, value set, or ID flexfield. The values are deterministic and invariant across all environments and releases.

Common Use Cases and Queries

No supported business use case exists for this view in EBS 12.1.1 or 12.2.2. It is not consumed by standard concurrent programs, Oracle Reports, OAF pages, or interface tables. Its only legitimate diagnostic use is confirmation of presence or definition during upgrade or patching analysis. A typical inspection query is:

• SELECT customer_contact_id, internal_contact_id, supplier_contact_id FROM apps.icx_lov_dummy_v;

This returns the single row 'X1', 'X2', 'X3'. A DBA verifying object status may also query:

• SELECT object_name, object_type, status FROM dba_objects WHERE object_name = 'ICX_LOV_DUMMY_V';

Customizations must never JOIN or reference this view for contact resolution. Any custom code found using it should be remediated to select from the appropriate contact source, such as HZ_CUST_ACCOUNT_ROLES, PER_ALL_PEOPLE_F, or PO_VENDOR_CONTACTS. Given its obsolete designation, the view may be removed in a future release, and dependent custom objects would then fail validation.