Search Results previous_tax_district




Overview
Explore in AI Chat

Overview

The view PAY_P46_PENNOT_ASG_INFO_V is a payroll (PAY) module database object owned by the APPS schema in Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It presents a flattened, business-friendly projection of the P46 Pension Notification (P46 PENNOT) assignment-level extra information captured against employee assignments in a United Kingdom payroll context. The view isolates a single extra information type, GB_P46PENNOT, and renames the generic AEI_INFORMATIONn columns of the underlying table into descriptive columns such as PREVIOUS_TAX_CODE, PREVIOUS_TAX_DISTRICT, and PREVIOUS_TAX_BASIS.

Its role is primarily reporting and integration. The physical storage of this data is held as indexed attribute columns within a generic extra information framework, which is not directly consumable by external reporting or statutory inbound/outbound processes. By exposing semantically named columns, the view allows Oracle Payroll statutory reporting, third-party HMRC-related interfaces, and custom extracts to query P46 pension notification data using meaningful identifiers rather than positional attribute slots. This view is of particular interest to implementers searching for previous_tax_code, since the column PREVIOUS_TAX_CODE is exposed directly by the view rather than referenced indirectly through an attribute column.

Underlying Base Objects

The view is defined over a single base object, PER_ASSIGNMENT_EXTRA_INFO (documented as a synonym with a single referenced base object). PER_ASSIGNMENT_EXTRA_INFO is the standard Oracle HRMS extra information table that stores supplementary, flexfield-like attributes attached to an assignment. The view applies a filter on the INFORMATION_TYPE column, restricting rows to those where INFORMATION_TYPE = 'GB_P46PENNOT'.

Because the view does not join to PER_ASSIGNMENTS or PER_ALL_PEOPLE_F directly, consumer queries that require employee names, assignment numbers, payroll identifiers, or legislative data group context must join out to those tables using ASSIGNMENT_ID. The view therefore behaves as a typed, filtered subset of the extra information table rather than a fully denormalised reporting entity.

Key Columns

  • P46_PEN_ASG_EXTRA_INFO_ID — The surrogate primary key of the underlying extra information row (ASSIGNMENT_EXTRA_INFO_ID).
  • ASSIGNMENT_ID — The assignment to which the P46 pension notification data belongs; the join key to PER_ASSIGNMENTS.
  • INFORMATION_TYPE — Always 'GB_P46PENNOT' given the view filter; identifies the record category.
  • AEI_INFORMATION_CATEGORY — The extra information category descriptor for the row.
  • P46_PEN_OBJECT_VERSION_NUM — Optimistic locking version number for the record.
  • P46_PEN_SEND_EDI — Flag indicating whether the P46 pension notification is to be sent electronically.
  • ANNUAL_PENSION — The annual pension amount reported for the assignment.
  • DATE_PENSION_STARTED — Date on which the pension commenced.
  • P46_PENNOT_SEND_EDI_FLAG — The P46 PENNOT-specific electronic submission flag.
  • PREVIOUS_TAX_DISTRICT — Tax district of the previous employment, relevant for HMRC notification.
  • DATE_LEFT_PREV_EMP — Date the employee left the previous employment.
  • PREVIOUS_TAX_CODE — The tax code applied by the previous employer; the column most frequently sought when querying this view.
  • PREVIOUS_TAX_BASIS — The tax basis associated with the previous tax code.
  • PREV_EMP_LAST_PAY_PERIOD_TYPE — Period type of the final payment from the previous employer.
  • PREV_EMP_LAST_PAYMENT_PERIOD — The final payment period from the previous employer.
  • RECENTLY_BEREAVED — Bereavement indicator relevant to pension notification processing.

Common Use Cases and Queries

Typical use cases include identifying assignments with a recorded previous tax code, reconciling P46 pension notification data ahead of HMRC electronic submission, and feeding inbound interfaces with pension and previous-employment details.

  • Listing previous tax codes for all P46 pension notification records.
  • Joining to assignment and person tables to produce a named statutory report.
  • Filtering on the SEND_EDI flags to locate records pending electronic submission.

The following example retrieves previous tax code and district details for a specific assignment:

SELECT p.previous_tax_code, p.previous_tax_district, p.date_left_prev_emp
FROM apps.pay_p46_pENnot_asg_info_v p
WHERE p.assignment_id = :p_assignment_id;

A reporting join enriching the view with assignment context:

SELECT pa.assignment_number, pp.full_name, p.previous_tax_code, p.previous_tax_basis
FROM apps.pay_p46_pennot_asg_info_v p,
     apps.per_all_assignments_f pa,
     apps.per_all_people_f pp
WHERE p.assignment_id = pa.assignment_id
  AND pa.person_id = pp.person_id
  AND TRUNC(SYSDATE) BETWEEN pa.effective_start_date AND pa.effective_end_date;

Because the view is APPS-owned and status VALID, it can be referenced directly by concurrent program SQL, Oracle Reports, and external extracts without additional grants when executed with standard APPS responsibilities.