Results for “okc_contact_sources_v”

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

Overview

OKC_CONTACT_SOURCES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered under the OKC — Contracts Core product family. In both 12.1.1 and 12.2.2, the view is documented as VALID and serves as the primary read interface over the OKC_CONTACT_SOURCES table, which stores the assignment of contact sources to contract roles and contract repositories. Its purpose is to expose a denormalized, flat projection of contact-source rows so that concurrent programs, BI Publisher reports, Oracle Contracts forms, and external integrations can retrieve contact-source data without directly querying the base table.

Because the view is a thin, near one-to-one projection of its base table, the underlying data model is not altered. It preserves the same column names, datatypes, and row cardinality as OKC_CONTACT_SOURCES. The view therefore acts as a stable public contract that shields consumers from physical attributes of the base table, including its storage layout and table-level attributes, while still returning the base table's ROWID as ROW_ID for downstream update and identification logic.

Underlying Base Objects

The view text is defined exclusively over OKC_CONTACT_SOURCES, referenced in the SELECT statement via its alias CSOB. In the documented ETRM metadata for 12.2.2, the referenced base object is listed as the synonym OKC_CONTACT_SOURCES. No joins, unions, or aggregations are present; the definition is a direct column projection with an explicit ROWID alias. The dependency chain is consequently simple: APPS.OKC_CONTACT_SOURCES_V → OKC_CONTACT_SOURCES synonym → underlying OKC_CONTACT_SOURCES table. This absence of joins means query performance is proportional to the base table access path, and any index present on OKC_CONTACT_SOURCES, such as those on RLE_CODE, CRO_CODE, or the date range columns, remains available to the optimizer when the view is queried.

Key Columns

• ROW_ID — the ROWID of the base table row, aliased in the view definition; used for row identification and optimistic update patterns.
• RLE_CODE — the contract role code to which the contact source applies, a principal filtering attribute.
• CRO_CODE — the contact repository or contact source organization code associated with the role.
• BUY_OR_SELL — indicates whether the contact source applies to the buying or selling side of the contract.
• START_DATE / END_DATE — the effective date range for the contact-source assignment, enabling date-effective querying.
• JTOT_OBJECT_CODE — the joint object code linking the row to related contract object structures.
• CONSTRAINED_YN — the flag indicating whether the contact source is constrained; this is the column most commonly searched for by users and is exposed unchanged from the base table.
• OBJECT_VERSION_NUMBER — the optimistic locking version number used by the Oracle Forms and OAF layers to detect concurrent updates.
• ACCESS_LEVEL — the access control level applied to the contact-source record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns providing record provenance and change tracking.

Common Use Cases and Queries

The view is typically queried when reporting on the contact sources assigned to contract roles, when validating the CONSTRAINED_YN setting for a given source, or when resolving the effective contact source for a role on a specified date. A representative query follows.

• SELECT RLE_CODE, CRO_CODE, BUY_OR_SELL, CONSTRAINED_YN FROM APPS.OKC_CONTACT_SOURCES_V WHERE CONSTRAINED_YN = 'Y' AND SYSDATE BETWEEN START_DATE AND END_DATE;
• SELECT CRO_CODE, START_DATE, END_DATE FROM APPS.OKC_CONTACT_SOURCES_V WHERE RLE_CODE = :p_role_code ORDER BY START_DATE;
• SELECT COUNT(*) FROM APPS.OKC_CONTACT_SOURCES_V WHERE BUY_OR_SELL = 'B' AND OBJECT_VERSION_NUMBER > 1;

Because the view preserves audit and versioning columns, it is equally suitable for reconciling contact-source changes in audit reports and for feeding external systems that require effective-dated contact-source data. Queries should filter on RLE_CODE, CRO_CODE, or the date range to exploit any supporting indexes on the base table.