Results for “pay_au_term_long_v”

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

Overview

PAY_AU_TERM_LONG_V is an Oracle EBS payroll view owned by the APPS schema and classified under the PAY - Payroll product. It is an Australian localisation view whose purpose is to surface termination-related long service leave data for reporting and integration. The view is defined over the element type "LONG SERVICE LEAVE ON TERMINATION" and consolidates the screen entry values and units of measure associated with up to seven input values defined for that element type, together with derived eligibility and processing indicators produced by the PAY_AU_TERMINATIONS package. In Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID, indicating the compiled definition is consistent with the underlying dictionary at the time of generation.

The view is not a transactional table in its own right; it is a denormalised presentation layer intended to simplify access to element entry data that would otherwise require multiple joins across the element entry, entry value, input value and element type tables. Because it depends on FND_SESSIONS for the effective date used in its derived computations, the view is effectively session-aware and returns results relative to the current application session.

Underlying Base Objects

The documented base objects referenced by the view are: FND_SESSIONS (SYNONYM), PAY_AU_TERMINATIONS (PACKAGE), PAY_ELEMENT_ENTRIES_F (SYNONYM), PAY_ELEMENT_ENTRY_VALUES_F (SYNONYM), PAY_ELEMENT_TYPES_F (SYNONYM) and PAY_INPUT_VALUES_F (SYNONYM). All synonyms resolve to APPS-owned or shared payroll objects.

• PAY_ELEMENT_TYPES_F supplies the element type definition and is filtered on ELEMENT_NAME = 'LONG SERVICE LEAVE ON TERMINATION'.
• PAY_ELEMENT_ENTRIES_F is the driving table, aliased PEE, providing the element entry rows, assignment, entry type and effective dating.
• PAY_ELEMENT_ENTRY_VALUES_F is referenced as seven aliases (EEV0 through EEV5 in the visible fragment) to pivot individual screen entry values.
• PAY_INPUT_VALUES_F is similarly aliased (PIV0 through PIV6) to constrain each pivot to a named input value and to expose the unit of measure.
• FND_SESSIONS supplies EFFECTIVE_DATE, which is passed into the PAY_AU_TERMINATIONS functions.
• PAY_AU_TERMINATIONS is a PL/SQL package exposing the PROCESSED and OVERRIDE_ELIG functions invoked directly within the SELECT list.

Key Columns

The view exposes a ROWID plus OBJECT_VERSION_NUMBER for the underlying element entry, and the identifiers ELEMENT_ENTRY_ID and ELEMENT_LINK_ID. CREATOR_TYPE and ENTRY_TYPE describe the origin and nature of the entry. ELEMENT_TYPE_ID links back to PAY_ELEMENT_TYPES_F, while ASSIGNMENT_ID, EFFECTIVE_START_DATE and EFFECTIVE_END_DATE tie the row to an assignment and an effective period.

For each of the pivoted input values the view returns a triplet: INPUT_VALUE_ID, SCREEN_ENTRY_VALUE and UOM. The documented input value names include "PRE 16_08_1978 PAY" and "POST 15_08_1978 PAY", reflecting the statutory date thresholds applicable to Australian long service leave. The final computed columns return the first character of the PAY_AU_TERMINATIONS.PROCESSED result and, per BUG# 5056831, the OVERRIDE_ELIG flag along with the associated INPUT_VALUE_ID and UOM.

Common Use Cases and Queries

Typical uses include auditing terminations processed under the Australian long service leave element, verifying the split between pre- and post-16 August 1978 pay components, and extracting data for statutory reporting or downstream interfaces.

• Listing termination entries for an assignment or effective period.
• Confirming whether an entry has been processed and whether eligibility was overridden.
• Reconciling screen entry values against the corresponding element entry.

A representative query is: SELECT element_entry_id, assignment_id, effective_start_date, effective_end_date, entry_type, processed_flag FROM apps.pay_au_term_long_v WHERE assignment_id = :p_assignment_id AND TRUNC(effective_start_date) <= TRUNC(SYSDATE);

Because results depend on FND_SESSIONS, callers should ensure a valid session context exists and should not rely on the view outside an initialised EBS application session.