Results for “additional_information1”

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

Overview

PAY_JP_WL_EXTRA_INFO_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product family. It exposes a filtered projection of the PAY_ACTION_INFORMATION table, restricted to the Japanese localization context used for payroll action extra information. Specifically, the view returns only rows where ACTION_CONTEXT_TYPE equals 'AAP' and ACTION_INFORMATION_CATEGORY equals 'JP_WL_EXTRA_INFO'. This makes the view a localization-specific access point that isolates Japanese withholding and labor-related extra information records from the larger, generic action information store.

The view plays a supporting role in reporting and integration rather than transactional data entry. Because it surfaces descriptive flexfield-style attributes (ADDITIONAL_INFORMATION1 through ADDITIONAL_INFORMATION30) alongside identification and audit columns, it is well suited to payroll extracts, statutory reporting feeds, and downstream integration interfaces that must read Japanese payroll action details without traversing unrelated action information categories. Its status is VALID, confirming it is a compiled, active object within the APPS schema.

Underlying Base Objects

The view is defined over a single documented base object: PAY_ACTION_INFORMATION, accessed via a synonym. The view text performs a straight SELECT from PAY_ACTION_INFORMATION with two predicate filters applied on ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY. No joins, aggregations, or set operations are involved, so the view is essentially a horizontal slice of the base table.

Because the view selects ROWID and passes through the ACTION_INFORMATION_ID primary key column, each row remains uniquely identifiable and can be correlated back to the base table when required. The OBJECT_VERSION_NUMBER column is also carried forward, preserving optimistic locking semantics for any consumers that need them. The relationship to the base object is therefore one of pure filtering: every row returned by the view exists in PAY_ACTION_INFORMATION, but not every row of PAY_ACTION_INFORMATION is returned.

Key Columns

• ROW_ID / ROWID — The physical row identifier from the base table, useful for direct row addressing.
• ACTION_INFORMATION_ID — Primary key of the underlying action information record; the primary correlation key for integration.
• OBJECT_VERSION_NUMBER — Version token supporting optimistic concurrency control.
• ASSIGNMENT_ID and ACTION_CONTEXT_ID — Link the record to the assignment and action context to which the extra information belongs.
• ACTION_CONTEXT_TYPE — Always 'AAP' in this view, identifying the action context classification.
• ACTION_INFORMATION_CATEGORY — Always 'JP_WL_EXTRA_INFO', the Japanese localization category filter.
• EFFECTIVE_DATE — Date from which the extra information is effective, supporting date-effective reporting.
• ADDITIONAL_INFORMATION1 … ADDITIONAL_INFORMATION30 — The descriptive attribute columns that hold the substantive Japanese payroll extra information payload. The user's search term, "additional_information1", maps directly to the first of these attribute columns.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY provide standard EBS auditing.

Note that the documented column list references ACTION_INFORMATION1 through ACTION_INFORMATION30 in the view text while presenting the exposed names as ADDITIONAL_INFORMATIONn. Consumers should confirm the exact exposed column naming in their release before coding against it.

Common Use Cases and Queries

Typical usage includes Japanese payroll reporting, localization data extracts, and validation of extra information captured against payroll actions. A representative query retrieving the primary identifier, assignment, effective date, and the first additional information attribute is shown below.

• Selecting the first additional information attribute for a given assignment:
  SELECT ACTION_INFORMATION_ID, ASSIGNMENT_ID, EFFECTIVE_DATE, ADDITIONAL_INFORMATION1 FROM APPS.PAY_JP_WL_EXTRA_INFO_V WHERE ASSIGNMENT_ID = :p_assignment_id;
• Extracting all rows effective within a reporting period:
  SELECT ACTION_INFORMATION_ID, EFFECTIVE_DATE, ADDITIONAL_INFORMATION1, ADDITIONAL_INFORMATION2 FROM APPS.PAY_JP_WL_EXTRA_INFO_V WHERE EFFECTIVE_DATE BETWEEN :p_start AND :p_end;
• Joining back to the base table to confirm the filter predicates:
  SELECT v.ACTION_INFORMATION_ID, v.ADDITIONAL_INFORMATION1 FROM APPS.PAY_JP_WL_EXTRA_INFO_V v, APPS.PAY_ACTION_INFORMATION a WHERE v.ACTION_INFORMATION_ID = a.ACTION_INFORMATION_ID;
• Auditing recently changed records:
  SELECT ACTION_INFORMATION_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM APPS.PAY_JP_WL_EXTRA_INFO_V WHERE LAST_UPDATE_DATE >= :p_since;

Because the view contains no aggregates, filters can be pushed efficiently to the base table, though queries should still constrain on ASSIGNMENT_ID or EFFECTIVE_DATE where possible to limit scanned rows.