Results for “bon_ei_prem_proc”

8 results




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

Overview

APPS.PAY_JP_UI_BON_ENTRIES_V is a Japanese localization (JP) view within the Oracle E-Business Suite Payroll (PAY) module. It serves as a user-interface abstraction layer that presents element entry data associated with the "BON_EI_PREM_PROC" element — a bonus premium processing element used in Japanese payroll calculations. The view is designed to flatten and aggregate the multi-row structure of element entry values into a single row per element entry, exposing two display-sequence based input values as discrete columns. This makes it particularly suitable for Oracle Forms-based UI blocks, concurrent program reporting, and integration interfaces that require a simplified, denormalized representation of bonus premium element entries.

Because the view ties its result set to the current FND_SESSIONS context via userenv('sessionid'), it is inherently session-scoped. Only element entries effective as of the session's effective date are returned, ensuring date-tracked (datetracked) consistency with the user's current session date.

Underlying Base Objects

Per ETRM 12.2.2 metadata, the view is defined over the following APPS synonyms:

  • FND_SESSIONS — Provides the session context; joined on session_id = userenv('sessionid') and used to derive the effective date that constrains all datetracked joins.
  • PAY_ELEMENT_TYPES_F — Filtered to element_name = 'BON_EI_PREM_PROC', isolating the Japanese bonus premium processing element type.
  • PAY_ELEMENT_ENTRIES_F — The core element entry records; filtered to entry_type = 'E' (entry-level, not assignment-level).
  • PAY_ELEMENT_LINKS_F — Links element entries to the element type and assignment context.
  • PAY_ELEMENT_ENTRY_VALUES_F — Holds the actual input values entered for each element entry.
  • PAY_INPUT_VALUES_F — Defines the input value metadata, including display_sequence used by the DECODE logic.

All joins are date-tracked: the effective date from FND_SESSIONS must fall between each object's effective_start_date and effective_end_date. The element entry values join uses nvl(pee.element_entry_id, pel.element_link_id), allowing the view to handle both entry-level and link-level value storage contexts.

Key Columns

  • element_entry_id — Primary identifier of the element entry.
  • effective_start_date / effective_end_date — Datetrack validity window for the entry.
  • assignment_id — The assignment to which the entry belongs.
  • element_link_id — Linkage identifier connecting entry to element type.
  • object_version_number — Optimistic locking version for the entry row.
  • input_value_id (display_sequence 1 and 2) — The entry value IDs for the first two input values, resolved via DECODE on display_sequence.
  • first-character display value (seq 1) — SUBSTRB(...screen_entry_value,1,1) of the first input value, typically a code or indicator.
  • numeric display value (seq 2) — TO_NUMBER(screen_entry_value) of the second input value, typically an amount or rate.
  • creation_date, created_by, last_update_date, last_updated_by, last_update_login — Standard audit columns.

Note the aggregation via MIN(DISTINCT ...) in the GROUP BY, which collapses duplicate value rows into one row per element entry.

Common Use Cases and Queries

This view is commonly queried by Japanese payroll localization forms and reports that need a compact view of bonus premium processing entries for the active session.

  • Listing bonus premium entries for the current user session.
  • Reporting on the two primary input values (code and amount) per entry.
  • Integration extracts feeding downstream Japanese statutory calculations.

Sample query:

SELECT element_entry_id, assignment_id,
       effective_start_date, effective_end_date,
       element_link_id, object_version_number
FROM   apps.pay_jp_ui_bon_entries_v
WHERE  assignment_id = :p_assignment_id
ORDER  BY effective_start_date DESC;

Because the view depends on userenv('sessionid'), it must be invoked within an active EBS session; direct SQL*Plus access outside a forms session may return no rows unless FND_SESSIONS is populated accordingly.