Results for “process_type_meaning”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_NI_ELEMENT_ENTRIES_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product module. It is documented as a view based on PAY_ELEMENT_ENTRY_VALUES_F and is used by the PAYGBTAX form to display National Insurance (NI) details for United Kingdom payroll processing. The view is registered with a VALID status in the ETRM metadata for the 12.2.2 release and is consistent with the 12.1.1 environment.
The view serves a presentation role: it pivots the row-based entry value records held in the element entry values table into a wide, denormalised result set, one row per element entry, where each NI input value occupies its own column group. This structure is well suited to the PAYGBTAX form, Oracle Reports outputs, and integration extracts that require NI category, certificate, renewal, pension and process information in a single flat row. Because the CATEGORY column stores a lookup code, the view also exposes CATEGORY_MEANING so that consumers receive the translated description rather than the raw code. This is the attribute most commonly searched for against this object.
Underlying Base Objects
The documented base objects referenced by PAY_NI_ELEMENT_ENTRIES_V are:
- PAY_ELEMENT_ENTRIES_F — the element entry header (assignment-level entry).
- PAY_ELEMENT_ENTRY_VALUES_F — the entry value lines holding each input value and its screen entry value.
- PAY_ELEMENT_LINKS_F and PAY_ELEMENT_TYPES_F — element link and element type definitions.
- PAY_INPUT_VALUES_F — the input value definitions; the view text joins on PIV.NAME to identify which NI attribute each row represents.
- HR_GENERAL — a PL/SQL package supplying DECODE_LOOKUP, used to translate codes into meanings.
- FND_SESSIONS — the standard Applications session synonym referenced through the underlying entry tables.
The view text selects from the entry values table and, for each of the NI attributes (CATEGORY, CERTIFICATE, DATE OF RENEWAL, PENSION, PROCESS TYPE, PERIODS, PRIORITY PERIOD TYPE and others), applies a MIN(DECODE(PIV.NAME, ..., ...)) aggregation keyed on ELEMENT_ENTRY_ID. Because of this GROUP BY-style construction, the view returns one consolidated row per element entry.
Key Columns
- ROW_ID — the ROWID of the underlying entry values row, retained for updatable/forms purposes.
- ELEMENT_ENTRY_ID — the element entry identifier linking back to PAY_ELEMENT_ENTRIES_F.
- CATEGORY — the NI category code (e.g. A, B, C, D) held as the screen entry value. This is the column surfaced by the CATEGORY lookup.
- CATEGORY_MEANING — the decoded description of the NI category, produced via HR_GENERAL.DECODE_LOOKUP('GB_CATEGORY', SCREEN_ENTRY_VALUE). The search term "category_meaning" maps directly to this column.
- CERTIFICATE / CERTIFICATE_MEANING — the NI certificate indicator and its decoded meaning from the GB_CERTIFICATE lookup.
- DATE_OF_RENEWAL — the certificate renewal date input value.
- PENSION / PENSION_MEANING — pension indicator and its decoded value from GB_PENSION.
- PROCESS_TYPE / PROCESS_TYPE_MEANING — processing indicator and its decoded value from GB_PROCESS.
- PERIODS / PERIOD_TYPE — period and priority period type input values.
- INPUT_VALUE_ID1 … INPUT_VALUE_ID7 — the surrogate input value identifiers corresponding to each attribute, useful for joins or updates.
Common Use Cases and Queries
The view is typically queried to reconcile NI categories assigned to employees or to extract NI-relevant element entries for audit and validation. A representative query returning NI category details for a set of element entries is:
SELECT element_entry_id, category, category_meaning, certificate_meaning, pension_meaning, process_type_meaning FROM apps.pay_ni_element_entries_v WHERE category IS NOT NULL;
A second common pattern filters on a specific NI category code to identify affected entries:
SELECT element_entry_id, category_meaning FROM apps.pay_ni_element_entries_v WHERE category = 'A';
Because meanings are resolved through HR_GENERAL.DECODE_LOOKUP at query time, the translated values reflect the current lookup configuration. Integrations and reports should therefore rely on CATEGORY_MEANING rather than hard-coding code-to-meaning mappings, and should treat INPUT_VALUE_ID1 as the stable identifier for joins back to PAY_ELEMENT_ENTRY_VALUES_F.
-
View based on PAY_ELEMENT_ENTRY_VALUES_F used by the PAYGBTAX form to display NI details.
APPS.PAY_NI_ELEMENT_ENTRIES_V·↳ FND_SESSIONS·↳ HR_GENERAL·↳ PAY_ELEMENT_ENTRIES_F·Explore PAY module →
-
View based on PAY_ELEMENT_ENTRY_VALUES_F used by the PAYGBTAX form to display NI details.
APPS.PAY_NI_ELEMENT_ENTRIES_V·↳ FND_SESSIONS·↳ HR_GENERAL·↳ PAY_ELEMENT_ENTRIES_F·Explore PAY module →
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.