Results for “pay_jp_itwb_pact_v”

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

Overview

The APPS.PAY_JP_ITWB_PACT_V view is a Japanese localization object within the Oracle E-Business Suite Payroll (PAY) module. It exposes a filtered, structured projection of action information records specifically associated with the JP_ITWB_PACT action information category, which supports Japan-specific payroll processing requirements such as the Income Tax Withholding Book (ITWB) and payment action (PACT) data handling.

In Oracle EBS 12.1.1 and 12.2.2, this view is registered in the ETRM as a VALID object owned by the APPS schema with "Japanese localization only" scope. It is not a general-purpose payroll view; it serves as a declarative data access layer over the PAY_ACTION_INFORMATION table, giving reporting, extraction, and integration routines a stable, pre-filtered interface. By restricting rows to ACTION_CONTEXT_TYPE = 'PA' and ACTION_INFORMATION_CATEGORY = 'JP_ITWB_PACT', the view isolates the Japan withholding and payment action records without requiring each consumer to replicate the filter logic.

Underlying Base Objects

According to the documented view definition, PAY_JP_ITWB_PACT_V is defined over two referenced objects:

• PAY_ACTION_INFORMATION (SYNONYM) — the primary base object, supplying all transactional columns. The synonym resolves to the underlying PAY_ACTION_INFORMATION table in the APPS schema, the repository of context-specific action information used across payroll action processing.
• FND_NUMBER (PACKAGE) — the Oracle Application Object Library package invoked for numeric conversion. The view calls FND_NUMBER.CANONICAL_TO_NUMBER to translate stored character-formatted amounts into canonical numeric values.

The view text selects a fixed column list from the base table, applies DECODE logic keyed on ACTION_INFORMATION_CATEGORY, and returns NULL for the numeric expressions when the category is not JP_ITWB_PACT. Because the WHERE clause already constrains the category, the DECODE serves primarily as a defensive guard and a consistent column-typing mechanism.

Key Columns

The view projects the following columns, several of which are central to Japan localization reporting:

• ROW_ID — the physical ROWID of the underlying action information row, exposed for direct row addressing.
• ACTION_INFORMATION_ID — the surrogate primary identifier of the action information record.
• OBJECT_VERSION_NUMBER — the optimistic locking / versioning column used for concurrent update control.
• PAYROLL_ACTION_ID and PAYROLL_ACTION_ID_O — the payroll action linkage, tying the information record to its parent payroll action.
• ACTION_CONTEXT_TYPE — fixed to 'PA' for payroll action context.
• ACTION_INFORMATION_CATEGORY — fixed to 'JP_ITWB_PACT'.
• EFFECTIVE_DATE — the date on which the action information takes effect.
• STATUS — processing status indicator.
• ITAX_ORG_ID — the organization identifier relevant to the Japan income tax context.
• ARCHIVE_SEQUENCE — the archive sequencing column, which the user specifically searched for. It identifies the archive run or sequence to which the record belongs, supporting archival and purge-related reporting.
• Numeric amount columns — derived from ACTION_INFORMATION2, ACTION_INFORMATION3, and ACTION_INFORMATION4 via FND_NUMBER.CANONICAL_TO_NUMBER, presented as canonical numbers.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical usage centers on Japan payroll extraction, archival tracking, and reconciliation.

• Archive sequence reporting:

  SELECT payroll_action_id, archive_sequence, effective_date, status
  FROM   apps.pay_jp_itwb_pact_v
  WHERE  archive_sequence IS NOT NULL
  ORDER  BY archive_sequence;

• Extraction by action:

  SELECT action_information_id, payroll_action_id,
         itax_org_id, effective_date
  FROM   apps.pay_jp_itwb_pact_v
  WHERE  payroll_action_id = :p_action_id;

• Audit/change tracking: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to reconcile records modified within a period.

Because the view is restricted to the Japanese localization, queries should be scoped to Japanese payroll actions. All access is read-oriented and flows through the APPS schema.