Results for “routing_list_member_id”

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

Overview

GHR_ROUTING_LIST_MEMBERS is a transactional detail table owned by the HR schema and delivered as part of the GHR — US Federal Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the individual membership rows that make up a routing list. A routing list defines an ordered set of recipients to whom documents, notifications, or workflow items are distributed, and GHR_ROUTING_LIST_MEMBERS records each participant or group entry that participates in that distribution sequence. The object is registered as VALID in the ETRM repository, confirming that it is a supported, documented database object in the current release.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is best modeled as a link. This classification is a modeling suggestion rather than a functional designation: the table resolves the relationship between routing lists and the users or groupboxes that belong to them, and it carries sequence ordering plus standard audit attributes. It is not a standalone hub of business entities, nor does it appear to be a pure descriptive satellite.

Key Information Stored

The documented physical schema contains ten columns. The most significant are:

• ROUTING_LIST_MEMBER_ID — the surrogate primary key, enforced by the index GHR_ROUTING_LIST_MEMBERS_PK. It uniquely identifies each membership row.
• ROUTING_LIST_ID — foreign key to GHR_ROUTING_LISTS, identifying the parent routing list to which the member belongs.
• SEQ_NUMBER — the ordinal position of the member within the routing list. Together with ROUTING_LIST_ID it forms the unique business key enforced by GHR_ROUTING_LIST_MEMBERS_UK, guaranteeing that no two members occupy the same sequence slot on the same list.
• USER_NAME — the identifier of the individual recipient, where the member is a named user rather than a group.
• GROUPBOX_ID — foreign key to GHR_GROUPBOXES, identifying a group container when the member is defined as a group rather than an individual.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS audit columns that record who created and last modified each membership row and when.

The co-existence of USER_NAME and GROUPBOX_ID indicates that a routing list member may be either an individual or a group, and that the two are mutually exclusive in practice.

Common Use Cases and Queries

The primary reporting use case is reconstructing the ordered distribution sequence for a given routing list. A typical query joins the member table to its parent list and resolves the recipient:

• Retrieve members of a routing list in order: SELECT m.seq_number, m.user_name, m.groupbox_id FROM ghr_routing_list_members m WHERE m.routing_list_id = :list_id ORDER BY m.seq_number;
• Identify all lists containing a given user: SELECT routing_list_id FROM ghr_routing_list_members WHERE user_name = :user_name ORDER BY routing_list_id, seq_number;
• Detect group-based members: SELECT routing_list_id, seq_number, groupbox_id FROM ghr_routing_list_members WHERE groupbox_id IS NOT NULL;

These patterns support audit reporting on notification distribution, review of escalation or approval chains, and reconciliation of routing configuration between environments.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign key and primary key relationships:

• GHR_ROUTING_LISTS — parent table joined on GHR_ROUTING_LIST_MEMBERS.ROUTING_LIST_ID = GHR_ROUTING_LISTS.ROUTING_LIST_ID.
• GHR_GROUPBOXES — referenced when the member is a group, joined on GHR_ROUTING_LIST_MEMBERS.GROUPBOX_ID = GHR_GROUPBOXES.GROUPBOX_ID.
• GHR_ROUTING_LIST_MEMBERS_PK — the unique index on ROUTING_LIST_MEMBER_ID.
• GHR_ROUTING_LIST_MEMBERS_UK — the unique index on ROUTING_LIST_ID and SEQ_NUMBER.

Together these objects define the routing configuration used by GHR notification and workflow processing.