Search Results override_eligibility
Overview
APPS.PAY_AU_TERM_LONG_V is an Oracle EBS payroll view that consolidates element entry data for the Australian legislative element "Long Service Leave on Termination." It is one of a family of Australian termination views (the "TERM_LONG" view specifically targets long service leave) that flatten the multi-row structure of PAY_ELEMENT_ENTRY_VALUES_F into a wide, single-row-per-entry projection for reporting and integration. The view presents the core identifiers of the parent element entry alongside six screen-entry input values ("Pre 16_08_1978 Pay," "Post 15_08_1978 Pay," and subsequent values) joined through PAY_INPUT_VALUES_F.
Two computed columns are especially significant because they invoke PL/SQL functions from the PAY_AU_TERMINATIONS package: pay_au_terminations.processed(...) returns a single-character status flag indicating whether the entry has been processed, and pay_au_terminations.override_elig(...) returns a single-character flag indicating whether the eligibility override has been applied. Both are truncated to length 1 via substr(...,1,1). Application logic and audits that reference "override_eligibility" ultimately trace to this override_elig function call.
Underlying Base Objects
The view is defined over the following documented base objects:
- PAY_ELEMENT_TYPES_F – supplies the element type; the view is restricted to the element named 'Long Service Leave on Termination'.
- PAY_ELEMENT_ENTRIES_F (aliased
pee) – the driving table, providing row identifiers, entry/assignment context, and effective dates. - PAY_ELEMENT_ENTRY_VALUES_F (aliased
eev0–eev5) – repeats once per input value to retrieve each screen entry value. - PAY_INPUT_VALUES_F (aliased
piv0–piv6) – joins each entry value to its input value definition, including thepiv6instance added under Bug# 5056831 for the override eligibility value and its UOM. - PAY_AU_TERMINATIONS (package) – referenced indirectly through the
processedandoverride_eligfunction calls. - FND_SESSIONS (aliased
ses) – supplies the current session's effective date, passed into both package functions to evaluate date-effective logic.
The ORDERED hint and the fixed join order reflect the view's performance-sensitive design, ensuring the element type filter is applied early.
Key Columns
element_entry_id,element_link_id,assignment_id– identify the element entry and its assignment.effective_start_date,effective_end_date– date-effective window of the entry.screen_entry_valueanduom(per input value, e.g.eev0–eev5) – the monetary or numerical value entered and its unit of measure.input_value_id(per input value, includingpiv6.input_value_id) – links each value to its definition;piv6specifically supports the override eligibility check.- The
processedcomputed column – single-character processing status. - The
override_eligcomputed column – single-character eligibility override flag, the column most relevant to searches on "override_eligibility."
Common Use Cases and Queries
The view is typically used to audit termination payouts, verify eligibility overrides, and feed downstream extracts. A representative query returns the override eligibility flag for a given assignment:
- Filter by
assignment_idand effective date range to list each long service leave entry and its override eligibility status. - Join to
PER_ASSIGNMENTS_ForPER_ALL_PEOPLE_Fto translateassignment_idinto an employee. - Extract
screen_entry_valuecolumns to reconcile payout amounts during termination processing. - Screen on the
override_eligcomputed column to identify entries where eligibility was manually overridden.
Example: SELECT element_entry_id, assignment_id, effective_start_date, substr(pay_au_terminations.override_elig(element_entry_id, piv6.input_value_id, sysdate),1,1) override_flag FROM apps.pay_au_term_long_v; — though in practice the computed column is selected directly from the view rather than reconstructed. Because the view invokes PL/SQL, queries can be slower; restricting by assignment_id or effective dates improves performance.
-
VIEW: APPS.PAY_AU_TERM_LONG_V
12.1.1
-
VIEW: APPS.PAY_AU_TERM_LONG_V
12.2.2
-
View: PAY_AU_TERM_LONG_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_AU_TERM_LONG_V, object_name:PAY_AU_TERM_LONG_V, status:VALID, product: PAY - Payroll , description: Australian localisation view. , implementation_dba_data: APPS.PAY_AU_TERM_LONG_V ,
-
PACKAGE: APPS.PQH_GSP_POST_PROCESS
12.1.1
-
View: PAY_AU_TERM_LONG_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_AU_TERM_LONG_V, object_name:PAY_AU_TERM_LONG_V, status:VALID, product: PAY - Payroll , description: Australian localisation view. , implementation_dba_data: APPS.PAY_AU_TERM_LONG_V ,
-
PACKAGE: APPS.PQH_GSP_POST_PROCESS
12.2.2
-
APPS.PAY_AU_TERMINATIONS SQL Statements
12.1.1
-
PACKAGE: APPS.PAY_AU_TERMINATIONS
12.1.1
-
PACKAGE: APPS.PAY_AU_TERMINATIONS
12.2.2
-
APPS.PAY_AU_TERMINATIONS SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PAY_AU_TERMINATIONS
12.1.1
-
PACKAGE BODY: APPS.PQH_GSP_POST_PROCESS
12.1.1
-
PACKAGE BODY: APPS.PQH_GSP_POST_PROCESS
12.2.2
-
PACKAGE BODY: APPS.PAY_AU_TERMINATIONS
12.2.2