Search Results okc_kol_contacts_v

Overview

OKC_KOL_CONTACTS_V is a reporting and integration view in the Oracle E-Business Suite Contracts Core (OKC) module. It exposes the contact records associated with contract documents, enriched with the descriptive role name resolved from Oracle's lookup framework. The view is defined over OKC_CONTACTS and joins to FND_LOOKUPS to translate the stored contact role code into a human-readable meaning. Its name reflects the "KOL" designation commonly associated with contract contact objects, and it is intended primarily for query and reporting consumption rather than for direct transactional maintenance. In the metadata captured from the ETRM repository for release 12.1.1 and 12.2.2, the view carries the remark "Not implemented in this database," indicating that the object may not exist until the relevant OKC patching or product installation has been applied. When present, it provides a stable, denormalized projection of contract contacts suitable for use in custom reports, concurrent programs, and outbound integrations.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the view text reveals its two source objects. The primary source is OKC_CONTACTS, aliased as CTCB, which holds the contract contact records including the contact party identifier, role code, sequence, and effective dates. The secondary source is FND_LOOKUPS, aliased as FNDV, the standard Oracle Applications lookup table. The join condition matches CTCB.CRO_CODE to FNDV.LOOKUP_CODE, constrained to LOOKUP_TYPE = 'OKC_CONTACT_ROLE'. An additional filter restricts rows to those whose lookup entry is currently active, using SYSDATE BETWEEN FNDV.START_DATE_ACTIVE AND NVL(FNDV.END_DATE_ACTIVE, SYSDATE). This means contacts whose role lookup has been end-dated will be excluded from the result set, which is an important consideration when reconciling against the base table. The view also invokes the OKC_UTIL.GET_NAME_FROM_JTFV function to resolve the contact's display name from the JTF object identifier columns.

Key Columns

• ID — The unique identifier of the contact record, sourced from OKC_CONTACTS.ID.
• DNZ_CHR_ID — The contract document identifier that the contact belongs to.
• CPL_ID — The contact point or party identifier associated with the contact.
• CRO_CODE — The stored contact role code, the column most frequently used in filtering.
• ROLE — The translated meaning of CRO_CODE, resolved from FND_LOOKUPS.MEANING.
• NAME — The resolved contact name returned by OKC_UTIL.GET_NAME_FROM_JTFV.
• OBJECT1_ID1 / OBJECT1_ID2 — Key components of the referenced JTF object identifier.
• JTOT_OBJECT1_CODE — The JTF object type code, indicating the entity class of the contact.
• PRIMARY_YN — Flag indicating whether the contact is the primary contact for the contract.
• OBJECT_VERSION_NUMBER — Optimistic locking version, useful for change detection.
• CONTACT_SEQUENCE — Ordering sequence for multiple contacts.
• START_DATE / END_DATE — Effective date range of the contact assignment.
• KOL_CRO_JTOT_CODE — A concatenated key of role code, asterisk, and JTF object code, truncated to 80 characters, provided for convenience in sorting and keying.

Common Use Cases and Queries

The view is typically used to report all contacts attached to a contract, to identify the primary contact, or to list contacts by role. A representative query filtering on role code is:

• SELECT ID, DNZ_CHR_ID, CRO_CODE, ROLE, NAME, PRIMARY_YN FROM OKC_KOL_CONTACTS_V WHERE CRO_CODE = :cro_code;
• SELECT DNZ_CHR_ID, NAME, ROLE FROM OKC_KOL_CONTACTS_V WHERE DNZ_CHR_ID = :contract_id AND PRIMARY_YN = 'Y';
• SELECT CRO_CODE, ROLE, COUNT(*) FROM OKC_KOL_CONTACTS_V GROUP BY CRO_CODE, ROLE;

Because the view applies an active-date filter on the lookup, queries returning fewer rows than expected should be validated against OKC_CONTACTS directly before concluding that contact data is missing.