Search Results pay_status_processing_rules_v

Overview

PAY_STATUS_PROCESSING_RULES_V is an APPS-owned database view within the PAY (Payroll) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to support the user interface; it is not a reporting-specific object but a presentation-layer view that supplies the Payroll setup forms with processing rules tied to assignment statuses. The view joins the status processing rule definition to the status type it applies to, an optional amend record, and the associated formula, while filtering on the current FND session and its effective date so that the form displays only rules relevant to the session's effective date.

Because it is a view rather than a table, it stores no data of its own and inherits the security, partitioning, and multi-org characteristics of the underlying objects. It is read-mostly in practice and is typically queried by the Payroll setup UI rather than being written to directly.

Underlying Base Objects

The view is defined over the following documented objects:

• PAY_STATUS_PROCESSING_RULES_F (synonym) — the core table holding the status processing rule rows, including effective dates, legislation, element type, assignment status type, formula, and processing rule.
• PAY_ASS_STATUS_TYPES_PLUS_STD (view) — provides the original assignment status type, including standard statuses that are not stored as amendable rows.
• PER_ASS_STATUS_TYPE_AMENDS (synonym) — supplies amended user status values where an amendment exists; the outer join means the original status is used when no amendment is present.
• FF_FORMULAS_F — the base formulas table joined via FORMULA_ID to expose FORMULA_NAME and effective dates.
• FND_SESSIONS (synonym) — used with USERENV('SESSIONID') to restrict rows to the effective date of the current session.
• Packages HR_API and FND_NUMBER are referenced in the documented metadata as supporting objects.

The joins combine the processing rule with its status type, its optional amendment, and its formula, all filtered by the active session's effective date.

Key Columns

• STATUS_PROCESSING_RULE_ID — primary identifier of the processing rule row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the rule.
• BUSINESS_GROUP_ID, LEGISLATION_CODE, LEGISLATION_SUBGROUP — the business group and legislative context of the rule.
• ELEMENT_TYPE_ID, ASSIGNMENT_STATUS_TYPE_ID — the element type and assignment status type the rule applies to.
• FORMULA_ID / SAVED_FORMULA_ID — the current and saved formula identifiers (SAVED_FORMULA_ID mirrors FORMULA_ID).
• PROCESSING_RULE — indicates the rule behavior; the view text shows special handling for 'P' (STANDARD) and 'B' (BAL_ADJUST) lookup codes.
• FORMULA_NAME — descriptive name of the associated fast formula.
• USER_STATUS — derived as NVL(AMENDED.USER_STATUS, ORIGINAL.USER_STATUS), returning the amended user status when present, otherwise the original.
• ROW_ID — the underlying ROWID of PAY_STATUS_PROCESSING_RULES_F.
• Standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN are also exposed.

Common Use Cases and Queries

The view is principally used by the Payroll setup UI to render status processing rules for the session's effective date. Reporting queries should therefore set the FND session context or filter on effective dates explicitly, and must be aware that USER_STATUS and FORMULA_NAME are resolved through joins.

A representative query lists active rules for a legislation:

• SELECT status_processing_rule_id, legislation_code, assignment_status_type_id, processing_rule, formula_name, user_status, effective_start_date, effective_end_date FROM pay_status_processing_rules_v WHERE legislation_code = :p_legislation ORDER BY effective_start_date DESC;

To inspect the formula bound to each rule, join on FORMULA_ID or use the exposed FORMULA_NAME directly. Because the view is date-effective and session-sensitive, any programmatic use should ensure the correct session effective date is established before querying.