Results for “jp_wl_extra_info”

2 results




Overview
Explore in AI Chat

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

Overview

APPS.PAY_JP_WL_EXTRA_INFO_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Payroll module, available in releases 12.1.1 and 12.2.2. It exposes a filtered subset of the PAY_ACTION_INFORMATION table, restricted to records relevant to Japanese payroll "Work Life" (WL) extra information. Specifically, the view returns only rows where ACTION_CONTEXT_TYPE equals 'AAP' and ACTION_INFORMATION_CATEGORY equals 'JP_WL_EXTRA_INFO'.

The view is a conventional (non-materialized) database view. It carries no business logic beyond its WHERE clause filter; it simply presents the underlying action information records in a flattened, accessible form. It provides read access to descriptive flexfield-style data captured against payroll actions for Japanese localization purposes. This object is typically referenced by concurrent programs, reports, and integration interfaces that need to retrieve Japanese payroll statutory or work-life related attributes stored in the generic action information framework.

Underlying Base Objects

The view is defined over a single documented base object: PAY_ACTION_INFORMATION, referenced through a synonym. The view is owned by the APPS schema and relies on that schema's synonym to resolve the underlying table.

PAY_ACTION_INFORMATION is the generic repository for action-level descriptive information in Oracle Payroll. It stores context-typed attribute values keyed by action context and category. The view imposes two constraints on this table: ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_WL_EXTRA_INFO'. Consequently, it selects only the action information rows matching the Japanese Work Life extra information category. No joins, aggregations, or functions appear in the view definition, so it remains a one-to-one projection of qualifying base rows.

Key Columns

The view projects a standard set of identifier, context, audit, and attribute columns:

  • ACTION_INFORMATION_ID — Primary key identifying each action information record.
  • OBJECT_VERSION_NUMBER — Optimistic locking / concurrency control column.
  • ACTION_CONTEXT_ID — Identifier of the parent action context to which this information belongs.
  • ACTION_CONTEXT_TYPE — Always 'AAP' in this view, indicating the action context classification.
  • ASSIGNMENT_ID — The assignment associated with the action information record.
  • EFFECTIVE_DATE — The effective date governing when the information applies.
  • ACTION_INFORMATION_CATEGORY — Always 'JP_WL_EXTRA_INFO', the category defining Japanese Work Life extra information.
  • ACTION_INFORMATION1 through ACTION_INFORMATION30 — Thirty generic attribute columns holding the actual localized data values. Their meaning is determined by the JP_WL_EXTRA_INFO category definition.
  • LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — Standard EBS audit columns tracking who created and last modified each row and when.

ROWID is also selected, exposing the physical row locator for each record.

Common Use Cases and Queries

Typical use cases include Japanese payroll localization reporting, data extraction for statutory reporting, and integration with downstream systems that consume Work Life extra information. A representative query retrieves all records for a given assignment:

  • SELECT * FROM APPS.PAY_JP_WL_EXTRA_INFO_V WHERE assignment_id = :p_assignment_id;
  • SELECT action_context_id, assignment_id, effective_date, action_information1, action_information2 FROM APPS.PAY_JP_WL_EXTRA_INFO_V WHERE effective_date BETWEEN :p_from AND :p_to;
  • SELECT COUNT(*) FROM APPS.PAY_JP_WL_EXTRA_INFO_V WHERE action_information_category = 'JP_WL_EXTRA_INFO';

Because the view filters on fixed values for ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY, queries need not repeat those predicates, though they may be included for clarity. Joins to PER_ALL_ASSIGNMENTS_F or PAY_ACTION_CONTEXTS via ASSIGNMENT_ID and ACTION_CONTEXT_ID respectively are common when building comprehensive payroll reports.