Results for “role_code”

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

Overview

OKI_K_PARTIES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKI – Contracts Intelligence product family. It exposes information about the parties associated with contracts, resolving each contract-party-role combination into a readable row that combines contract identifiers, role classifications, and party names. The view is structurally valid in both Oracle EBS 12.1.1 and 12.2.2 and serves as a reporting and integration access point for contract party data without requiring consumers to join the underlying OKC and OKX transactional entities directly.

Because contract party data is distributed across role assignment tables and party master tables, this view performs the necessary joins and applies the OKC_UTIL.GET_K_ACCESS_LEVEL security function, ensuring that only contracts for which the requesting user holds at least read ('R') or update ('U') access are returned. The user search term "role_meaning" corresponds directly to the ROLE_MEANING column, which carries the translated, user-facing description of the role code assigned to a party on a contract. This makes the view particularly valuable for role-oriented reporting.

Underlying Base Objects

The view text identifies four principal sources within each branch of its UNION:

• OKC_K_PARTY_ROLES_B (aliased CPR) — the base contract party role assignment table, supplying the party role ID, contract header ID, role code, party identifier, and descriptive flexfield attributes.
• OKI_SALES_K_HDRS (aliased SHD) — supplies contract number, contract number modifier, complete contract number, and the security code (SCS_CODE) used by the access-level function.
• FND_LOOKUPS (aliased RLE) — provides role meaning, filtered on LOOKUP_TYPE = 'OKC_ROLE' and matched to the role code.
• OKX_PARTIES_V or OKX_ORGANIZATION_DEFS_V (aliased OKX) — resolves the party name, depending on whether the party is an external party or an operating unit.

The UNION combines two selection branches. The first handles party role records whose JTOT_OBJECT1_CODE is 'OKX_PARTY', joining to OKX_PARTIES_V. The second handles operating unit records whose JTOT_OBJECT1_CODE is 'OKX_OPERUNIT', joining to OKX_ORGANIZATION_DEFS_V filtered on ORGANIZATION_TYPE = 'OPERATING_UNIT' and INFORMATION_TYPE = 'OPERATING UNIT INFORMATION'. Both branches restrict results using OKC_UTIL.GET_K_ACCESS_LEVEL.

Key Columns

• PARTY_ROLE_ID — unique identifier of the party role assignment.
• CONTRACT_ID — internal contract header identifier used for joins.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, COMPLETE_CONTRACT_NUMBER — the formatted contract reference.
• ROLE_CODE — the lookup code from FND_LOOKUPS identifying the party's function on the contract.
• ROLE_MEANING — the translated meaning of the role code; this is the column users typically search for by the term "role_meaning".
• PARTY_ID and PARTY_NAME — the numeric identifier and descriptive name of the party.
• CREATION_DATE, LAST_UPDATE_DATE — audit columns describing when the role assignment was created and last modified.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield segments capturing customer-specific data.

Common Use Cases and Queries

Typical scenarios include listing all parties on a contract with their role meanings, identifying contracts where a specific party holds a given role, and joining the view into custom reporting or interface logic. A representative query follows:

SELECT CONTRACT_NUMBER, COMPLETE_CONTRACT_NUMBER, ROLE_CODE, ROLE_MEANING, PARTY_NAME
FROM APPS.OKI_K_PARTIES_V
WHERE ROLE_MEANING = :role_meaning
ORDER BY COMPLETE_CONTRACT_NUMBER;

A second common pattern filters by contract to enumerate all associated parties and their roles, while a third joins PARTY_ID to other OKX-based views for extended party attributes. Because access is enforced through OKC_UTIL.GET_K_ACCESS_LEVEL, results automatically reflect the invoking user's contract security privileges, making the view suitable for both interactive reporting and programmatic data extraction within the Contracts Intelligence module.