Search Results women_owned_flag

Overview

The view APPS.OKC_K_PARTY_ROLES_V is a Contracts Core (OKC) reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It is defined in the APPS schema with VALID status and is documented as a view over the table OKC_CONTRACT_PARTY_ROLES_B. Its purpose is to present contract party role assignments in a denormalized, user-readable form by resolving language-dependent descriptive attributes and lookup meanings at query time.

Contract party roles record the parties associated with a contract or contract line, the role each party plays (for example, customer, supplier, or bill-to party), and various classification attributes relevant to regulatory and diversity reporting. Because the view joins the base table to its translation table and to the OKC_ROLE lookup set, consumers receive translated role names and alias values without needing to join FND_LOOKUPS themselves. The view is used in contract authoring inquiries, party-role reports, and integration extracts where a flattened, multi-language-aware representation of the party role data is required. The user search term women_owned_flag corresponds directly to the WOMEN_OWNED_FLAG column exposed by this view.

Underlying Base Objects

The view is constructed from three principal sources, each documented in the ETRM metadata:

• OKC_K_PARTY_ROLES_B — the base table holding the transactional party role rows. Aliased as CPLB, it supplies identifiers, flags, descriptive flexfield attributes, and audit columns.
• OKC_K_PARTY_ROLES_TL — the translation table carrying language-specific attributes such as SFWT_FLAG, COGNOMEN, and ALIAS. Aliased as CPLT, it is joined on ID and constrained to the session language via CPLT.LANGUAGE = USERENV('LANG').
• FND_LOOKUPS — aliased as FNDV and joined on LOOKUP_TYPE = 'OKC_ROLE' and RLE_CODE = LOOKUP_CODE, providing the MEANING used to populate the ROLE column.

The view text also references FND_GLOBAL (package) for the USERENV language context. In the ETRM 12.2.2 metadata, OKC_K_PARTY_ROLES_B and OKC_K_PARTY_ROLES_TL are listed as synonyms, and the view is owned by APPS.

Key Columns

• ID / ROW_ID — the primary identifier of the party role record and its physical ROWID.
• OBJECT_VERSION_NUMBER — supports optimistic locking in the contract authoring UI.
• CHR_ID / DNZ_CHR_ID — the contract header identifier and its denormalized counterpart.
• CPL_ID / CLE_ID / RLE_CODE — party identifier, contract line identifier, and role code.
• WOMEN_OWNED_FLAG — indicates whether the party is classified as women-owned, used in supplier diversity reporting.
• SMALL_BUSINESS_FLAG / MINORITY_GROUP_LOOKUP_CODE — companion diversity classification attributes.
• ROLE — the translated lookup meaning for the role code, derived from FND_LOOKUPS.
• ALIAS / COGNOMEN — language-specific alternate and formal names from the translation table.
• PRIMARY_YN — identifies the primary party for the role context.
• CUST_ACCT_ID / BILL_TO_SITE_USE_ID — customer account and bill-to site references used in receivables integration.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield segments available for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

A frequent reporting requirement is to list all parties on a contract together with their roles and diversity classifications. The following query extracts party roles for a specific contract, including the women-owned indicator.

SELECT role, women_owned_flag, small_business_flag,
       minority_group_lookup_code, primary_yn
FROM   apps.okc_k_party_roles_v
WHERE  chr_id = :p_chr_id
ORDER  BY role;

To isolate women-owned parties across contracts for supplier diversity analysis:

SELECT chr_id, cust_acct_id, role
FROM   apps.okc_k_party_roles_v
WHERE  women_owned_flag = 'Y'
AND    rle_code = 'CUSTOMER';

Because the view resolves ROLE and ALIAS through the translation table, it is also suitable for multi-language contract extracts and for integration interfaces that must supply human-readable role descriptions. Developers should note the view is read-only with respect to business logic; inserts and updates must target OKC_K_PARTY_ROLES_B and OKC_K_PARTY_ROLES_TL directly, and reporting queries should filter on CHR_ID or CPL_ID to avoid full scans on large contract volumes.