Results for “jtf_rs_role_code”
2 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ASO_APR_JTF_SALES_APPROVERS_V is a reporting view in the ASO - Order Capture module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It exposes the set of sales approvers configured in the CRM/Resource Manager foundation by joining group definitions, role-to-resource relations, and role definitions. The view is provided primarily to support approval routing and inquiry logic used by Oracle Quoting (ASO) and related modules such as Approvals Management (AME), where approvers are identified by membership in a resource group bound to a role whose role code is SALES_APPROVER.
The view is documented as "Not implemented in this database," which indicates that in a standard or minimally configured instance the object may not be physically deployed or populated. Where it is deployed, it supplies a normalized roster of approvers (group-level and role-level attributes) that can drive reporting, validation, and integration needs around sales approvals. Because the view is defined over the JTF_RS (Resource Manager) family of tables, it is itself a read-only presentation layer rather than a transactional object.
Underlying Base Objects
The ETRM metadata does not enumerate referenced base objects, but the embedded view text documents the exact definition. The view is a three-way join:
- JTF_RS_GROUPS_VL (T1) — resource groups, exposing GROUP_ID, GROUP_NAME, GROUP_DESC, and their active date range (START_DATE_ACTIVE, END_DATE_ACTIVE).
- JTF_RS_ROLE_RELATIONS_VL (T2) — relations binding a role to a resource (here filtered to ROLE_RESOURCE_TYPE = 'RS_GROUP').
- JTF_RS_ROLES_VL (T3) — role definitions exposing ROLE_ID, ROLE_CODE, ROLE_TYPE_CODE, ROLE_NAME, and ROLE_DESC.
The join conditions tie groups to role relations (T1.GROUP_ID = T2.ROLE_RESOURCE_ID) and relations to roles (T2.ROLE_ID = T3.ROLE_ID), with the HARDCODED FILTER T3.ROLE_CODE = 'SALES_APPROVER'. This is the single most important characteristic of the view: it isolates exactly those groups bound to the SALES_APPROVER role, and no other roles.
Key Columns
Columns are qualified in the view with the JTF_RS_ prefix, though the join aliases map them to underlying table columns. Notable columns include:
- JTF_RS_GROUP_ID — primary identifier of the resource group that represents an approver unit.
- JTF_RS_GROUP_NAME / JTF_RS_GROUP_DESC — descriptive attributes of the approver group.
- JTF_RS_ROLE_ID — identifier of the role assigned to the group; restricted to SALES_APPROVER.
- JTF_RS_ROLE_CODE — the role code value; the constant 'SALES_APPROVER' due to the view filter, which is why a search for role_code typically resolves to this object.
- JTF_RS_ROLE_TYPE_CODE, JTF_RS_ROLE_NAME, JTF_RS_ROLE_DESC — role classification and descriptive metadata.
- JTF_RS_ROLE_RELATE_ID, JTF_RS_ROLE_RESOURCE_TYPE — identify the relation record and confirm the resource type is 'RS_GROUP'.
- Date columns (JTF_RS_GROUP_START_DATE, JTF_RS_GROUP_END_DATE, JTF_RS_ROLE_RELAT_START_DATE, JTF_RS_ROLE_RELAT_END_DATE) — enable effective-dated filtering of active approvers.
Common Use Cases and Queries
Typical uses include auditing which groups are configured as sales approvers, feeding approval-routing logic, and validating configuration during implementation. A basic query:
SELECT JTF_RS_GROUP_NAME, JTF_RS_ROLE_CODE, JTF_RS_ROLE_NAME FROM ASO_APR_JTF_SALES_APPROVERS_V;- Filter for currently active approvers using the date columns.
- Join to JTF_RS_GROUP_MEMBERS or related resource tables to expand the group to individual approvers for notification or reporting.
Because the view is not implemented in many instances, confirm its deployment status before relying on it for production reporting; the underlying JTF_RS tables remain the authoritative source.
-
Not implemented in this database·Explore ASO module →
-
Not implemented in this database·Explore ASO module →