Results for “jp_def_pact”

6 results




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

Overview

APPS.PAY_JP_DEF_PACT_V is a reporting view in the Oracle E-Business Suite 12.1.1 and 12.2.2 Payroll (PAY) module, specific to the Japanese localization. It exposes data associated with the Japanese Defined Contribution Pension Plan Agreement (JP_DEF_PACT) action category, presenting a flattened, canonicalized projection of Payroll Action Information records. The view forms part of the Payroll Action Information framework, where actions such as payroll modifications or statutory submissions are stored generically and then surfaced through category-specific views.

The view is read-only by design. It selects from PAY_JP_DEF_PACT_DML_V and applies fixed filters that restrict the result set to rows where ACTION_CONTEXT_TYPE equals 'PA' (Payroll Action) and ACTION_INFORMATION_CATEGORY equals 'JP_DEF_PACT'. This view functions as the supported integration and reporting interface for defined contribution pension plan agreement data, allowing external systems, concurrent programs, and BI Publisher reports to consume numeric and date values in native formats rather than their stored canonical (character) representations.

Underlying Base Objects

The documented base objects referenced by this view are:

The view adds no joins or aggregations of its own; its sole transformation is the canonical-type conversion plus the two literal filters on ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY. This means performance and row population behavior are inherited directly from the underlying DML view.

Key Columns

Common Use Cases and Queries

Typical use cases include reconciliation of defined contribution pension agreement submissions, extraction of salary payer and tax office details for statutory reporting, and feeding downstream interfaces with properly typed values. A representative query follows:

SELECT payroll_action_id,
       effective_date,
       payroll_id,
       organization_id,
       submission_period_status,
       submission_start_date,
       submission_end_date,
       tax_office_name,
       salary_payer_name
FROM   apps.pay_jp_def_pact_v
WHERE  effective_date BETWEEN :p_start AND :p_end;

Because the context type and category are hard-coded, callers need not filter on them. For a single action, query by payroll_action_id; for a status audit, group by submission_period_status. Note that the underlying DML view is used for maintenance, whereas this view should be treated as the read-only reporting interface.