Search Results master_payroll_action_id

Overview

APPS.PAY_JP_WL_PACT_V is a database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents action information records used by the Japanese payroll localization, specifically data associated with work loss (WL) and payment action (PACT) processing. The view exposes rows drawn from the PAY_ACTION_INFORMATION repository, combining that base data with derived numeric values supplied by the FND_NUMBER package. Its FND Design Data identifier is PAY.PAY_JP_WL_PACT_V, and the object carries a VALID status in the data dictionary.

The view functions as a read-oriented reporting and integration surface. Because the underlying PAY_ACTION_INFORMATION table stores payroll action context as flexible, category-driven rows rather than fixed columns, the view flattens that structure into a stable columnar shape. This makes the Japanese statutory payment and work-loss information easier to consume in BI Publisher reports, extracts, interfaces, and custom concurrent programs without requiring callers to reconstruct the entity-attribute-value model themselves. It is not referenced by any other database object, confirming its role as a terminal reporting layer rather than a dependency for further application logic.

Underlying Base Objects

The documented base objects are limited to two entries:

• PAY_ACTION_INFORMATION (SYNONYM) — the primary source of rows and columns. This table stores action information records linked to assignment actions and payroll actions, including contextual and descriptive attributes.
• FND_NUMBER (PACKAGE) — a utility package used within the view definition, typically for numeric conversion or normalization of stored values.

Because the view is defined solely over PAY_ACTION_INFORMATION with supporting calls to FND_NUMBER, all persisted data originates in the action information table. The ACTION_INFORMATION_ID column acts as the logical link to the base record, while ASSIGNMENT_ACTION_ID and MASTER_PAYROLL_ACTION_ID tie rows to payroll action processing. No independent storage exists for the view itself.

Key Columns

• ROW_ID — ROWID pseudocolumn for the underlying base row.
• ACTION_INFORMATION_ID — unique identifier of the action information record.
• OBJECT_VERSION_NUMBER — optimistic locking version for the row.
• ASSIGNMENT_ACTION_ID / ASSIGNMENT_ID — links to the assignment action and assignment being processed.
• EFFECTIVE_DATE — date on which the action information takes effect.
• ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY — classify the record so consumers can distinguish among context types and categories.
• SUBJECT_YEAR_MNTH — the year and month to which the record relates; this is the column most frequently searched for, as it drives period-based filtering of Japanese payroll payment and work-loss data.
• ARCHIEVE_OPTION — indicates archival handling for the record.
• MASTER_PAYROLL_ACTION_ID / PAYROLL_ID — identify the associated payroll and its master action.
• WITHHOLDING_AGENT, ASSIGNMENT_SET, STATUS, MASTER_FLAG — descriptive attributes controlling withholding agent identification, assignment set scope, processing status, and master/child designation.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical usage centers on period-based reporting, reconciliation, and interface extraction for Japanese payroll. The SUBJECT_YEAR_MNTH column is the standard filter for restricting output to a given reporting period, while STATUS and MASTER_FLAG are commonly used to isolate active or master-level records.

Retrieve all records for a specific year and month:

• SELECT * FROM APPS.PAY_JP_WL_PACT_V WHERE SUBJECT_YEAR_MNTH = '2024/06';

Restrict to a payroll and period, returning selected attributes:

• SELECT PAYROLL_ID, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_INFORMATION_CATEGORY, STATUS FROM APPS.PAY_JP_WL_PACT_V WHERE PAYROLL_ID = :p_payroll_id AND SUBJECT_YEAR_MNTH = :p_year_mnth;

Filter by assignment set and withholding agent for statutory reporting:

• SELECT * FROM APPS.PAY_JP_WL_PACT_V WHERE ASSIGNMENT_SET = :p_set AND WITHHOLDING_AGENT IS NOT NULL;

Because the view is read-only and not referenced by other objects, it is safe to query directly in custom reports, extracts, and data conversion routines without affecting application logic. Consumers should apply indexed predicates on ASSIGNMENT_ACTION_ID, PAYROLL_ID, or ACTION_INFORMATION_ID where performance is a concern.