Results for “cro_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKI_ROLE_MAPS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKI – Contracts Intelligence product family. Its documented purpose is to map contract and contact roles to specific reporting values. In practice, the view provides a denormalized, read-only projection of the OKI_ROLE_MAPS table, allowing reporting tools, concurrent programs, and integration interfaces to resolve role classifications without querying the base table directly. The view is marked VALID in both Oracle EBS 12.1.1 and 12.2.2, and its column set is consistent across both releases.

Because it is a simple SELECT-over-table view with no joins, aggregation, or filtering predicates, it introduces no additional processing overhead beyond the underlying table access. This makes it suitable for high-volume extraction into operational data stores or Contracts Intelligence reporting schemas.

Underlying Base Objects

The view is defined exclusively over the base table OKI_ROLE_MAPS, aliased as ORM. The defining query selects every column from that table without transformation, join, or WHERE clause. There are no other documented base objects, and ETRM metadata lists no additional referenced objects for this view. Consequently, row-level filtering, security, and multi-org behavior are inherited entirely from OKI_ROLE_MAPS, including its SECURITY_GROUP_ID column.

The one-to-one relationship between the view and the table means INSERT, UPDATE, and DELETE operations cannot be performed through the view; it is intended strictly for query and reporting access.

Key Columns

• ROLE_USE – Indicates the context in which a role applies, distinguishing contract roles from contact roles and directing which reporting classification should be applied.
• SCS_CODE – The source or system classification code associated with the role mapping.
• RLE_CODE – The role code identifying the specific contract or contact role being mapped.
• CRO_CODE – The reporting role code; this is the target value to which the role is mapped for reporting purposes. This column is frequently the subject of user searches and is the primary output of the mapping logic.
• OBJECT_VERSION_NUMBER – Optimistic locking version indicator maintained by the underlying table.
• SECURITY_GROUP_ID – Identifies the security group owning the mapping row, supporting data isolation in multi-group deployments.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record standard Oracle EBS who/when audit information.

Common Use Cases and Queries

The principal use case is resolving a role code to its reporting value during contract or contact reporting. A typical query retrieving the reporting mapping for a specific role is:

• SELECT role_use, scs_code, rle_code, cro_code FROM apps.oki_role_maps_v WHERE rle_code = :p_role_code;
• SELECT rle_code, cro_code FROM apps.oki_role_maps_v WHERE role_use = 'CONTRACT' ORDER BY rle_code;
• SELECT DISTINCT cro_code FROM apps.oki_role_maps_v WHERE security_group_id = :p_group;

These queries are commonly embedded in custom reports, OBIEE or BI Publisher data models, and interface programs that translate EBS role values into standardized reporting categories. Because the view exposes audit columns, it also supports change-tracking extracts. When troubleshooting mapping discrepancies, DBAs typically compare OKI_ROLE_MAPS_V output against OKI_ROLE_MAPS directly, since the two are structurally identical.