Results for “ghr_mass_actions_preview”

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

Overview

The HR.GHR_MASS_ACTIONS_PREVIEW table is a staging and review structure within the Oracle E-Business Suite US Federal Human Resources (GHR) module. Its documented purpose is to present employee and position detail to the user based on the selection criteria entered during a mass action or mass personnel action process. Rather than committing changes directly, the mass action flow first populates this table so that the affected population — employees, positions, and their associated pay and organizational attributes — can be previewed, refined, and selectively confirmed before final processing.

The table carries a heuristic Data Vault classification of standalone, meaning the mining of foreign key structure did not surface the dense relationship pattern typical of a link or satellite. As a modeling suggestion, it is best treated as a transient, transaction-scoped staging entity keyed by a surrogate identifier rather than as a durable hub or link in a Data Vault model. Its lifecycle is tied to a user session, and rows are generally short-lived, reflecting a working set rather than a permanent record of the enterprise.

Key Information Stored

The table is unusually wide, with 117 documented columns, reflecting the breadth of attributes required to describe a federal personnel action. The single-column primary key is MASS_ACTION_PREVIEW_ID, which is also the sole unique index documented (GHR_MASS_ACTIONS_PREVIEW_PK) and therefore the only documented business-key candidate. The most significant columns include:

• SESSION_ID — ties the preview rows to the user's mass action session, delimiting the working set.
• MASS_ACTION_TYPE and UI_TYPE — identify the nature of the action being previewed and its presentation mode.
• SELECT_FLAG — records whether the user has elected to include a given row in processing, the core interactive control of the preview.
• PERSON_ID, EMPLOYEE_NUMBER, and FULL_NAME — identify the employee affected.
• POSITION_ID, POSITION_NUMBER, POSITION_TITLE, and POSITION_SEQ_NO — identify the position involved.
• ORGANIZATION_ID, ORGANIZATION_NAME, ORG_STRUCTURE_ID, and POSITIONS_ORGANIZATION — capture the organizational context.
• PERSONNEL_OFFICE_ID and POI_DESC — the foreign key to GHR_POIS, identifying the servicing personnel office.
• From/to pay pairs such as FROM_BASIC_PAY/TO_BASIC_PAY, FROM_TOTAL_SALARY/TO_TOTAL_SALARY, FROM_LOCALITY_ADJ/TO_LOCALITY_ADJ, and the availability, AUO, supervisory differential, and retention allowance variants — the before-and-after compensation picture.
• GRADE_OR_LEVEL, PAY_PLAN, STEP_OR_RATE, and PAY_RATE_DETERMINANT — position classification and pay determination.
• EFFECTIVE_DATE — the date on which the proposed action takes effect.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Twenty-plus USER_ATTRIBUTE columns are available as descriptive flexfield targets.

Common Use Cases and Queries

The primary use case is review and verification of a mass action population before submission. A typical query retrieves all rows selected in a session for display or reporting:

• SELECT person_id, employee_number, full_name, position_number, from_basic_pay, to_basic_pay FROM ghr_mass_actions_preview WHERE session_id = :p_session AND select_flag = 'Y';
• Reconciliation of before-and-after pay: comparing FROM_* against TO_* columns to quantify the cost impact of a proposed mass pay adjustment.
• Organizational reporting: grouping by ORGANIZATION_NAME or PERSONNEL_OFFICE_ID to produce headcount and salary summaries for the affected population.
• Transfer actions: the presence of paired columns such as AGENCY_CODE_TRANSFER_FROM/AGENCY_CODE_TRANSFER_TO and the extensive TO_* set supports mass transfers between agencies, duty stations, and personnel offices.
• Audit and exception checking: detection of rows where the action was previewed but not selected.

Related Objects

The documented foreign key relationship is to GHR_POIS via PERSONNEL_OFFICE_ID, and a parallel reference exists through TO_PERSONNEL_OFFICE_ID. Beyond this, the table depends on the core HR objects that supply its content:

• PER_ALL_PEOPLE_F — source of PERSON_ID, EMPLOYEE_NUMBER, and FULL_NAME.
• PER_ALL_POSITIONS_F — source of POSITION_ID, POSITION_NUMBER, and position title data.
• HR_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS — source of ORGANIZATION_ID, ORGANIZATION_NAME, and ORG_STRUCTURE_ID.
• PER_ALL_ASSIGNMENTS_F — source of grade, pay plan, step, and assignment-level attributes.
• PAY_PAY_RATES / pay table objects — referenced through FROM_PAY_TABLE_IDENTIFIER and TO_PAY_TABLE_IDENTIFIER.
• Mass action concurrent programs and the GHR mass personnel action APIs that read and write this preview table during the confirm phase.