Results for “constrained_rle_code”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_ROLES_B is a table in the OKC schema (Contracts Core) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM documentation carries the terse description "For future use," indicating that Oracle delivered the object as part of the Contracts Core data model but did not activate it through standard application flows in these releases. It should therefore be treated as a dormant or reserved structural object rather than an operational source of contract data.
The table stores role definitions in a _B (base) table pattern, which in EBS conventionally pairs with a _TL translation table for multilingual attributes. Its documented column set includes effective-dating columns and audit columns, consistent with an entity that was designed to be maintainable and expandable. ETRM classifies OKC_ROLES_B heuristically as standalone within the Data Vault modeling suggestion framework, meaning it is modeled as a reference or lookup structure. Because the only documented foreign key is to FND_SECURITY_GROUPS and no other table references it, the standalone classification is consistent: the object functions closer to a reference hub of role codes than to a transactional link or satellite.
Key Information Stored
The physically documented schema contains 12 columns. The most significant are:
- CODE — the primary key, enforced by OKC_ROLES_B_PK and also by the unique index OKC_ROLES_B_U1. In this table the surrogate primary key and the business-key candidate coincide, so CODE serves as both the technical identifier and the natural role identifier used by any referencing logic.
- CONSTRAINED_RLE_CODE — a role code constrained relative to another role definition, supporting role hierarchies or qualification rules.
- CUSTOMER_VENDOR_FLAG — distinguishes whether the role applies to a customer party, a vendor party, or is otherwise classified, enabling party-type-specific role assignment.
- START_DATE and END_DATE — effective-dating columns that bound the validity window of each role definition.
- OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column used by the framework to detect concurrent updates.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing insert and update provenance.
- SECURITY_GROUP_ID — the Multi-Org / data-security discriminator, referencing FND_SECURITY_GROUPS, which scopes rows to the appropriate operating unit or security context.
No descriptive or translated text column (such as a NAME) is documented, which reinforces the "for future use" status: the table has structure but no populated descriptive payload in standard implementations.
Common Use Cases and Queries
Because the object is dormant in standard 12.1.1 and 12.2.2, direct application use cases are limited. Practical scenarios are diagnostic and modeling-oriented:
- Confirming whether records exist, as a due-diligence step before building custom contract-role logic:
SELECT CODE, CUSTOMER_VENDOR_FLAG, START_DATE, END_DATE FROM OKC.OKC_ROLES_B; - Checking Multi-Org scoping of any seeded rows:
SELECT r.CODE, g.SECURITY_GROUP_NAME FROM OKC.OKC_ROLES_B r, FND_SECURITY_GROUPS g WHERE r.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID; - Evaluating effective-dated role validity for point-in-time reporting: filter with
SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE + 1). - Assessing whether customer- versus vendor-specific roles are represented:
SELECT CUSTOMER_VENDOR_FLAG, COUNT(*) FROM OKC.OKC_ROLES_B GROUP BY CUSTOMER_VENDOR_FLAG; - Reverse-engineering potential role hierarchy:
SELECT CODE, CONSTRAINED_RLE_CODE FROM OKC.OKC_ROLES_B WHERE CONSTRAINED_RLE_CODE IS NOT NULL;
These queries are best used to verify whether the table is populated before relying on it; implementations that need contract role functionality typically model it through other OKC structures or custom extensions.
Related Objects
- FND_SECURITY_GROUPS — referenced by OKC_ROLES_B.SECURITY_GROUP_ID; the primary join path for Multi-Org security resolution.
- OKC_ROLES_B_PK — the primary key constraint over CODE, the object's technical anchor.
- OKC_ROLES_B_U1 — the unique index over CODE, confirming CODE as the business-key candidate.
- OKC_ROLES_TL — the conventional translation-table partner implied by the _B naming pattern, expected to hold language-specific descriptions when the object is activated.
- Other OKC Contracts Core role and party tables — any seeded OKC contract role lookups that share the CODE domain, which should be reconciled if custom role logic is introduced.
- FND_* audit and WHO columns — the standard EBS user and date references underlying CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
Because ETRM documents only one foreign key and no inbound references, the dependency surface of OKC_ROLES_B is narrow, consistent with its reserved status.