Search Results wnu_object_version_num

Overview

PAY_WNU_ASG_INFO_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product family. It is registered in ETRM with a status of VALID and is delivered in both Release 12.1.1 and 12.2.2. The view presents a filtered, business-friendly projection of assignment-level extra information used by the Great Britain Work Number Update (WNU) payroll processing functionality.

The name derives from its narrow scope: it exposes only those rows in PER_ASSIGNMENT_EXTRA_INFO whose INFORMATION_TYPE is 'GB_WNU'. Rather than requiring callers to know the underlying extra-information model, the view renames the columns into descriptive WNU terms, providing a stable read interface for reporting, reconciliation, and integration components that need to inspect an assignment's Work Number Update state. The column name WNU_OBJECT_VERSION_NUM, which maps to the base column OBJECT_VERSION_NUMBER, is significant: it confirms that the view carries the optimistic-locking version token from the underlying row, allowing consumers to detect concurrent changes.

Underlying Base Objects

The view is defined over a single base object: PER_ASSIGNMENT_EXTRA_INFO, accessed through the APPS synonym. PER_ASSIGNMENT_EXTRA_INFO is the standard Oracle HRMS/Payroll table that stores flexible, developer-defined descriptive information attached to an assignment. Each row carries an ASSIGNMENT_ID, an INFORMATION_TYPE, an information category, a numeric OBJECT_VERSION_NUMBER, and a set of generic AEI_INFORMATION columns whose meaning depends on the information type.

The view text performs a single-table selection with a WHERE clause restricting INFORMATION_TYPE to 'GB_WNU'. No joins, unions, or aggregations are applied, so the view is essentially a typed, renamed filter over the base table. This keeps the view inexpensive to query and means row counts and locking behaviour track the base table directly.

Key Columns

• WNU_ASG_EXTRA_INFO_ID — Primary identifier of the underlying extra-information row (ASSIGNMENT_EXTRA_INFO_ID).
• ASSIGNMENT_ID — The assignment to which the WNU information belongs; the principal join key to PER_ASSIGNMENTS_F and related HR objects.
• INFORMATION_TYPE — Always 'GB_WNU' in this view; retained so downstream consumers can filter uniformly.
• AEI_INFORMATION_CATEGORY — The information category that groups the WNU extra-information setup.
• WNU_OBJECT_VERSION_NUM — Optimistic-locking version number inherited from the base row; incremented on each update.
• PREVIOUS_ASSIGNMENT_NUMBER — Populated from AEI_INFORMATION1; records the assignment number prior to a Work Number Update.
• NOT_INCLUDED_IN_WNU — Populated from AEI_INFORMATION2; flags assignments excluded from Work Number Update processing.

Common Use Cases and Queries

Typical usage includes identifying assignments excluded from WNU, auditing assignment-number changes recorded by WNU, and reconciling extra-information rows for a population of employees.

SELECT wnu.assignment_id,
       wnu.previous_assignment_number,
       wnu.not_included_in_wnu,
       wnu.wnu_object_version_num
FROM   apps.pay_wnu_asg_info_v wnu
WHERE  wnu.assignment_id = :p_assignment_id;

To list all assignments currently excluded from Work Number Update:

SELECT assignment_id, previous_assignment_number
FROM   apps.pay_wnu_asg_info_v
WHERE  not_included_in_wnu = 'Y';

Because the view is a thin filter, queries should be restricted by ASSIGNMENT_ID or INFORMATION_TYPE-driven predicates where possible. Developers extending WNU logic should treat the view as read-only and perform maintenance against PER_ASSIGNMENT_EXTRA_INFO, respecting the OBJECT_VERSION_NUMBER surfaced here as WNU_OBJECT_VERSION_NUM.