Search Results oki_role_maps_u1

Overview

OKI.OKI_ROLE_MAPS is a seed data table in the Oracle E-Business Suite Contracts Intelligence (OKI) schema. It functions as a role resolution mapping that translates a party role or contact role associated with a contract category (sub-class) into a canonical role type used for reporting. The design intent is documented explicitly: a contract category may name its customer or vendor role inconsistently across sub-classes, so the reporting layer requires a stable mapping to know which party role represents the customer and which contact role represents the sales representative. Without this translation, aggregations such as "top contract customers" or "sales representative by contract" cannot be computed reliably.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as reference and seed data rather than transactional data. Under the heuristic Data Vault classification supplied in the metadata, OKI_ROLE_MAPS is identified as a standalone object. In Data Vault modeling terms this suggests the table behaves as a small reference or lookup structure rather than a hub, link, or satellite, and it may be treated as a reference table joined at query time rather than modeled as a core business entity.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• ROLE_USE (VARCHAR2, 10) — The role use descriptor, for example CUSTOMER or vendor, indicating which reporting role the mapping serves.
• SCS_CODE (VARCHAR2, 30) — The contract category (sub-class) code to which the mapping applies.
• RLE_CODE (VARCHAR2, 30) — The party role code that should be interpreted as the role identified by ROLE_USE for that category.
• CRO_CODE (VARCHAR2, 30) — The contact role code, used where the mapping targets a contact rather than a party.
• OBJECT_VERSION_NUMBER (NUMBER) — Row version tracking column, used for optimistic locking and change detection.
• SECURITY_GROUP_ID (NUMBER) — Multi-tenant / application hosting discriminator, documented as a foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Who columns recording audit and ownership metadata.

The composite business key is defined by the primary key OKI_ROLE_MAPS_PK on (ROLE_USE, SCS_CODE). A separate unique index, OKI_ROLE_MAPS_U1, enforces uniqueness on the same column pair (ROLE_USE, SCS_CODE) in the APPS_TS_SEED tablespace. Because both the PK and the unique index cover the identical column set, OKI_ROLE_MAPS_U1 should be read as an alternate access path for the business key rather than a distinct business rule. No surrogate single-column primary key is documented; the table relies entirely on the natural composite key.

Common Use Cases and Queries

The primary use case is role resolution during reporting. A reporting query typically joins OKI_ROLE_MAPS to contract and party role tables to determine which role code satisfies a given ROLE_USE for a contract category. A representative retrieval pattern is:

• Look up the party role for a category: SELECT RLE_CODE FROM OKI.OKI_ROLE_MAPS WHERE ROLE_USE = 'CUSTOMER' AND SCS_CODE = :category;
• Resolve the contact role for a sales representative by substituting CRO_CODE for RLE_CODE in the same predicate.
• Enumerate all mappings for a category with SELECT ROLE_USE, RLE_CODE, CRO_CODE FROM OKI.OKI_ROLE_MAPS WHERE SCS_CODE = :category;
• Migrate or audit seed data by comparing OBJECT_VERSION_NUMBER and the Who columns between environments.

Because the table is seed-scoped and small, it is usually joined rather than scanned directly, and it benefits from the OKI_ROLE_MAPS_U1 index whenever the ROLE_USE / SCS_CODE predicate is present.

Related Objects

OKI_ROLE_MAPS is documented as referencing no other database objects within its own dependency graph, and it is referenced by the APPS synonym/view layer exposed as OKI_ROLE_MAPS. The principal documented relationships are:

• FND_SECURITY_GROUPS — referenced through the SECURITY_GROUP_ID column, supporting application hosting and data partitioning.
• OKI_ROLE_MAPS_PK — the composite primary key on (ROLE_USE, SCS_CODE).
• OKI_ROLE_MAPS_U1 — the unique index on the same key columns, used as the primary access path.

Reporting joins typically extend outward to the contract category and party role structures that consume the RLE_CODE and CRO_CODE values, though those relationships are implicit in the reporting model rather than enforced by foreign keys on this seed table.