Search Results jtf_rs_dbi_conc_pub




Overview
Explore in AI Chat

Overview

JTF_RS_DBI_CONC_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PUB (public) API. It belongs to the CRM Resource Manager (JTF_RS) module family and supports the DBI (Denormalized Business Intelligence) layer that maintains pre-aggregated resource group and manager hierarchy data. The package is specifically oriented around concurrent-program driven population of denormalized resource group tables, which support downstream reporting, territory, and resource-selection logic without repeatedly joining the full normalized resource schema.

In practical terms, the package resolves group identifiers and resource group memberships and persists them into denormalized staging structures such as JTF_RS_DBI_DENORM_RES_GROUPS and JTF_RS_GROUPS_DENORM. This enables faster lookups of a resource's associated groups, first-login group, service group, and field service district assignments. The package is designed to be run in batch or concurrent contexts rather than in interactive online transactions.

Key Procedures and Functions

The documented procedures and functions reflect two responsibilities: resolving group identifiers and populating denormalized tables.

  • POPULATE_MAIN — The primary entry point that orchestrates the overall population of DBI denormalized resource group data. It typically invokes the supporting routines below in sequence.
  • POPULATE_RES_GRP — Populates resource group denormalization records, writing resolved group memberships into the denormalized resource group structures.
  • POPULATE_FLD_SRV_DISTRICT — Populates field service district assignments, mapping resources to their applicable district for field service processing.
  • GET_SG_ID — Retrieves the service group (SG) identifier for a given context or resource.
  • GET_SG_ID_ALL_LOGIN — Retrieves the service group identifier applicable across all login groups, an aggregate variant of GET_SG_ID.
  • GET_FSG_ID — Retrieves the field service group (FSG) identifier for the specified context or resource.
  • GET_FSG_ID_ALL_LOGIN — Returns the field service group identifier across all login groups.
  • GET_FIRST_LOGIN_GROUP_ID — Returns the identifier of the resource's first (default) login group, used when establishing the primary group context for a resource.

The GET_* routines are lookup functions; the POPULATE_* routines are write operations that fill the denormalized tables consumed by reporting and resource lookup logic. Parameter lists are not exposed in the documented metadata and should not be assumed.

Tables Accessed

The package reads and writes the CRM resource group tables, including JTF_RS_GROUPS_B and JTF_RS_GROUPS_DENORM (group definitions and their denormalized counterpart), JTF_RS_GROUP_MEMBERS (group membership), and JTF_RS_GROUP_USAGES (how groups are used). Manager hierarchy data is sourced from JTF_RS_REP_MANAGERS and JTF_RS_RESOURCE_EXTNS, while role information comes from JTF_RS_ROLES_B. The denormalized targets JTF_RS_DBI_DENORM_RES_GROUPS and JTF_RS_DBI_DENORM_RES_GROUPS_S (with its _S sequence/security companion) and JTF_RS_DBI_MGR_GROUPS with JTF_RS_DBI_MGR_GROUPS_S receive populated data. FND_APPLICATION, FND_PRODUCT_INSTALLATIONS, and FND_ORACLE_USERID provide application and installation context, and BIS_SYSTEM_DATE supplies the current system date for effective-dating logic.

Usage Notes

This package is intended for concurrent program execution and scheduled batch maintenance rather than form-level or online invocation. It is normally scheduled to refresh DBI denormalized resource group and manager group data after changes to resource groups, memberships, or manager hierarchies, keeping reporting and resource-selection queries performant. Custom code may call the GET_* lookup functions to resolve service group, field service group, or first-login group identifiers, but the POPULATE_* routines should be invoked only through the delivered concurrent programs to preserve data integrity and avoid overlapping refresh runs. The ETRM metadata records no inbound dependencies from other packages, so the package operates as a leaf batch utility within the JTF_RS DBI layer.