Search Results current_session




Overview
Explore in AI Chat

Overview

APPS.PAY_STATUS_PROCESSING_RULES_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view that exposes the effective-dated status processing rules used by Oracle Payroll to determine how an assignment status change is processed. It joins the underlying rule definition table to the assignment status type hierarchy and to the formula that governs the rule's behavior, producing a single denormalized row per applicable rule.

The view plays a critical role in payroll reporting and integration because processing rules decide whether a status change triggers payroll processing, a balance adjustment, or no action at all. Unlike the base table, the view resolves the enacted status type name (merging the original standard status type with any legislative amendment) and resolves the current formula name, so consumers do not need to re-create those joins. Its name and column set make it a convenient source for payroll and HR extracts, Fast Formula diagnostics, and rule maintenance reports.

Underlying Base Objects

The ETRM documented base objects for this view are FF_FORMULAS_F_VL, FND_NUMBER, FND_SESSIONS, HR_API, PAY_ASS_STATUS_TYPES_PLUS_STD, PAY_STATUS_PROCESSING_RULES_F, and PER_ASS_STATUS_TYPE_AMENDS. Only two of these are true base tables: PAY_STATUS_PROCESSING_RULES_F (the effective-dated rule definition, referenced through a synonym) and PER_ASS_STATUS_TYPE_AMENDS (assignment status type amendments). The remaining objects are views, synonyms, or packages that supply derived data and services.

  • PAY_STATUS_PROCESSING_RULES_F — the primary table supplying status_processing_rule_id, effective_start_date, effective_end_date, business_group_id, legislation_code, element_type_id, assignment_status_type_id, formula_id, processing_rule, comment_id, legislation_subgroup, and audit columns.
  • PAY_ASS_STATUS_TYPES_PLUS_STD — a view providing the standard assignment status types; joined on assignment_status_type_id to supply the base status type.
  • PER_ASS_STATUS_TYPE_AMENDS — supplies amended user_status values for legislative variations; the view uses NVL(amended.user_status, original.user_status) to resolve the effective status name.
  • FF_FORMULAS_F_VL — joined with an outer (+) operator to supply formula_name; because the join is outer, rules without a formula still appear.
  • FND_SESSIONS — provides current_session, accessed through userenv('sessionid') to obtain the effective date of the current session. HR_API and FND_NUMBER are supporting objects for status type derivation.

Key Columns

  • status_processing_rule_id — primary identifier for the rule.
  • effective_start_date / effective_end_date — date range for which the rule is valid; the view filters to the session's effective date.
  • business_group_id, legislation_code, legislation_subgroup — rule ownership and legislative scope.
  • element_type_id — the element type the rule applies to.
  • assignment_status_type_id — the assignment status type governed by the rule.
  • user_status — resolved status name from the original or amended status type.
  • processing_rule — code indicating the action (for example 'P' for standard processing or 'B' for balance adjustment).
  • formula_id, saved_formula_id, formula_name — the formula driving the rule; formula_id and saved_formula_id are the same value.
  • comment_id, creation_date, created_by, last_update_date, last_updated_by, last_update_login, row_id — audit and row-identification columns.

Common Use Cases and Queries

The view is most often queried to list currently active processing rules for a business group, to inspect which formula is attached to a rule, or to validate that status changes will be handled as intended. Because the view applies a session-effective-date filter, it returns only rules valid on the current session's effective date.

SELECT status_processing_rule_id,
       user_status,
       processing_rule,
       formula_name,
       effective_start_date,
       effective_end_date
  FROM apps.pay_status_processing_rules_v
 WHERE business_group_id = :p_business_group_id
 ORDER BY user_status;

A second frequent pattern searches rules whose processing rule code is not standard, or identifies rules missing a formula (formula_name IS NULL). The current_session term appearing in the user's search reflects the internal FND_SESSIONS join and the userenv('sessionid') predicate, which is the mechanism the view uses to enforce effective-date filtering against the caller's session.