Results for “ghr_routing_lists”

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

Overview

GHR_ROUTING_LISTS is a table in the HR schema owned by the GHR - US Federal Human Resources product module within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores routing list definitions used to organize and direct routing activity across US Federal HR processes. Each row represents a named routing list, optionally associated with a routing group, and serves as the central reference point for routing history and routing list membership records.

In Data Vault modeling terms, the table's FK structure classifies it heuristically as hub-leaning. It carries a single-column surrogate primary key, a unique business key, and one foreign key referencing a parent grouping table, while three separate child tables reference it. This pattern is consistent with a hub entity that anchors descriptive content in downstream satellites and membership links.

Key Information Stored

The table contains 9 documented columns. The most significant are:

• ROUTING_LIST_ID — the surrogate primary key, defined by the GHR_ROUTING_LISTS_PK constraint. It uniquely identifies each routing list and is the column referenced by all child tables.
• NAME — the business-key candidate, enforced by the unique index GHR_ROUTING_LISTS_UK1. This is the user-facing identifier for the routing list.
• ROUTING_GROUP_ID — foreign key to GHR_ROUTING_GROUPS, indicating the routing group to which the list belongs.
• PRIMARY_ROUTING_LIST_FLAG — indicates whether the routing list is designated as the primary list, a common control for default selection logic.

Five standard Oracle EBS audit columns complete the structure: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE. These support change tracking and are populated automatically by the application tier.

Common Use Cases and Queries

Typical usage centers on determining which routing lists exist, how they group, and which routing events have occurred against them. A common lookup pattern resolves the list name and its parent group:

• Reporting on routing lists by group: select ROUTING_LIST_ID, NAME, PRIMARY_ROUTING_LIST_FLAG from GHR_ROUTING_LISTS where ROUTING_GROUP_ID = :p_group_id.
• Resolving list membership: join GHR_ROUTING_LISTS to GHR_ROUTING_LIST_MEMBERS on ROUTING_LIST_ID to identify members associated with each list.
• Auditing routing activity: join to GHR_PA_ROUTING_HISTORY or GHR_PD_ROUTING_HISTORY on ROUTING_LIST_ID to trace historical routing events for a given list.
• Identifying primary lists: filter on PRIMARY_ROUTING_LIST_FLAG to isolate lists used as defaults in routing configuration.

Because NAME carries a unique constraint, direct lookups by name are efficient and reliable for integration and data-migration scripts.

Related Objects

The following objects participate in documented foreign key relationships with GHR_ROUTING_LISTS:

• GHR_ROUTING_GROUPS — parent table referenced by GHR_ROUTING_LISTS.ROUTING_GROUP_ID.
• GHR_ROUTING_LIST_MEMBERS — child table referencing GHR_ROUTING_LISTS.ROUTING_LIST_ID; holds list membership detail.
• GHR_PA_ROUTING_HISTORY — child table referencing ROUTING_LIST_ID; captures routing history for personnel action routing.
• GHR_PD_ROUTING_HISTORY — child table referencing ROUTING_LIST_ID; captures routing history for position description routing.

Together these objects form the routing configuration and history cluster within the GHR module, with GHR_ROUTING_LISTS acting as the central hub that links groups, members, and historical routing records. Analysts should account for the master-detail dependency when purging or migrating routing configuration data, since child history and membership rows reference the list key directly.