Results for “position_title”

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

Overview

GHR_MASS_AWARDS_PREVIEW_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the GHR product family (US Federal Human Resources) and, as its name implies, exposes the preview information used by the Mass Award process. Mass awards in the federal HR context allow a personnel office to grant the same award — a cash award, a time-off award, or a similar recognition — to multiple employees in a single mass action. Before that action is committed through the award workflow, the application displays a preview grid so the operator can review and deselect individual employees. This view supplies the rows and columns for that preview grid.

The view is purely a presentation and reporting construct. It does not store data; it projects and joins columns from the underlying personnel-action request tables into a single, denormalized result set suitable for a self-service or OAF-based page, an Oracle Reports layout, or an ad-hoc query. Because the view text is shipped as part of the APPS schema and marked VALID, it can be queried directly by custom reports, extracts, and integration code, although the usual caveat applies regarding the volatility of non-public EBS view definitions across patch levels.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• GHR_PA_REQUESTS (aliased PAR) — the driving table. It holds the mass action header and line rows for personnel actions, including the award amount, the award unit of measure, the award percentage, the effective date, and the initial selection flag.
• GHR_PA_REQUEST_EXTRA_INFO (aliased REI) — the descriptive-flexfield-style extension table that stores award-specific attributes keyed by PA_REQUEST_ID and INFORMATION_TYPE.

The two objects are outer-joined: REI.PA_REQUEST_ID(+) = PAR.PA_REQUEST_ID with REI.INFORMATION_TYPE(+) = 'GHR_US_PAR_AWARDS_BONUS'. This is an outer join on the extra-information side, so a mass-award row is still returned even when no matching award bonus extra-information record exists; the agency, type, group award, and tangible benefit columns then come back as NULL.

Several WHERE predicates tightly scope the result set: MASS_ACTION_ID IS NOT NULL, PERSON_ID IS NOT NULL, NVL(RPA_TYPE,'$') = 'A' (the personnel action type that designates an award), and PA_NOTIFICATION_ID IS NULL. The last predicate excludes rows that have already been routed to a notification, which is what distinguishes a preview candidate from a committed or in-flight action.

Key Columns

The view renames several base columns for readability, and these aliases are the names a report developer should use:

• MASS_AWARD_ID (from PAR.MASS_ACTION_ID) and PA_REQUEST_ID — the identifiers of the mass action and of the individual personnel action request line.
• SELECT_FLAG (from PAR.MASS_ACTION_SELECT_FLAG) — the flag indicating whether the employee row is currently selected for inclusion in the mass award. This is the column most closely associated with the concept a user searches for as select_flag, and it drives the check-box state in the preview grid.
• PERSON_ID, EMPLOYEE_LAST_NAME, EMPLOYEE_FIRST_NAME, EMPLOYEE_MIDDLE_NAMES, EMPLOYEE_NATIONAL_IDENTIFIER — employee identity and name attributes.
• EFFECTIVE_DATE, AWARD_AMOUNT, AWARD_UOM, AWARD_PERCENTAGE — the award terms themselves.
• AWARD_AGENCY_CODE, AWARD_TYPE, GROUP_AWARD_ID, TANGIBLE_BENEFIT_DOLLARS, DATE_AWARD_EARNED — sourced from the extra-information table (REI_INFORMATION3, 4, 6, 7, and 9 respectively).
• BASIC_PAY, ORGANIZATION_ID, DUTY_STATION_CODE, DUTY_STATION_DESC, AGENCY_CODE, AGENCY_CODE_DESC, POI, POSITION_OCCUPIED, POSITION_TITLE, PAY_PLAN, GRADE_OR_LEVEL, OCC_CODE, OFFICE_SYMBOL, COMMENTS — positional and organizational context, making the view useful for producing an audit-ready listing without additional joins.

Common Use Cases and Queries

Typical uses include previewing an in-progress mass award before submission, auditing who was and was not selected, and feeding downstream extracts. To list the selected employees for a given mass action:

SELECT MASS_AWARD_ID, PERSON_ID, EMPLOYEE_LAST_NAME, EMPLOYEE_FIRST_NAME, AWARD_AMOUNT, AWARD_UOM, SELECT_FLAG FROM APPS.GHR_MASS_AWARDS_PREVIEW_V WHERE MASS_AWARD_ID = :mass_award_id AND SELECT_FLAG = 'Y' ORDER BY EMPLOYEE_LAST_NAME;

To count selected versus unselected rows for a mass action:

SELECT SELECT_FLAG, COUNT(*) FROM APPS.GHR_MASS_AWARDS_PREVIEW_V WHERE MASS_AWARD_ID = :mass_award_id GROUP BY SELECT_FLAG;

To review all award rows with their organizational context:

SELECT PERSON_ID, POSITION_TITLE, GRADE_OR_LEVEL, DUTY_STATION_DESC, EFFECTIVE_DATE, AWARD_AMOUNT FROM APPS.GHR_MASS_AWARDS_PREVIEW_V WHERE MASS_AWARD_ID = :mass_award_id;

Because the view is not multi-org partitioned and carries no security predicate of its own, responsibility-level data access must be enforced by joining to PER_ALL_ASSIGNMENTS_F or by applying the appropriate business-group and security-profile filters in the calling report.