Search Results okc_contact_sources_u1

Overview

OKC.OKC_CONTACT_SOURCES is a seed-data reference table in the Oracle E-Business Suite Contracts (OKC) schema. It defines the valid data sources that may be used to define a Contract Contact in a specific role, as recorded in OKC_CONTACTS. In practice, the table functions as a metadata registry: it tells the Contracts application which OKX view supplies contact information for a given combination of contact role, source role, and buy/sell context. Contract entities such as Contract Items (OKC_K_ITEMS_B), Contract Parties (OKC_K_PARTY_ROLES_B), Contacts (OKC_CONTACTS), and Rules (OKC_RULES_B) can reference different data sources depending on the Contract Subclass (OKC_SUBCLASS_B) and other factors, and OKC_CONTACT_SOURCES governs which of those sources is permissible.

The object is stored in the APPS_TS_SEED tablespace with PCT Free 10, consistent with its role as seeded setup data rather than high-volume transactional content. Based on the foreign key structure and the presence of descriptive attributes tied to a composite business key, the heuristic Data Vault classification is satellite-leaning; this should be treated as a modeling suggestion rather than a normative Oracle designation. The table is owned by OKC, carries FND design data OKC.OKC_CONTACT_SOURCES, and has a status of VALID.

Key Information Stored

The documented physical schema contains 16 columns. The most significant are described below.

• CRO_CODE – Role code for a Contact, such as "Program Manager", "Payer", or "Officer".
• RLE_CODE – Role code for the contact source, such as "Customer" or "Vendor".
• BUY_OR_SELL – The role of the contact in the buy/sell context.
• START_DATE – Beginning of the active period, one second after midnight on the indicated date.
• END_DATE – End of the active period, one second before midnight on the indicated date.
• JTOT_OBJECT_CODE – Foreign key to JTF_OBJECTS_B; represents the view referenced by OBJECT_ID columns.
• CONSTRAINED_YN – Flag indicating whether the source is constrained.
• OBJECT_VERSION_NUMBER – Sequential number set to 1 on insert and incremented on update; used by APIs to ensure the current record is passed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Who columns for audit lineage.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, supporting multi-org/security partitioning.
• ACCESS_LEVEL and ZD_EDITION_NAME – Additional control and editioning columns documented in the 12.2.2 schema.

The primary key is OKC_CONTACT_SOURCES_PK, defined over CRO_CODE, RLE_CODE, BUY_OR_SELL, and START_DATE. The unique index OKC_CONTACT_SOURCES_U1 covers CRO_CODE, RLE_CODE, BUY_OR_SELL, START_DATE, and ZD_EDITION_NAME, making it the strongest business-key candidate. Because there is no single surrogate identifier column, the composite key serves both as the primary key and as the effective business identifier.

Common Use Cases and Queries

Typical usage centers on validating or reporting which contact sources are available for a given role during contract authoring. A common pattern filters active rows by role and buy/sell context:

• Lookup of valid sources for a role: SELECT cro_code, rle_code, buy_or_sell, jtot_object_code FROM okc_contact_sources WHERE cro_code = :p_cro_code AND buy_or_sell = :p_buy_sell AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE+1);
• Reporting constrained versus unconstrained sources: filter on CONSTRAINED_YN to identify sources restricted by business rules.
• Joining to JTF_OBJECTS_B on JTOT_OBJECT_CODE to resolve the underlying view name referenced by OBJECT_ID columns.
• Resolving the edition context in 12.2.2 by including ZD_EDITION_NAME in the predicate when editioning is enabled.
• Auditing seed changes by examining CREATION_DATE and LAST_UPDATE_DATE against the 1-on-insert OBJECT_VERSION_NUMBER convention.

Related Objects

The following objects are most significant in relation to OKC_CONTACT_SOURCES.

• OKC_CONTACTS – Stores contract contacts whose valid source definitions are governed by this table.
• OKC_K_ITEMS_B – Contract Items, a contracts entity that may reference different data sources; this is the object type referenced in the user search for "okc_k_items_b".
• OKC_K_PARTY_ROLES_B – Contract Parties that can reference differing data sources.
• OKC_RULES_B – Rules that may be source-dependent.
• OKC_SUBCLASS_B – Contract Subclass; a primary determinant of which sources are valid.
• JTF_OBJECTS_B – Joined via OKC_CONTACT_SOURCES.JTOT_OBJECT_CODE to identify the referenced view.
• FND_SECURITY_GROUPS – Joined via OKC_CONTACT_SOURCES.SECURITY_GROUP_ID for security partitioning.
• OKX views – The underlying data sources that the table's metadata points to for populating contact information.