Results for “com_itx_info”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.PAY_JP_ITAX_ENTRIES_V is a payroll reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. Its name indicates it exposes Japanese income tax (ITAX) entries held within Oracle Payroll, and its scope is a denormalised projection of element entry input values that belong to Japanese income tax elements. The view occupies the standard APPS schema and is referenced as a synonym from the Oracle Human Resources and Payroll reporting layers.
The view is not a stored table; it is a SQL definition that binds session context (through FND_SESSIONS, enforced with an ORDERED and INDEX hint) to the payroll element framework and reshapes the underlying element entry values into a wide, positional column layout. Six input values are addressed by display_sequence, and each is emitted in several forms: the raw input_value_id, a varchar2 representation truncated with substrb, a numeric representation via to_number, and a decoded lookup form. This positional projection is what makes the view suitable for fixed-format reporting and integration feeds, since a consuming program can read named columns instead of performing pivots at runtime.
Underlying Base Objects
The documented base objects of the view are:
- FND_SESSIONS (SYNONYM) — session context used to constrain the query to the current run context.
- PAY_ELEMENT_TYPES_F (SYNONYM) — the element definitions, including Japanese income tax elements.
- PAY_ELEMENT_LINKS_F (SYNONYM) — assignable links that bind element types to payrolls and other criteria.
- PAY_ELEMENT_ENTRIES_F (SYNONYM) — the assignment-level element entries, the driving transaction.
- PAY_ELEMENT_ENTRY_VALUES_F (SYNONYM) — the actual input values held per entry.
- PAY_INPUT_VALUES_F (SYNONYM) — the input value definitions, supplying display_sequence and lookup_type.
- HR_GENERAL (PACKAGE) — decode_lookup, used to translate coded values.
- HR_JP_GENERAL_PKG (PACKAGE) — decode_org, used for the Japanese organisation decode.
The join path runs from fnd_sessions through pay_element_types_f and pay_element_links_f to pay_element_entries_f, then to pay_element_entry_values_f and pay_input_values_f. The ORDERED and 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) reflect a tuning strategy that drives the query from the session and uses the most selective indexes on each table.
Key Columns
- element_entry_id — primary identifier of the element entry; the row grain of the view.
- assignment_id — the assignment to which the entry applies.
- element_link_id — the link controlling eligibility of the element.
- effective_start_date, effective_end_date — date-tracked validity window of the entry.
- object_version_number — optimistic locking token inherited from the entry.
- Positional input value IDs — min(distinct decode(display_sequence,n,input_value_id)) for n = 1 to 6.
- Positional screen_entry_value columns — the raw screen values, some truncated to 30 characters and others narrowed to a single character.
- Decoded columns — hr_general.decode_lookup outputs (up to 80 characters) and hr_jp_general_pkg.decode_org output (up to 240 characters).
- Audit columns — creation_date, created_by, last_update_date, last_updated_by, last_update_login, each reduced with min(distinct).
Common Use Cases and Queries
Because the view flattens Japanese income tax element entry data into fixed positions, it is typically used for payroll reporting, regulatory extracts, and integration feeds requiring deterministic column names. A typical query filters by assignment and current date:
- SELECT element_entry_id, assignment_id, effective_start_date, effective_end_date FROM apps.pay_jp_itax_entries_v WHERE assignment_id = :p_assignment_id AND sysdate BETWEEN effective_start_date AND effective_end_date;
- SELECT element_entry_id, element_link_id FROM apps.pay_jp_itax_entries_v WHERE created_by = :p_user AND creation_date >= trunc(sysdate);
- Joining to PAY_ELEMENT_ENTRIES_F using element_entry_id to retrieve additional descriptive context not exposed by the view.
When using the view for extracts, note that the substrb and min(distinct) logic collapses values and may suppress duplicates, so it suits summary reporting rather than audit-grade reconstruction of individual input values. Users should also ensure the FND session is initialised, since the view drives from FND_SESSIONS and relies on the session-based hints for acceptable performance.
-
View: PAY_JP_ITAX_ENTRIES_V 12.2.2
This view is used for Japanese localization only.
APPS.PAY_JP_ITAX_ENTRIES_V·↳ FND_SESSIONS·↳ HR_GENERAL·↳ HR_JP_GENERAL_PKG·Explore PAY module →
-
View: PAY_JP_ITAX_ENTRIES_V 12.1.1
This view is used for Japanese localization only.
APPS.PAY_JP_ITAX_ENTRIES_V·↳ FND_SESSIONS·↳ HR_GENERAL·↳ HR_JP_GENERAL_PKG·Explore PAY module →