Results for “jtf_rs_rep_managers_vl”

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

Overview

The view JTF_RS_REP_MANAGERS_VL belongs to the JTF – CRM Foundation product family and resides in the APPS schema. It presents the denormalized reporting hierarchy that links resources to their managers, administrators, and other related personnel across resource groups. Its documented purpose is to expose the member-to-manager and member-to-administrator relationships maintained within the CRM resource management model, allowing reports, forms, and integrations to resolve lines of reporting without traversing the full underlying structure.

Because the object is a view and not a table, it carries no independent storage. Its value in EBS 12.1.1 and 12.2.2 environments lies in providing a stable, denormalized access path to hierarchy information used by resource administration, territory and assignment processing, and reporting on organizational structure. The denormalized identifier and level columns enable efficient retrieval of complete chains of authority rather than requiring recursive queries against transactional tables.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over a single referenced base object: JTF_RS_REP_MANAGERS, accessed through a synonym. The view text confirms this, selecting all exposed columns from the alias MGR referencing that table. No joins are present in the definition, so the view functions as a filtered and column-projected reflection of the base table rather than a composite of multiple sources. This means any insert, update, or delete activity affecting reporting hierarchy records originates in the base table, and the view inherits the transactional currency of that source. In a typical installation the owner of the base object is APPS or the JTF schema, and the synonym resolves transparently for callers referencing the view name.

Key Columns

The view exposes the full denormalized hierarchy record. The principal columns include:

• DENORM_MGR_ID — the denormalized manager identifier, providing the unique handle for each hierarchy row.
• PERSON_ID and RESOURCE_ID — identify the member within the hierarchy, linking to the person and resource entities respectively.
• CATEGORY — the resource or membership category used to qualify the relationship.
• MANAGER_PERSON_ID — the person record of the manager or administrator to whom the member reports.
• GROUP_ID — the resource group in which the relationship applies, since hierarchy is tracked across groups.
• REPORTS_TO_FLAG — indicates whether the relationship represents a direct reporting line.
• HIERARCHY_TYPE — classifies the nature of the hierarchy entry, differentiating among manager, administrator, and other relationship types. This is the column most commonly used to filter the view for a specific relationship class.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date range of the relationship.
• DENORM_LEVEL — the depth or level of the member within the denormalized hierarchy, supporting ordered traversal.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus the fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY for descriptive flexibility.

Common Use Cases and Queries

Typical scenarios include determining a resource's manager for approval routing, rendering organizational charts, populating administrator assignments across groups, and resolving escalation paths in CRM flows. The HIERARCHY_TYPE column is frequently the discriminating filter, since a single member may appear in multiple hierarchy roles.

The following query returns active manager relationships for a given resource:

• SELECT person_id, manager_person_id, hierarchy_type, denorm_level
• FROM jtf_rs_rep_managers_vl
• WHERE resource_id = :p_resource_id
• AND reports_to_flag = 'Y'
• AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

To enumerate all administrator relationships within a specific group, the predicate would instead filter on hierarchy_type and group_id, ordering by denorm_level to reconstruct the chain. Because the view simply projects the base table, these queries benefit from the indexes defined on JTF_RS_REP_MANAGERS, and no aggregation is required to obtain the denormalized level and manager identifier.