Results for “pay_jp_itax_other_v2”

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

Overview

PAY_JP_ITAX_OTHER_V2 is a read-only database view owned by the APPS schema in Oracle E-Business Suite. As its name and ETRM classification indicate, the object is specific to the Japanese localization of Oracle Payroll (PAY). The view does not store data itself; it presents a filtered projection of the underlying action information repository, restricting the result set to a single logical category of records. Its documented status is VALID and its object type is VIEW, confirming it is a queryable, non-materialized definition rather than a base table.

The view exists to give Japanese payroll processing and its dependent reports, concurrent programs, and integrations a stable, purpose-built access path to a well-defined slice of payroll action data. By binding the category and context filters into the view definition, Oracle isolates the Japanese income tax "other" data set from the much larger, generic action information store, so that consumers do not need to replicate the filtering logic themselves. This segregation supports both reporting and downstream data exchange without exposing the entire population of payroll action records.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: PAY_ACTION_INFORMATION, accessed through a synonym. PAY_ACTION_INFORMATION is the standard Payroll action information table, a wide, generic structure that stores supplemental data associated with payroll actions using indexed slots rather than dedicated columns. The view is defined directly over this table with two predicate filters applied in its WHERE clause: ACTION_INFORMATION_CATEGORY must equal 'JP_ITAX_OTHER2' and ACTION_CONTEXT_TYPE must equal 'AAP'.

The view text selects the ROWID pseudo-column together with ACTION_INFORMATION_ID, ACTION_CONTEXT_ID, the context type and category, EFFECTIVE_DATE, ASSIGNMENT_ID, OBJECT_VERSION_NUMBER, the thirty generic ACTION_INFORMATIONn slots, and the standard Who columns (LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE). The category 'JP_ITAX_OTHER2' identifies this as the Japanese income tax "other" information set, and the context type 'AAP' scopes the records to the applicable payroll action context. Because all filtering is embedded in the definition, any query against the view is automatically constrained to this category and context combination.

Key Columns

• ACTION_INFORMATION_ID — Primary identifier for the underlying action information row.
• ACTION_CONTEXT_ID / ACTION_CONTEXT_TYPE — Identify the payroll action context; the view is fixed to context type 'AAP'.
• ACTION_INFORMATION_CATEGORY — Fixed to 'JP_ITAX_OTHER2', the defining filter of the view.
• ASSIGNMENT_ID — Links the record to the employee assignment to which the tax information applies.
• EFFECTIVE_DATE — Date from which the associated data is effective, supporting date-tracked lookups.
• ACTION_INFORMATION1 through ACTION_INFORMATION30 — Generic attribute slots whose meaning depends on the category and localization configuration; for the Japanese income tax set they carry the tax-specific data elements.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the underlying framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns maintained by the application.

Note that the documented column list also references derived Japanese descriptors such as DESCRIPTION_KANJI, DESCRIPTION_KANA, FILE_DESCRIPTION variants, and override flags; these are presented as available descriptive attributes for the localization rather than as columns in the view text excerpt itself.

Common Use Cases and Queries

The principal use cases are Japanese payroll reporting, income tax data extraction, and integration with external filing or local statutory processes. Because the view already constrains category and context, consumers query it as if it were a dedicated table.

• Retrieve all tax records for a given assignment: SELECT * FROM apps.pay_jp_itax_other_v2 WHERE assignment_id = :assignment_id;
• Retrieve records effective within a period: SELECT action_information_id, effective_date, action_information1 FROM apps.pay_jp_itax_other_v2 WHERE effective_date BETWEEN :start_date AND :end_date;
• Join to assignment or person data to enrich a statutory report: SELECT v.assignment_id, v.effective_date, v.action_information1 FROM apps.pay_jp_itax_other_v2 v, apps.per_all_assignments_f a WHERE v.assignment_id = a.assignment_id;
• Audit recently changed rows: SELECT action_information_id, last_update_date, last_updated_by FROM apps.pay_jp_itax_other_v2 WHERE last_update_date > SYSDATE - 7;

As with all APPS-owned views, access should be granted through the application's security model, and the underlying category and context values should be treated as fixed contract elements of the view.