Results for “ssp_days_due”

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

Overview

SSP_SSP_ENTRIES_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (SSP) module. It exposes nonrecurring element entries associated with Statutory Sick Pay (SSP) and the SSP Corrections element. The view denormalizes payroll entry header, input value, and assignment data into a single reporting-friendly rowset, resolving the individual input values stored in PAY_ELEMENT_ENTRY_VALUES_F (FROM, TO, AMOUNT, RATE, QUALIFYING DAYS, SSP DAYS DUE, WITHHELD DAYS, and SSP WEEKS) into discrete, strongly typed columns using FND_DATE and FND_NUMBER conversion routines.

Because SSP is a legislative UK payroll feature, this view supports statutory reporting and reconciliation of sick pay processed through element entries. It is not a transactional entry form; it is a query surface for retrieving SSP-related nonrecurring entries together with the person, assignment, and element link context required for audit and downstream processing.

Underlying Base Objects

The view is defined over core Oracle Payroll tables, joined to HR security and conversion utilities. The ETRM 12.2.2 metadata documents the following referenced base objects:

• PAY_ELEMENT_ENTRIES_F — the element entry header, filtered to creator type 'S'.
• PAY_ELEMENT_ENTRY_VALUES_F — the input values (FROM, TO, AMOUNT, RATE, QUALIFYING DAYS, SSP DAYS DUE, WITHHELD DAYS, SSP WEEKS) per entry.
• PAY_INPUT_VALUES_F — defines the input value names used to pivot on.
• PAY_ELEMENT_TYPES_F — filters element names to 'STATUTORY SICK PAY' and 'SSP CORRECTIONS'.
• PAY_ELEMENT_LINKS_F — links element types to assignments via an EXISTS subquery.
• PER_ASSIGNMENTS_F — resolves the assignment to a person via PAF.PERSON_ID.
• FND_DATE and FND_NUMBER — packages converting canonical screen entry values to native date and number types.
• HR_GENERAL and HR_SECURITY — HR utility and security packages available to the view context.

Date effectivity is enforced throughout: entries are matched across PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, and PER_ASSIGNMENTS_F by comparing EEV.EFFECTIVE_START_DATE against each object's effective start and end dates.

Key Columns

• TARGET_ENTRY_ID — the target element entry identifier, the column referenced in the user's search and a key linkage for corrections against an original SSP entry.
• ELEMENT_ENTRY_ID — the unique identifier of the SSP or SSP Corrections element entry.
• ELEMENT_LINK_ID — the element link connecting the element type to the assignment.
• ASSIGNMENT_ID and PERSON_ID — the assignment and person to whom the entry belongs.
• FROM / TO date columns — FND_DATE-converted start and end of the SSP period.
• AMOUNT and RATE — FND_NUMBER-converted monetary values.
• QUALIFYING_DAYS, SSP_DAYS_DUE, WITHHELD_DAYS, SSP_WEEKS — FND_NUMBER-converted SSP entitlement and calculation quantities.
• A DECODE expression returns 'N' when the element name is 'STATUTORY SICK PAY' and 'Y' otherwise, distinguishing the SSP element from SSP Corrections.
• CREATOR_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and ROW_ID (MIN of PAY_INPUT_VALUES_F.ROWID for the 'FROM' input) provide audit and row identification attributes.

Common Use Cases and Queries

Typical scenarios include reconciling SSP and SSP Corrections entries for a pay period, auditing withheld and qualifying days, and tracing correction entries back to their original element entry through TARGET_ENTRY_ID.

• Listing all SSP entries for a person or assignment within a date range.
• Identifying SSP Corrections records and their corresponding TARGET_ENTRY_ID.
• Summarising amounts, rates, and SSP weeks across a payroll run.
• Building HR/legislative extracts requiring canonical-to-native value conversion.

Illustrative query:

SELECT person_id, assignment_id, element_entry_id, target_entry_id,
       amount, rate, qualifying_days, ssp_days_due, withheld_days, ssp_weeks
FROM apps.ssp_ssp_entries_v
WHERE person_id = :p_person_id
  AND effective_start_date BETWEEN :p_start AND :p_end;

Because rows are secured through the HR security model and filtered by effectivity, queries should always constrain by date and, where relevant, by person or assignment to return accurate, current results.