Search Results tax_reg_number




Overview
Explore in AI Chat

Overview

The view APPS.PAY_NL_TAXOFF_ACTION_INFO_V is a payroll reporting object defined in the Oracle E-Business Suite (EBS) Payroll (PAY) module. Its documented purpose is to support the Dutch Payslip Report, where it resolves the tax office name and tax registration number associated with an employee's payroll action. The view carries a status of VALID in the APPS schema and is present in both EBS 12.1.1 and 12.2.2 environments.

Functionally, the view acts as a reconciliation and enrichment layer across payroll action information. It joins records held against a payroll action (PAY_ASSIGNMENT_ACTIONS) to two separate action-information categories — the EMEA payroll information set and the Dutch "NL OTHER EMPLOYEE DETAILS" set — and links them along a shared key. For users searching on tax_reg_number, this view is the primary surface where the Dutch tax registration number is exposed for statutory payslip output and any downstream reporting or integration that consumes Dutch tax identifiers.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

  • PAY_ACTION_INFORMATION — aliased twice in the view text. The alias PAI_EPI represents the "EMEA PAYROLL INFO" action-information category, while PAI_NL_OED represents the "NL OTHER EMPLOYEE DETAILS" category. The self-join allows attributes held in the EMEA set to be matched against attributes held in the Dutch-specific set.
  • PAY_ASSIGNMENT_ACTIONS — aliased PAA, providing the assignment-level action context and the payroll action identifier used to correlate records.

The join logic is driven by two context relationships. The payroll action identifier on PAA (PAYROLL_ACTION_ID) equals ACTION_CONTEXT_ID on the EMEA alias, whose records are constrained to ACTION_CONTEXT_TYPE 'PA' and ACTION_INFORMATION_CATEGORY 'EMEA PAYROLL INFO'. Separately, the assignment action identifier on PAA (ASSIGNMENT_ACTION_ID) equals ACTION_CONTEXT_ID on the Dutch alias, whose records are constrained to ACTION_CONTEXT_TYPE 'AAP' and ACTION_INFORMATION_CATEGORY 'NL OTHER EMPLOYEE DETAILS'. The two information sets are then matched where ACTION_INFORMATION5 (Dutch) equals ACTION_INFORMATION2 (EMEA), establishing the linkage between the tax office and the corresponding registration data.

Key Columns

  • ACTION_CONTEXT_ID — The action context identifier sourced from the Dutch other employee details record (PAI_NL_OED). It ties the row back to the originating assignment action and provides the correlation key for the payslip line.
  • TAX_OFFICE_NAME — Sourced from PAI_EPI.ACTION_INFORMATION4, exposing the descriptive name of the Dutch tax office relevant to the payroll action.
  • TAX_REG_NUMBER — Sourced from PAI_EPI.ACTION_INFORMATION6, exposing the tax registration number. This is the column surfaced when users query on tax_reg_number, and it supplies the statutory identifier required on the Dutch payslip.

Because the view exposes only three columns, its contract is narrow and stable: a context identifier paired with a tax office name and its corresponding registration number.

Common Use Cases and Queries

The primary use case is the Dutch Payslip Report, which must print the correct tax office and registration number per payroll action. Secondary use cases include reconciliation of tax registration data across the EMEA and Dutch information categories, and integration extracts where downstream systems require the Dutch tax registration identifier.

A representative query retrieving tax registration details for a given action context is:

  • SELECT action_context_id, tax_office_name, tax_reg_number FROM apps.pay_nl_taxoff_action_info_v WHERE action_context_id = :p_action_context_id;
  • SELECT action_context_id, tax_office_name, tax_reg_number FROM apps.pay_nl_taxoff_action_info_v;

Because the view performs its own constrained joins, no additional WHERE predicates are strictly required to obtain valid rows; filtering by ACTION_CONTEXT_ID is recommended when resolving a single payslip action. Note that the source record must exist in both information categories and the ACTION_INFORMATION5 = ACTION_INFORMATION2 linkage must be satisfied, or the row will not appear.