Search Results jp_itax_other2

Overview

APPS.PAY_JP_ITAX_OTHER_V2 is a reporting and integration view in the Oracle E-Business Suite Payroll (PAY) application schema. It exposes a filtered subset of rows from the PAY_ACTION_INFORMATION table, restricted to records whose action information category equals the literal value 'JP_ITAX_OTHER2' and whose action context type equals 'AAP'. In effect, the view is a denominated slice of the generic action-information store, dedicated to a specific Japanese income tax ("ITAX") informational grouping used in Oracle Payroll for Japan localization.

The view does not introduce new data structures, calculations, or business logic. Its purpose is to present the relevant rows with a stable, named interface so that reports, extracts, Fast Formulas integrations, and downstream interfaces can query Japanese income tax "other" information without repeatedly encoding the category and context filter in application code. Because the definition pins both the category and the context type, consumers obtain a consistent, self-documenting data set that is insulated from the breadth of unrelated rows held in the underlying table.

The view follows the standard EBS 12.1.1 / 12.2.2 convention of being owned by APPS and defined over an APPS synonym that resolves to the underlying PAY table. It is exposed in the ETRM (E-Business Suite Technical Reference Manual) metadata as a documented view with the referenced base object listed as PAY_ACTION_INFORMATION (SYNONYM).

Underlying Base Objects

The sole documented referenced base object is PAY_ACTION_INFORMATION, resolved through an APPS synonym. PAY_ACTION_INFORMATION is the EBS Payroll table that stores user-defined, flexfield-style information attached to an action context — in this case payroll actions and assignments. The view is defined entirely over this table, with no joins to other entities in the provided definition.

The definition applies two predicates: action_information_category = 'JP_ITAX_OTHER2' and action_context_type = 'AAP'. The category value identifies the Japanese income tax "other" information grouping, while the context type 'AAP' denotes the assignment-level action context. The view also selects ROWID, which preserves the ability to reference individual underlying rows for update-aware processing or row identification.

Because the view is a simple projection with static predicates, it inherits the columns and data types of the base table directly and carries no independent storage. Any change to the base table structure made through a supported patch or upgrade is reflected automatically in the view, subject to recompilation under the standard EBS patching process.

Key Columns

• ROWID — The physical row identifier of the underlying PAY_ACTION_INFORMATION row.
• ACTION_INFORMATION_ID — Primary surrogate key of the action-information record.
• ACTION_CONTEXT_ID and ACTION_CONTEXT_TYPE — Identify the parent context; in this view the context type is fixed to 'AAP' (assignment-related action context).
• EFFECTIVE_DATE — The date from which the information row is effective, supporting date-tracked queries.
• ASSIGNMENT_ID — The assignment to which the Japanese income tax "other" information relates.
• OBJECT_VERSION_NUMBER — Optimistic locking / concurrency control value.
• ACTION_INFORMATION_CATEGORY — Always 'JP_ITAX_OTHER2' in this view; retained as an explicit column for completeness.
• ACTION_INFORMATION1 … ACTION_INFORMATION30 — The thirty generic descriptor columns that hold the actual Japanese income tax "other" attribute values, as defined by the information type's flexfield configuration.
• LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — Standard EBS audit (WHO) columns.

Common Use Cases and Queries

Typical use cases include Japanese payroll reporting, extraction of income tax "other" data for tax filing interfaces, and lookup by assignment for a given effective date. The following example lists all "other" income tax rows for an assignment:

SELECT action_information_id,
       assignment_id,
       effective_date,
       action_information1,
       action_information2,
       action_information3
FROM   apps.pay_jp_itax_other_v2
WHERE  assignment_id = :p_assignment_id
ORDER  BY effective_date DESC;

The next example returns the current effective row for an assignment as of a given date:

SELECT *
FROM   apps.pay_jp_itax_other_v2
WHERE  assignment_id = :p_assignment_id
AND    effective_date = (SELECT MAX(effective_date)
                         FROM   apps.pay_jp_itax_other_v2
                         WHERE  assignment_id = :p_assignment_id
                         AND    effective_date <= :p_effective_date);

Because the view filters on a fixed category and context type, queries remain concise and are less susceptible to accidental inclusion of unrelated action-information rows. For bulk extracts, standard EBS best practice applies: use a driving query over assignments and join to the view, or select from the view directly with an effective-date predicate to constrain the result set.