Search Results rs_party




Overview
Explore in AI Chat

Overview

APPS.JTF_RS_ALL_RESOURCES_VL is a consolidated, language-enabled (VL) view within the Oracle E-Business Suite Resource Manager (JTF_RS) schema, available in both release 12.1.1 and 12.2.2. It presents a unified directory of every resource type known to the Resource Manager subsystem by combining three separate source views — individual resources, resource groups, and resource teams — into a single result set through UNION ALL. The suffix "VL" indicates that the view exposes translated (language-dependent) name columns in addition to the base identifier data.

The view is central to reporting and integration because it allows a single query to return employees, partners, supplier contacts, parties, groups, and teams without the caller needing to know which underlying entity type a given resource belongs to. A RESOURCE_TYPE discriminator column is generated within the view body so that consumers can filter or classify rows at query time. This makes the view a frequent target for custom reports, Oracle Discoverer workbooks, OBIEE/BI Publisher data models, and interface programs that must resolve a resource identifier to a display name.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists the following referenced objects: HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), JTF_RS_GROUPS_VL (VIEW), JTF_RS_RESOURCE_DTLS_VL (VIEW), and JTF_RS_TEAMS_VL (VIEW).

The view text resolves as follows:

  • The first UNION ALL branch selects from JTF_RS_RESOURCE_DTLS_VL, aliased RSC. This supplies individual resource rows and derives RESOURCE_TYPE from the RSC.CATEGORY column through a DECODE expression.
  • The second branch selects from JTF_RS_GROUPS_VL, aliased GRP, returning group records with the literal type 'RS_GROUP'.
  • The third branch selects from JTF_RS_TEAMS_VL, aliased TM, returning team records with the literal type 'RS_TEAM'.

HR_GENERAL and HR_SECURITY are referenced by the underlying detail views to enforce organization and security (MO) filtering, so that the resources returned to a session respect the operating unit and security profile in force. The base detail views map to physical Resource Manager tables such as JTF_RS_RESOURCE_EXTNS, JTF_RS_GROUPS_B, and JTF_RS_TEAMS_B, joined to their _TL translation tables.

Key Columns

  • RESOURCE_ID — The primary identifier for the row. For individuals it is rsc.resource_id; for groups it is derived from group_id; for teams from team_id. Because the three sources are disjoint, this value is unique across the union.
  • RESOURCE_NUMBER — The user-facing resource number, group number, or team number.
  • RESOURCE_TYPE — A discriminator produced by DECODE on rsc.category. Documented mappings are EMPLOYEE→'RS_EMPLOYEE', PARTNER→'RS_PARTNER', SUPPLIER_CONTACT→'RS_SUPPLIER_CONTACT', PARTY→'RS_PARTY', OTHER→'RS_OTHER', TBH→'RS_TBH'; groups yield 'RS_GROUP' and teams yield 'RS_TEAM'. This is the value relevant to the "rs_party" search.
  • RESOURCE_NAME — The translated display name of the resource, group, or team.
  • EMAIL — Email address; NULL for teams and groups where not applicable.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating for the resource record.
  • PHONE — Telephone number, populated only for individual resources; NULL for groups and teams.
  • PERSON_PARTY_ID — The TCA party identifier linking an individual resource to the trading community model; NULL for groups and teams (cast via to_number(NULL)).
  • ORG_ID / ORG_NAME — Operating unit context carried only by the individual-resource branch.

Common Use Cases and Queries

The view is most often used to drive resource list of values (LOVs) and cross-entity reporting. A typical query filtering on the party resource type, consistent with the "rs_party" search, is:

  • SELECT resource_id, resource_number, resource_name, email FROM apps.jtf_rs_all_resources_vl WHERE resource_type = 'RS_PARTY' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);
  • To enumerate all groups and teams: SELECT resource_type, resource_name FROM apps.jtf_rs_all_resources_vl WHERE resource_type IN ('RS_GROUP','RS_TEAM');
  • To join resources to a TCA party: SELECT r.resource_name, r.resource_type, p.party_name FROM apps.jtf_rs_all_resources_vl r JOIN apps.hz_parties p ON p.party_id = r.person_party_id;

Because HR_SECURITY is applied beneath the view, results are automatically restricted to the organizations and resources the querying user is authorized to see, which is why the view is preferred over direct queries against the underlying Resource Manager tables in secured reporting environments.