Search Results okc_role_sources_pk

Overview

OKC_ROLE_SOURCES is a configuration table in the Contracts Core (OKC) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It defines the valid data sources from which a PARTY may be derived when that party is assigned to a particular ROLE within a contract. In practical terms, the table acts as a role-to-source mapping control: for each contract role (for example, a buyer, seller, or internal counterparty role) it records which underlying object type supplies the party values, and whether the mapping applies on the buy side, the sell side, or both. Because contract authoring, defaulting, and party validation logic in OKC reference this table, it functions as a foundational setup object rather than a transactional table — it is populated during implementation and rarely changes during day-to-day contracting.

From a Data Vault modeling perspective, the documented structure is best described as satellite-leaning. This is a heuristic classification derived from the foreign-key and primary-key topology. The primary key (RLE_CODE, BUY_OR_SELL, START_DATE) is a natural composite key that, combined with the START_DATE/END_DATE pair, gives the table a time-versioned, attribute-descriptive character typical of a satellite rather than a hub or link. Note that this is a modeling suggestion only, not a declared property of the object.

Key Information Stored

OKC_ROLE_SOURCES contains 14 documented columns. The most significant are:

• RLE_CODE — Identifies the contract role to which the source rule applies. This is the leading component of the primary key.
• BUY_OR_SELL — Indicates whether the rule applies to the buy side, the sell side, or both. This is the second component of the primary key and a critical dimension in contract party resolution.
• START_DATE and END_DATE — Bound the effective period of the mapping, giving the table its date-effective behavior. START_DATE is the third primary key component.
• JTOT_OBJECT_CODE — The foreign key to JTF_OBJECTS_B that identifies the source object type supplying the party. This is the central descriptive attribute of the row.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle AOL framework for concurrent update protection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns providing audit trail information.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling row-level access.
• ACCESS_LEVEL — Governs the access privileges applicable to the row.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching.

The surrogate primary key is OKC_ROLE_SOURCES_PK on (RLE_CODE, BUY_OR_SELL, START_DATE). The documented unique index OKC_ROLE_SOURCES_U1 on (RLE_CODE, BUY_OR_SELL, START_DATE, ZD_EDITION_NAME) is the business-key candidate and confirms that a role/side combination cannot have overlapping effective rows within a given edition.

Common Use Cases and Queries

Typical uses include validating that a role is properly configured before contract creation, reporting the effective source for each role and side, and troubleshooting party defaulting failures in contract authoring.

To list current, effective role-to-source mappings:

• SELECT rle_code, buy_or_sell, jtot_object_code, start_date, end_date FROM okc_role_sources WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE) ORDER BY rle_code, buy_or_sell;

To find the source object for a specific role and side:

• SELECT jtot_object_code FROM okc_role_sources WHERE rle_code = :role AND buy_or_sell = :buy_or_sell AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

For contract DBA reporting, joining to JTF_OBJECTS_B yields a human-readable source description rather than an object code.

Related Objects

• JTF_OBJECTS_B — joined via OKC_ROLE_SOURCES.JTOT_OBJECT_CODE = JTF_OBJECTS_B.OBJECT_CODE; resolves the source object type.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; enforces row-level security grouping.
• OKC_ROLES (or equivalent role definition table) — provides the description of RLE_CODE; the natural parent of the role dimension.
• OKC_CONTRACT_PARTIES — consumes the role/source rules when recording actual parties on a contract.
• JTF_OBJECTS_TL — the translated name companion to JTF_OBJECTS_B, used in multi-language reporting.
• OKC_CONTRACTS_ALL — the contract header table whose authoring flows depend on valid role sources.