Results for “pay_jp_hi_comp_entries_v”

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

Overview

The PAY_JP_HI_COMP_ENTRIES_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PAY (Payroll) product family. Its status is VALID, and it is documented specifically as a localization component reserved for Japanese payroll processing. The view does not represent a general-purpose payroll entity; it exists to support the Japanese localization of Oracle Payroll, where statutory and customer-specific compensation data must be consolidated from individual element entry records into a denormalized, display-oriented structure.

Functionally, the view pivots element entry input values into fixed positional columns. When a Japanese payroll element is entered against an assignment, the individual input values that make up that entry (as defined in PAY_INPUT_VALUES_F and stored in PAY_ELEMENT_ENTRY_VALUES_F) are collapsed via DECODE on DISPLAY_SEQUENCE and aggregated with MIN(DISTINCT ...). This produces one row per element entry, with up to six discrete value columns, each cast or truncated according to the expected data type of that position.

Underlying Base Objects

The ETRM metadata identifies the following referenced base objects:

• PAY_ELEMENT_ENTRIES_F (SYNONYM) — the driving table; supplies ELEMENT_ENTRY_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, ASSIGNMENT_ID, and standard WHO audit columns.
• PAY_ELEMENT_ENTRY_VALUES_F (SYNONYM) — holds the individual input values for each entry, including SCREEN_ENTRY_VALUE.
• PAY_ELEMENT_LINKS_F (SYNONYM) — supplies ELEMENT_LINK_ID, tying the entry to an element eligibility link.
• PAY_ELEMENT_TYPES_F (SYNONYM) — the element definition joined into the driving set.
• PAY_INPUT_VALUES_F (SYNONYM) — defines the input values and their DISPLAY_SEQUENCE, which drives the pivot logic.
• FND_SESSIONS (SYNONYM) — referenced in the FROM clause with an ordered index hint, used for session-scoped context.
• HR_GENERAL (PACKAGE) — invoked as HR_GENERAL.DECODE_LOOKUP to resolve lookup meanings for positional value 4.

The view relies on an ORDERED hint and a fixed set of index hints (FND_SESSIONS_U1, PAY_ELEMENT_TYPES_F_UK2, PAY_ELEMENT_ENTRIES_F_N50, PAY_ELEMENT_LINKS_F_PK, PAY_ELEMENT_ENTRY_VALUES_F_N50, PAY_INPUT_VALUES_F_PK), reflecting a performance-tuned access path for its intended transactional volume.

Key Columns

• ELEMENT_ENTRY_ID — primary identifier of the element entry row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range of the entry.
• ASSIGNMENT_ID — the assignment to which the entry belongs.
• ELEMENT_LINK_ID — the element link governing eligibility.
• OBJECT_VERSION_NUMBER — optimistic locking version for the entry.
• Positional INPUT_VALUE_ID columns (up to six) — the input value identifiers resolved by DISPLAY_SEQUENCE 1 through 6.
• Positional SCREEN_ENTRY_VALUE columns — the entry values; positions 1 and 4 are character-based (SUBSTRB to 6 and 30 bytes respectively), while positions 2, 3, 5, and 6 are converted with TO_NUMBER, indicating numeric input values.
• Decoded lookup column — a lookup meaning for position 4, resolved through HR_GENERAL.DECODE_LOOKUP and truncated to 80 bytes.
• Creation and audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, each aggregated with MIN(DISTINCT ...).

Common Use Cases and Queries

The view is most commonly used in Japanese localization reporting, interface extracts, and payroll data validation, where consumers require element entries in a flat, positionally aligned format rather than the normalized entry/value pair structure.

SELECT element_entry_id,
       assignment_id,
       effective_start_date,
       effective_end_date,
       element_link_id
FROM   apps.pay_jp_hi_comp_entries_v
WHERE  assignment_id = :p_assignment_id
AND    TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Because the view is defined for the Japanese localization only, queries should be restricted to assignments and payrolls within that legislative context. When diagnosing discrepancies, joining the returned ELEMENT_ENTRY_ID back to PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F restores the un-pivoted detail, allowing each positional column to be reconciled against its source input value.