Search Results absence_value

Overview

APPS.PAY_APAC_PAYSLIP_ABSENCES_V is a reporting view in the Oracle E-Business Suite Payroll (PAY) module, owned by the APPS schema and classified in FND Design Data as PAY.PAY_APAC_PAYSLIP_ABSENCES_V. It exposes absence-related information that is formatted for inclusion on payslips generated for the Asia-Pacific (APAC) legislations. The view consolidates absence type, reporting element name, absence dates and quantities, unit of measure, and a monetary value so that downstream payslip programs and reports can present both the absence duration and the associated pay amount in a single, denormalized result set.

The view carries the standard Oracle restriction that it is intended for internal use by Oracle Applications programs; direct customer access is not supported. Its principal known consumer is APPS.PAY_IN_SOE (Statement of Earnings), which references the view to build the absence section of the payslip. The presence of the PAY_VALUE column places this view squarely in the category of objects that translate an absence entry into its payroll-valued form, which is why a search for "pay_value" surfaces it.

Underlying Base Objects

The view is defined over, and depends on, the following documented objects:

• PAY_ACTION_INFORMATION (referenced through an APPS synonym) — supplies the action context that anchors each row to a payroll action.
• FND_DATE (package) — used for date conversion and formatting of the absence start and end dates.
• FND_NUMBER (package) — used for numeric conversion and formatting of the absence and pay values.
• HR_GENERAL_UTILITIES (package) — used for generic HR/Payroll utility logic, including unit-of-measure and value handling.

The dependency chain is one-directional: the view reads from these objects, and PAY_IN_SOE reads from the view. Because FND_DATE, FND_NUMBER, and HR_GENERAL_UTILITIES are packages rather than tables, the row source ultimately originates from PAY_ACTION_INFORMATION and related payroll action data, with the packages applied as transformation functions.

Key Columns

• ACTION_CONTEXT_ID (NUMBER) — identifier linking the absence row to its parent payroll action context.
• ACTION_CONTEXT_TYPE (VARCHAR2) — discriminator describing the type of action context.
• ABSENCE_TYPE (VARCHAR2, 240) — the descriptive name of the absence (for example, leave category), exposed as a developer descriptive flexfield column.
• ELEMENT_REPORTING_NAME (VARCHAR2, 240) — the reporting name of the payroll element to which the absence maps; also exposed as a developer descriptive flexfield column.
• START_DATE / END_DATE (DATE) — the effective span of the absence.
• ABSENCE_VALUE (NUMBER) — the quantity of absence recorded.
• UOM (VARCHAR2, 4000) — the unit of measure in which ABSENCE_VALUE is expressed (days, hours, and so on).
• PAY_VALUE (NUMBER) — the monetary value attributed to the absence for payslip presentation, the column most relevant to "pay_value" searches.

Common Use Cases and Queries

Typical usage is diagnostic or reporting-oriented: reconciling payslip absence lines against payroll run results, verifying that an absence maps to the correct element reporting name, or confirming the monetary amount carried into the Statement of Earnings. A representative query is shown below.

• Retrieve all absence rows with their pay values:
  SELECT ACTION_CONTEXT_ID, ABSENCE_TYPE, ELEMENT_REPORTING_NAME, START_DATE, END_DATE, ABSENCE_VALUE, UOM, PAY_VALUE FROM APPS.PAY_APAC_PAYSLIP_ABSENCES_V;
• Filter by a specific action context to isolate a single payroll action.
• Aggregate PAY_VALUE by ABSENCE_TYPE or ELEMENT_REPORTING_NAME for cost and trend analysis.
• Join to payroll action or assignment data on ACTION_CONTEXT_ID to attribute absences to employees.

Because the view is Oracle-internal and unsupported for direct access, any custom query should be treated as read-only and validated against the supported PAY_IN_SOE output before being relied upon.