Results for “constrained_code”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.OKC_ROLES_V is a bilingual reporting view within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It presents the set of contract role definitions used throughout the Contract Terms and Conditions (ETRM) and contract authoring functionality. The view exposes role codes, constrained role relationships, customer/vendor indicators, versioning data, and translated meaning and description text, making it suitable for reporting, integration, and lookup purposes across Oracle EBS 12.1.1 and 12.2.2.
Because the view joins the base table to its translation table using the session language, it returns role metadata in the language of the current user session rather than in a single hard-coded language. This design supports multilingual deployments and is consistent with the standard Oracle EBS MLS (Multi-Language Support) pattern. The view is owned by APPS, and its referenced base objects are exposed through synonyms, ensuring standard APPS-level accessibility from custom reports, concurrent programs, and integration interfaces.
Underlying Base Objects
The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:
- OKC_ROLES_B — the base table holding language-independent role attributes, including the role code, the constrained role code, the customer/vendor flag, the object version number, effective dates, and standard WHO audit columns.
- OKC_ROLES_TL — the translation table holding language-specific text, including the SFWT (Single Field With Translation) flag, meaning, and description.
The join condition is RLEB.CODE = RLET.CODE AND RLET.LANGUAGE = USERENV('LANG'), which links base and translation rows on the role code and restricts the translation row to the current session language. The view also selects RLEB.rowid as ROW_ID. This restricted, language-specific join means the view returns one row per role code for the active language, making it appropriate for user-facing reporting and lookup validation rather than for cross-language auditing at the table level.
Key Columns
- ROW_ID — the ROWID of the underlying OKC_ROLES_B row, useful for row identification in update or navigation scenarios.
- CODE — the unique role code identifying each contract role; the join key between the base and translation tables.
- CONSTRAINED_CODE — exposed from CONSTRAINED_RLE_CODE; identifies the constrained role code, which limits or restricts permissible roles in role assignment. This is the column users typically search for when investigating the term "constrained_code".
- CUSTOMER_VENDOR_FLAG — indicates whether the role applies to a customer or a vendor party in the contract.
- OBJECT_VERSION_NUMBER — the row version used for optimistic locking and change detection.
- SFWT_FLAG — the Single Field With Translation flag, indicating translation behavior for the role's text.
- MEANING and DESCRIPTION — the translated display name and descriptive text for the role, sourced from OKC_ROLES_TL in the session language.
- START_DATE and END_DATE — effective date range for the role definition.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording who created and last updated the row and when.
Common Use Cases and Queries
The view is commonly used to populate role selection lists, validate role codes during contract creation, and report role definitions with translated text. A simple retrieval of all current role definitions follows:
SELECT code, constrained_code, customer_vendor_flag, meaning, description FROM apps.okc_roles_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
To identify constrained roles specifically, filter on the constrained code column:
SELECT code, meaning, constrained_code FROM apps.okc_roles_v WHERE constrained_code IS NOT NULL ORDER BY code;
For integration or lookup validation, the view can be queried by customer/vendor classification:
SELECT code, meaning FROM apps.okc_roles_v WHERE customer_vendor_flag = 'C' ORDER BY meaning;
Because the join is language-restricted, the view returns translated MEANING and DESCRIPTION values for the session language automatically, eliminating the need for separate translation joins in custom queries. This makes OKC_ROLES_V a convenient and consistent source for contract role metadata in Oracle EBS 12.1.1 and 12.2.2 reporting and integration.