Results for “adjustment_type”

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

Overview

The PAY_PAYWSMEE_ADJUSTMENT view is a payroll diagnostic object owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) module. It exposes a curated list of element entries that represent an adjustment to another element entry. Rather than presenting all element entries, the view filters to only those entries whose ENTRY_TYPE is 'A' (adjustment) or 'R' (replacement), and whose associated input value carries the reserved name 'PAY VALUE'. This makes the view a focused reporting and integration surface for reconciling adjustments applied to an employee's pay element entries.

Because the view resolves adjustment semantics at query time — including currency formatting and a derived adjustment classification — it is particularly useful for auditing, troubleshooting, and downstream reporting where the raw payroll tables would otherwise require complex joins. It is a session-aware view, depending on FND_SESSIONS and USERENV('SESSIONID'), so effective dating is evaluated against the user's current session effective date.

Underlying Base Objects

The view is defined over the following documented base objects:

• PAY_ELEMENT_ENTRIES_F — supplies the entry header, including entry type, assignment, element link, and the TARGET_ENTRY_ID that links an adjustment to the entry it modifies.
• PAY_ELEMENT_ENTRY_VALUES_F — supplies the screen entry value for each input value belonging to the entry.
• PAY_ELEMENT_LINKS_F — the element link that ties an element type to its eligibility and effective dates.
• PAY_ELEMENT_TYPES_F — the element type definition, providing the currency code used in formatting.
• PAY_INPUT_VALUES_F — the input value definition; the view restricts to UPPER(NAME) = 'PAY VALUE'.
• FND_SESSIONS — resolves the session effective date used across all effective-date range predicates.
• HR_CHKFMT (PACKAGE) — invoked to format the entry value according to unit of measure and currency code.

All base references except the HR_CHKFMT package are synonyms resolved at runtime against their underlying _F tables and date-tracked (Dataliet) columns.

Key Columns

• ELEMENT_ENTRY_ID — primary identifier of the adjustment element entry.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — effective dating range for the entry.
• TARGET_ENTRY_ID — the element entry that this entry adjusts or replaces.
• ENTRY_TYPE — 'A' for adjustment, 'R' for replacement.
• ASSIGNMENT_ID / ELEMENT_LINK_ID — the assignment and element link context.
• INPUT_VALUE_ID — identifier of the input value (restricted to "PAY VALUE").
• SCREEN_ENTRY_VALUE — the raw value as entered on screen.
• ENTRY_VALUE — the formatted value, passed through HR_CHKFMT.CHANGEFORMAT.
• ADJUSTMENT_TYPE — a derived classification: ADD or SUBTRACT for adjustments (based on the sign of the screen value), or REPLACE for replacement entries.

Common Use Cases and Queries

The view is commonly used to reconcile adjustments against original entries, to report the signed nature of an adjustment, and to feed downstream integrations that must distinguish additive from replacement changes. A representative query follows:

• SELECT element_entry_id, target_entry_id, entry_type, adjustment_type, entry_value
• FROM apps.pay_paywsmee_adjustment
• WHERE assignment_id = :p_assignment_id
• AND effective_start_date >= :p_start_date;

Typical scenarios include payroll audit reports identifying all SUBTRACT adjustments within a pay period, and validation routines confirming that every replacement entry (REPLACE) has a valid TARGET_ENTRY_ID. Because the view is session-scoped via FND_SESSIONS, queries return only data effective as of the active session date, which aligns results with the user's current payroll processing context.