Search Results payroll_earning_date

Overview

PSPFV_PAYROLL_TRANS_CONTROLS is a read-only Oracle EBS view in the PSP (Labor Distribution) module. It presents payroll transaction control information — the summarized debit and credit activity generated when payroll results are transformed into labor distribution and General Ledger entries. The view functions as a consolidated reporting and integration layer, joining the core payroll control record in PSP_PAYROLL_CONTROLS to descriptive payroll, period, action, organization, and ledger attributes so that downstream reporting, reconciliation, and interface processes can query a single, denormalized row per payroll control.

The "F" in the name and the presence of the "_LA:..." descriptive flexfield token in the view text indicate this is a flexfield-enabled view, exposing a descriptive flexfield context segment (PAYROLL_SOURCE_TYPE) that is resolved at query time against PSP_LOOKUPS. The view is declared WITH READ ONLY, reinforcing its role as a query-only presentation object rather than a data-entry surface. In the referenced database, the object is not implemented, meaning the SQL is documented but no physical object exists in that instance.

Underlying Base Objects

The view is defined over six joined objects:

• PSP_PAYROLL_CONTROLS (PPC) — the driving table holding control totals, status, batch name, source code, and phase columns.
• PAY_PAYROLLS_F (PPF) — supplies PAYROLL_NAME; joined by payroll and by the time-period start date falling within the payroll's effective date range.
• PER_TIME_PERIODS (PTP) — supplies PERIOD_NAME, joined on TIME_PERIOD_ID.
• PAY_PAYROLL_ACTIONS (PPA) — supplies payroll action dates (effective, earned, advice), joined on PAYROLL_ACTION_ID.
• HR_ALL_ORGANIZATION_UNITS (HOU) — supplies the business group name, joined on ORGANIZATION_ID.
• GL_SETS_OF_BOOKS (GL) — supplies the set of books name, joined on SET_OF_BOOKS_ID.

The ETRM 12.2.2 metadata documents no referenced base objects, so these relationships are derived from the published view text. Joins are all inner joins, so a control row appears only when its payroll, period, action, organization, and ledger all resolve.

Key Columns

• PAYROLL_CONTROL_ID — primary identifier of the payroll control record.
• BATCH_RUN_ID / BATCH_NAME / ADJ_SUM_BATCH_NAME — batch and adjustment-summary identifiers for the distribution run.
• PAYROLL_SOURCE_CODE and PAYROLL_SOURCE_TYPE — source code plus its flexfield meaning from PSP_LOOKUPS.
• SET_OF_BOOKS_ID / SET_OF_BOOKS_NAME and BUSINESS_GROUP_ID / BUSINESS_GRP_NAME — ledger and business group identifiers and names.
• NUMBER_OF_CREDIT_TRANSACTIONS / NUMBER_OF_DEBIT_TRANSACTIONS — counts of generated credit and debit transactions.
• BATCH_STATUS_FLAG — the status code of the control/batch, governing whether the payroll distribution has been run, validated, or transferred. This is the column most frequently searched.
• TOTAL_* amounts — debit/credit totals for base transactions, sublines, distributed amounts, Grants, and GL share amounts, enabling reconciliation across distribution stages.
• GL_PHASE / GMS_PHASE — phase indicators for GL and Grants processing.
• PAYROLL_NAME, PERIOD_NAME, PAYROLL_EFFECTIVE_DATE, PAYROLL_EARNING_DATE, PAYROLL_ADVICE_DATE — descriptive payroll context.

Common Use Cases and Queries

Typical use is monitoring payroll distribution status and reconciling control totals before GL transfer.

• List batches by status: SELECT batch_name, batch_status_flag, gl_phase FROM pspfv_payroll_trans_controls WHERE batch_status_flag = 'C';
• Reconcile debit/credit totals per payroll: SELECT payroll_name, period_name, total_debit_amount, total_credit_amount FROM pspfv_payroll_trans_controls ORDER BY period_name;
• Identify undistributed sublines: SELECT payroll_control_id, total_sublines_debit_amount - total_dist_debit_amount FROM pspfv_payroll_trans_controls;
• Report by ledger and business group for a period: select names together with transaction counts filtered on PERIOD_NAME and SET_OF_BOOKS_NAME.

Because the view is read-only and pre-joined, it is suited to concurrent-report queries and downstream integrations that require batch-level distribution status without navigating the underlying payroll tables directly.