Search Results formatted_value

Overview

APPS.PAY_JP_SOE_PREPAY_PAYMENTS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as PAY.PAY_JP_SOE_PREPAY_PAYMENTS_V. It is classified as a view type "used to simplify forms coding," which indicates that its primary consumer is Oracle Payroll's Japanese Statutory/Statement of Earnings (SOE) prepayment form rather than external reporting or integration layers. The view surfaces prepayment and assignment action data for Japanese payroll processing, combining payment, currency, and action attributes into a denormalized result set that a form can query directly.

Because the view is a forms-support construct, Oracle explicitly warns that it is not recommended for direct querying or data alteration and that its definition may change dramatically in subsequent minor or major releases. Developers searching for marked_for_retry_flag should treat the column as a display-oriented flag exposed for the JP SOE prepayment form, not as a stable public interface.

Underlying Base Objects

The view is defined over a documented set of base objects spanning payroll actions, payment methods, and localization logic:

• PAY_PRE_PAYMENTS — the core prepayment records.
• PAY_ASSIGNMENT_ACTIONS — assignment-level action rows.
• PAY_PAYROLL_ACTIONS — payroll action definitions.
• PAY_PAYMENT_TYPES and PAY_PAYMENT_TYPES_TL — payment type and translated name.
• PAY_ORG_PAYMENT_METHODS_F and PAY_ORG_PAYMENT_METHODS_F_TL — organization payment method and translated name.
• PAY_PERSONAL_PAYMENT_METHODS_F — personal payment method data.
• FND_CURRENCY (package) — currency formatting and validation.
• HR_GENERAL (package) — HR utility logic.
• PAY_JP_SOE_PKG (package) — the Japanese SOE localization package that drives much of the view's derived logic.
• DUAL — used for constant or scalar expressions in the query.

The presence of PAY_JP_SOE_PKG confirms that the view's transformation logic is localized for Japan, and no downstream database objects are documented as referencing it, reinforcing its role as a terminal, form-facing view.

Key Columns

The view exposes eighteen columns. Notable ones include:

• SOURCE_ASSIGNMENT_ACTION_ID and ASSIGNMENT_ACTION_ID — identifiers linking the prepayment to the originating and current assignment actions.
• PRE_PAYMENT_ID — the prepayment record key.
• PAYROLL_ACTION_ID, ACTION_TYPE, D_ACTION_TYPE, and ACTION_STATUS — action context, with D_ACTION_TYPE providing a display-formatted action type.
• MARKED_FOR_RETRY_FLAG — a flag indicating whether the prepayment is marked for retry, used by the form to control reprocessing behavior.
• CATEGORY, PAYMENT_TYPE_NAME, and ORG_PAYMENT_METHOD_NAME — payment classification and method descriptions.
• PRIORITY, VALUE, FORMATTED_VALUE, and CURRENCY_CODE — monetary amount, its formatted display string, and currency.
• EXTERNAL_ACCOUNT_ID and MESSAGES_EXIST_FLAG — external account linkage and indicator that messages exist for the row.

Common Use Cases and Queries

Typical use is restricted to diagnostics or troubleshooting the JP SOE prepayment form. A minimal query follows:

• SELECT PRE_PAYMENT_ID, ASSIGNMENT_ACTION_ID, MARKED_FOR_RETRY_FLAG, ACTION_STATUS, FORMATTED_VALUE, CURRENCY_CODE FROM APPS.PAY_JP_SOE_PREPAY_PAYMENTS_V WHERE MARKED_FOR_RETRY_FLAG = 'Y';
• Filtering by PAYROLL_ACTION_ID isolates prepayments for a given payroll action.
• Joining on ASSIGNMENT_ACTION_ID to PAY_ASSIGNMENT_ACTIONS supports retry-behavior analysis.

Given the documented warning, this view should be used for investigation only, with production reporting directed to the underlying base tables.