Search Results jp_itax_person

Overview

APPS.PAY_JP_ITAX_PERSON_V is a reporting and integration view in Oracle E-Business Suite that exposes Japanese income tax ("ITAX") person-level information captured within the Oracle Payroll action information framework. In Oracle EBS 12.1.1 and 12.2.2, the view presents a filtered, denormalized projection of the PAY_ACTION_INFORMATION table, restricting rows to a single action information category — JP_ITAX_PERSON — combined with a single action context type — AAP (Assignment Action). This combination indicates that the underlying records represent Japanese income tax attributes associated with a specific payroll assignment and its corresponding action.

From the perspective of EBS reporting and integration, the view abstracts the polymorphism of PAY_ACTION_INFORMATION, where dozens of different functional categories share a common set of thirty generic payload columns (ACTION_INFORMATION1 through ACTION_INFORMATION30). By applying the JP_ITAX_PERSON and AAP predicates at the view level, the view offloads filtering logic from consuming queries and provides a semantically meaningful surface for extraction, reconciliation, and downstream localization reporting.

Underlying Base Objects

According to the documented ETRM metadata, the view references a single base object: PAY_ACTION_INFORMATION (documented as a SYNONYM pointing to the underlying table, typically PAY_ACTION_INFORMATION owned by the APPLSYS or PAY schema within the APPS synonym layer).

Because the view is defined over a synonym rather than a direct table reference, it participates in the standard EBS synonym architecture: APPS.PAY_JP_ITAX_PERSON_V is compiled against APPS.PAY_ACTION_INFORMATION, which resolves to the actual table at runtime. No joins are present. The view is a simple horizontal filter composed of two predicates:

• ACTION_INFORMATION_CATEGORY = 'JP_ITAX_PERSON' — isolates Japanese income tax person records.
• ACTION_CONTEXT_TYPE = 'AAP' — restricts to assignment-level action context.

Key Columns

The view projects every column present in PAY_ACTION_INFORMATION. The structurally significant columns include:

• ACTION_INFORMATION_ID — primary surrogate key of the underlying action information row.
• ACTION_CONTEXT_ID — identifier of the action context; combined with ACTION_CONTEXT_TYPE = 'AAP', this corresponds to the assignment action instance.
• ACTION_CONTEXT_TYPE — constant 'AAP' within this view, denoting assignment-level context.
• ASSIGNMENT_ID — the payroll assignment to which the Japanese income tax person details belong.
• EFFECTIVE_DATE — the date from which the record's information is effective.
• ACTION_INFORMATION_CATEGORY — constant 'JP_ITAX_PERSON' within this view; the discriminator for the record type.
• ACTION_INFORMATION1 … ACTION_INFORMATION30 — the generic payload attributes whose meaning is defined by the JP_ITAX_PERSON category. These hold the localized Japanese income tax person fields.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework.
• LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — standard EBS who-columns for audit and lineage.
• ROWID — physical row address exposed for update-through-view or performance purposes.

Common Use Cases and Queries

The view is commonly used in Japanese localization reporting, data extraction to external payroll engines or tax filing tools, and reconciliation of assignment-level income tax person attributes held in action information. Typical queries include:

• Listing all ITAX person records for an assignment:
  SELECT action_information_id, assignment_id, effective_date, action_information1, action_information2
  FROM apps.pay_jp_itax_person_v
  WHERE assignment_id = :p_assignment_id;
• Extracting current records as of a date:
  SELECT assignment_id, effective_date, action_information1
  FROM apps.pay_jp_itax_person_v
  WHERE effective_date <= :p_as_of_date;
• Audit and lineage checks:
  SELECT action_information_id, last_updated_by, last_update_date
  FROM apps.pay_jp_itax_person_v
  WHERE last_update_date >= :p_since;
• Bulk integration export: full-select of the view into a staging table or file for downstream Japanese tax processing.

Because the view is read-only in practice and predicate-bound, queries should filter further using ASSIGNMENT_ID or EFFECTIVE_DATE to avoid scanning the full action information population.