Search Results admin_flag

Overview

OKX_RESOURCE_ROLES_V is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product family. It exposes information about role and resource associations used by Oracle Contracts, allowing role assignments to be reported, audited, and joined against other EBS entities without requiring direct access to the underlying JTF (Oracle CRM Foundation / Resource Manager) base tables. The view is documented as VALID in both Release 12.1.1 and 12.2.2 and is referenced in the ETRM (E-Business Suite Technical Reference Manual) as a supported integration and reporting object.

The view consolidates data from three base objects into a denormalized, user-friendly result set, presenting role identifiers, translated role names and descriptions, association dates, and a series of Boolean-style indicator flags. Because it restricts the result set to roles where the role type code equals CONTRACTS, the view is effectively a Contracts-specific projection of the broader JTF resource-role model.

Underlying Base Objects

The view definition joins three synonym-referenced base tables in the APPS schema:

• JTF_RS_ROLE_RELATIONS (RR) — the primary association table, supplying the role-resource relationship records, active date ranges, and the delete flag.
• JTF_RS_ROLES_B (B) — the base role definition table, supplying role type, role code, seeded status, and the membership, administration, lead, and manager indicator flags.
• JTF_RS_ROLES_TL (T) — the translated role table, supplying the language-dependent role name and description. The join is filtered by T.LANGUAGE = USERENV('LANG'), returning text in the session's NLS language.

The join condition links B.ROLE_ID to RR.ROLE_ID and to T.ROLE_ID, and the query is constrained by B.ROLE_TYPE_CODE = 'CONTRACTS', ensuring that only Contracts-typed roles are returned.

Key Columns

• RESOURCE_ID / RESOURCE_TYPE — the identifier and type of the resource participating in the role association.
• ROLE_RELATE_ID — the unique identifier of the role-to-resource relationship record (also surfaced as ID1).
• ROLE_ID — the role identifier used to join to other role-based views.
• NAME / DESCRIPTION — the language-translated role name and description from JTF_RS_ROLES_TL.
• STATUS — a derived value computed with DECODE/SIGN logic: 'I' if the current date precedes START_DATE_ACTIVE or follows END_DATE_ACTIVE, otherwise 'A' for active.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the association.
• ROLE_TYPE_CODE / ROLE_CODE — classification attributes of the role.
• DELETE_FLAG / SEEDED_FLAG — deletion and Oracle-seeded indicators.
• MEMBER_FLAG, ADMIN_FLAG, LEAD_FLAG, MANAGER_FLAG — role-capability indicators. The searched term manager_flag maps to the MANAGER_FLAG column, which identifies whether the association carries manager responsibilities, and which is commonly used to filter for managerial role assignments in Contracts.

Common Use Cases and Queries

Typical scenarios include auditing Contracts role assignments, filtering managerial roles, and validating active associations for reporting.

• List all active Contracts role associations where the manager capability is set:

SELECT role_id, name, resource_id, status, manager_flag
FROM   apps.okx_resource_roles_v
WHERE  status = 'A'
AND    manager_flag = 'Y';

• Enumerate roles with any leadership or administrative capability:

SELECT role_code, name, lead_flag, admin_flag, manager_flag
FROM   apps.okx_resource_roles_v
WHERE  lead_flag = 'Y' OR admin_flag = 'Y' OR manager_flag = 'Y';

• Report associations by effective date range:

SELECT role_relate_id, role_id, name, start_date_active, end_date_active
FROM   apps.okx_resource_roles_v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE))
                          AND NVL(end_date_active, TRUNC(SYSDATE));

Because the view is a simple join with no aggregation, it performs well as a reporting source and can be safely joined to other JTF resource and Contracts tables by ROLE_ID or RESOURCE_ID. As with all APPS views, queries should be executed with the appropriate product responsibility and MO: Operating Unit context where relevant.