Results for “okc_k_party_roles”

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

Overview

OKC_K_PARTY_ROLES_HV is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. It is the history view counterpart to the transactional table OKC_K_PARTY_ROLES, which stores the parties assigned to contract documents and the roles those parties play (for example, customer, supplier, or bill-to party). The "_HV" suffix follows the EBS naming convention for a history view, which presents current and prior versions of a row using the version columns maintained by the Contracts versioning framework.

The view exposes the party role data together with translation and lookup information so that consumers receive descriptive values rather than raw codes. It is joined to the FND_LOOKUPS lookup type OKC_ROLE to resolve RLE_CODE into a role meaning, and to the translation header table for language-specific attributes such as COGNOMEN and ALIAS. This makes the view suitable for reporting, concurrent program queries, and integrations that need to display or extract party role information across language environments.

Because it reads from the _BH (base history) table rather than the base table, it retains superseded major versions of a party role record, enabling audit and point-in-time reporting.

Underlying Base Objects

The view is defined over three base objects, all resolved through APPS synonyms in the documented metadata. The first is OKC_K_PARTY_ROLES_BH, aliased CPLB, which supplies the versioned party role rows, including the primary keys, version numbers, flexfield attributes, and auditing columns. The second is OKC_K_PARTY_ROLES_TLH, aliased CPLT, which provides the language-specific translation of attributes such as COGNOMEN, ALIAS, and the SFWT_FLAG.

The third is FND_LOOKUPS, joined using LOOKUP_TYPE = 'OKC_ROLE' and LOOKUP_CODE = RLE_CODE, which supplies the MEANING column for the role. The metadata also references the FND_GLOBAL package, reflecting the use of the USERENV('LANG') session function to filter translations to the user's language. Consistent with EBS history views, the "B" and "T" tables are joined on ID and MAJOR_VERSION so that each version of the base record is matched with its corresponding translation.

Key Columns

The view exposes the identity and versioning columns ID, MAJOR_VERSION, OBJECT_VERSION_NUMBER, and ROW_ID, which together allow consumers to distinguish between multiple major versions of the same party role. CHR_ID identifies the contract header, while CLE_ID and CPL_ID link the record to contract line and party information. DNZ_CHR_ID supports associations across contract documents.

RLE_CODE carries the role code, and the MEANING column derived from FND_LOOKUPS provides its display name. The OBJECT1_ID1, OBJECT1_ID2, and JTOT_OBJECT1_CODE columns carry the reference to the party or object assuming the role, while CUST_ACCT_ID and BILL_TO_SITE_USE_ID provide customer account and bill-to site context. Domain qualifiers include FACILITY, MINORITY_GROUP_LOOKUP_CODE, SMALL_BUSINESS_FLAG, and WOMEN_OWNED_FLAG.

Translation-driven columns include COGNOMEN, ALIAS, and SFWT_FLAG. The standard ATTRIBUTE1 through ATTRIBUTE15 columns carry the descriptive flexfield data, and CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE provide audit information. PRIMARY_YN indicates whether the party role is the primary role for the contract.

Common Use Cases and Queries

Typical uses include audit reports showing the evolution of parties on a contract, integration extracts that feed downstream systems, and reconciliation queries that compare history to current state. The following query lists party roles for a given contract, resolving the role code to its display meaning:

• SELECT id, major_version, chr_id, rle_code, role, primary_yn FROM okc_k_party_roles_hv WHERE chr_id = :contract_id ORDER BY major_version;
• SELECT chr_id, rle_code, role, cognomen, alias FROM okc_k_party_roles_hv WHERE rle_code = 'CUSTOMER' AND last_update_date >= :cutoff_date;
• SELECT id, major_version, object_version_number, last_updated_by, last_update_date FROM okc_k_party_roles_hv WHERE id = :party_role_id ORDER BY major_version;

Because the view filters translations to USERENV('LANG'), results reflect the session language of the reporting user. Queries that need all languages should use the underlying _TL tables directly.