Results for “cro_code”

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

Overview

OKS_CONTACT_V is a database view owned by the APPS schema within the OKS (Service Contracts) product family of Oracle E-Business Suite. It is documented in ETRM 12.2.2 with the description "Contacts View for Contract details Form," indicating its principal role as a presentation-layer data source for the Service Contracts contact form rather than as a transactional entity. The view consolidates contact role information, lookup meaning values, and party contact names into a single denormalized result set, allowing callers to resolve a contract order contact to its human-readable name and role without performing multiple joins in application code.

While the view is most closely associated with the Service Contracts UI, its exposure of contact identifiers makes it equally relevant to reporting and integration scenarios where a contract-related contact must be flattened into a single row containing both a role meaning and a display name. Because it is a view and not a table, it carries no storage of its own and always reflects the current state of the underlying base objects at query time.

Underlying Base Objects

ETRM documents the following referenced base objects for OKS_CONTACT_V: FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), OKC_CONTACT_SOURCES_V (VIEW), OKS_K_ORDER_CONTACTS_V (VIEW), and OKX_PARTY_CONTACTS_V (VIEW). The view text joins these sources as follows:

• OKC_CONTACT_SOURCES_V A — supplies the contact role source definitions; the join restricts BUY_OR_SELL = 'S' and RLE_CODE = 'CUSTOMER', so only customer-side contact sources are surfaced.
• FND_LOOKUPS B — resolves the contact role code (CRO_CODE) to its descriptive MEANING, constrained by LOOKUP_TYPE = 'OKC_CONTACT_ROLE'.
• OKX_PARTY_CONTACTS_V C — the party contacts view, joined on TO_NUMBER(D.OBJECT1_ID1) = C.ID1 and D.OBJECT1_ID2 = C.ID2, contributing the contact NAME.
• OKS_K_ORDER_CONTACTS_V D — the contract order contacts view, providing the driving subject identifiers ID, COD_ID, OBJECT1_ID1, OBJECT1_ID2, and JTOT_OBJECT_CODE.
• FND_GLOBAL — referenced as a package, typically for session context such as USER_ID or RESP_ID dependencies in dependent logic.

Key Columns

• ID — the primary identifier returned from the order contacts source.
• COD_ID — the contact/order detail identifier carried from OKS_K_ORDER_CONTACTS_V.
• OBJECT1_ID1 — the first object identifier component; converted with TO_NUMBER when matching to the party contacts view.
• OBJECT1_ID2 — the second object identifier component, joined directly to OKX_PARTY_CONTACTS_V.
• JTOT_OBJECT_CODE — the JTOT object code that links the contact source definition to the contact record; a mandatory join predicate.
• CRO_CODE — the contact role code, resolved against the OKC_CONTACT_ROLE lookup.
• MEANING — the translated lookup meaning for the contact role, suitable for display.
• NAME — the resolved contact name from the party contacts view.

Common Use Cases and Queries

Typical usage centers on resolving contacts attached to contract orders and presenting their role and name together. A representative query retrieves all customer-side contacts with their roles:

• SELECT id, cod_id, object1_id1, object1_id2, jtot_object_code, cro_code, meaning, name FROM apps.oks_contact_v ORDER BY id;
• SELECT meaning, name FROM apps.oks_contact_v WHERE cro_code = :role_code;
• SELECT COUNT(*) FROM apps.oks_contact_v WHERE object1_id1 = :object_id;

Because OKS_CONTACT_V joins several views, query performance depends on the selectivity of the underlying contract order contacts and party contacts sources. Restricting by COD_ID, OBJECT1_ID1, or CRO_CODE is advisable in production queries. The view is read-only and should not be treated as an interface for data manipulation.