Results for “element_value”

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

Overview

The PAY_NL_SUMMARY_ACTION_INFO_V view is a reporting object owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) module. It is classified as a VALID view in ETRM for releases 12.1.1 and 12.2.2, and its documented purpose is to support the Dutch Payslip Report, one of the localized payroll reporting outputs for the Netherlands legislation. Rather than storing data of its own, the view provides a narrowed, semantically meaningful projection over the payroll action information infrastructure, exposing Dutch calculation results in a form that the payslip report and related statutory extracts can consume directly.

The view does not expose raw, generic payload columns. Instead it renames them into business-friendly aliases so that downstream report logic can address payroll element data without needing to understand the internal ACTION_INFORMATION numbering scheme. This makes it an integration and reporting convenience layer rather than a transactional entity.

Underlying Base Objects

The view is defined over a single documented base object: PAY_ACTION_INFORMATION, accessed through a synonym in the APPS schema. The view text selects from PAY_ACTION_INFORMATION with the alias PAI_NL_SUM, annotated with the comment "AIC ---- NL CALCULATIONS".

Two filtering predicates constrain the rows returned:

• ACTION_CONTEXT_TYPE = 'AAP' — restricts the view to the payroll action context type associated with assignment-level action processing.
• ACTION_INFORMATION_CATEGORY = 'NL CALCULATIONS' — restricts rows to the Dutch payroll calculation category, isolating Netherlands-specific results from other legislative or generic action information.

Because the view is read-only and built entirely on PAY_ACTION_INFORMATION, it inherits that table's partitioning, indexing, and security characteristics. No joins, aggregations, or DML constructs are present in the documented view text.

Key Columns

The view exposes exactly three columns, each mapped directly from a column in PAY_ACTION_INFORMATION:

• ACTION_CONTEXT_ID — sourced from PAI_NL_SUM.ACTION_CONTEXT_ID. This is the identifier that ties each calculation row back to its originating payroll action context, effectively the join key to the assignment, payroll run, or action that produced the values.
• ELEMENT_TYPE — sourced from PAI_NL_SUM.ACTION_INFORMATION8. This carries the classification of the payroll element to which the calculation result belongs (for example, a Dutch earnings, deduction, or statutory element type).
• ELEMENT_VALUE — sourced from PAI_NL_SUM.ACTION_INFORMATION12. This holds the calculated value associated with the element type, which is the column most commonly referenced when users search for "element_value" against this view. It is the numeric or textual result that the Dutch Payslip Report renders.

The mapping of generic ACTION_INFORMATION8 and ACTION_INFORMATION12 columns to the semantic ELEMENT_TYPE and ELEMENT_VALUE names is the principal value the view adds.

Common Use Cases and Queries

The primary use case is the Dutch Payslip Report, which queries the view to retrieve element values for display on payslips. Secondary uses include ad hoc reconciliation of Dutch payroll calculations, validation of statutory element output, and troubleshooting of assignment-level calculation results.

To retrieve all element values for a specific action context:

• SELECT action_context_id, element_type, element_value FROM apps.pay_nl_summary_action_info_v WHERE action_context_id = :p_context_id;

To isolate a particular element type across contexts, for example a Dutch statutory deduction:

• SELECT action_context_id, element_value FROM apps.pay_nl_summary_action_info_v WHERE element_type = :p_element_type;

Because ACTION_CONTEXT_ID links to the underlying action context, queries are frequently joined back to payroll action or assignment tables to attribute values to specific employees or payroll periods. All access is read-only, and results are bounded to ACTION_CONTEXT_TYPE 'AAP' and category 'NL CALCULATIONS', so callers need not repeat those predicates.