Results for “ghr_payroll”

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

Overview

GHR_PAYROLL is a table owned by the HR schema within the GHR — US Federal Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in the E-Business Suite Technical Reference Manual (ETRM) as a valid, standalone object whose stated purpose is to supply data to the payroll interface for the SF113A report, a U.S. federal reporting requirement covering payroll and allowance data. The table therefore functions as a staging and reporting store rather than as a transactional driver of the core Oracle Payroll engine.

The object has a narrow, purpose-built footprint of eleven documented columns and a single primary key constraint, GHR_PAYROLL_PK, defined on PAYROLL_ID. The metadata classifies the table heuristically as standalone under the Data Vault model. As a modeling suggestion, this indicates that GHR_PAYROLL behaves as a satellite-like record keyed to a payroll or person event, with no documented foreign-key dependencies to other hubs or links. Because no FK relationships are declared, referential integrity to person or assignment records is managed at the application layer rather than enforced in the database.

Key Information Stored

The table captures a dated payroll amount record associated with a person for reporting purposes. The most significant documented columns are:

• PAYROLL_ID — the surrogate primary key and the single column of the GHR_PAYROLL_PK constraint. It uniquely identifies each payroll reporting row.
• PERSON_ID — identifies the employee or person to whom the payroll amounts belong. This is the principal business-key candidate for linking to person records, although the metadata does not document a unique index on it.
• DATE_FROM and DATE_TO — the effective date range for the payroll data, defining the period over which the reported amounts apply.
• TOTAL_SALARY_AMOUNT — the aggregate salary figure for the person over the effective period.
• LUMP_SUM_AMOUNT — a separate amount column capturing lump-sum payments distinct from regular salary.
• LAST_UPDATE_DATE, CREATION_DATE — standard audit timestamps recording when the row was created and last modified.
• LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO columns identifying the user and login session responsible for the row's creation and most recent change.

The only documented unique index is GHR_PAYROLL_PK on PAYROLL_ID, making the surrogate key the sole enforced business-key candidate. PERSON_ID combined with DATE_FROM and DATE_TO is the natural grain suggested by the column set, but this is not enforced by a unique constraint in the documented schema.

Common Use Cases and Queries

The primary use case is extraction of SF113A report data through the payroll interface. Typical queries select payroll rows by person and effective period, or aggregate amounts across a reporting window.

• Reporting by person and period: SELECT person_id, date_from, date_to, total_salary_amount, lump_sum_amount FROM hr.ghr_payroll WHERE person_id = :person_id AND date_from >= :start_date AND date_to <= :end_date ORDER BY date_from;
• Period totals: SELECT SUM(total_salary_amount), SUM(lump_sum_amount) FROM hr.ghr_payroll WHERE date_from BETWEEN :p_start AND :p_end;
• Audit and change tracking using LAST_UPDATE_DATE to identify recently modified rows feeding the interface.
• Reconciliation of staged payroll amounts against Oracle Payroll results prior to SF113A submission.

Related Objects

The documented metadata records no foreign keys, so relationships are implicit rather than enforced. The following objects are the most significant integration points:

• PER_ALL_PEOPLE_F — joined via PERSON_ID to resolve the person identity behind each PAYROLL_ID row.
• The GHR payroll interface program that reads GHR_PAYROLL to produce the SF113A report.
• Oracle Payroll run and assignment results tables, used to reconcile TOTAL_SALARY_AMOUNT and LUMP_SUM_AMOUNT.
• GHR_PAYROLL_PK — the primary key constraint itself, referencing PAYROLL_ID.

Because the table is standalone, dependent logic resides in the payroll interface and GHR reporting layer rather than in database-level referential constraints.