Results for “pay_check_status”

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

Overview

APPS.PAYBV_CHECK_PAYMENTS is a reporting view in Oracle E-Business Suite Payroll (Oracle HRMS / Payroll) that presents check (cheque) payment information at the assignment level, enriched with descriptive status, method, and security information. It is not a base transaction table but a denormalized query designed to expose payroll disbursement details for external reporting, integration, and user-facing inquiry. The name suggests it belongs to the "BV" (business view) family of reporting objects, which typically join normalized payroll and HR tables and apply lookup decoding so that consumers receive human-readable values rather than raw codes.

Its most notable contribution is the derived status_code and decoded status columns. These are computed using nested DECODE logic that interprets the relationship between void dates, reversals, and replacements. For any check whose status is ambiguous in the raw tables, this view resolves it into a single canonical state. The status column then translates the internal status_code through the lookup table PAY_CHECK_STATUS via the HR_BIS package function bis_decode_lookup. Because the user search term "pay_check_status" maps directly to this lookup, the view is the principal means by which the PAY_CHECK_STATUS lookup is surfaced to report authors and integrators.

Underlying Base Objects

The view is defined over a subquery that joins person, assignment, payroll, and payment tables. Documented referenced base objects include:

• PER_PEOPLE_F and PER_ASSIGNMENTS_F — source of full_name and assignment_number.
• PAY_PAYROLLS_F — source of payroll_name.
• PAY_PRE_PAYMENTS — source of cheque_date, cheque_number, process/effective date, void_date, and value.
• PAY_ORG_PAYMENT_METHODS_F — source of payment_method and original_method_code.
• PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, and PAY_ACTION_INTERLOCKS — used to derive reversal and replacement relationships and effective/process dates.
• HR_BIS, HR_GENERAL, HR_PERSON_NAME, HR_PRE_PAY, HR_SECURITY — packages supplying lookup decoding, name formatting, prepayment logic, and row-level security.

The view therefore does not own data; it is a read-only projection over volatile payroll and HR tables, and its output changes as prepayments are voided or replaced.

Key Columns

• full_name, assignment_number, payroll_name — identity and payroll context.
• process_date, cheque_date, cheque_number — payment identification.
• payment_method — decoded payment method (for example check/cheque).
• value — payment amount.
• status_code — internal computed code (P, C, R, RWV, RWMP, DMP, MR, V) derived from void/reversal/replacement logic.
• status — decoded PAY_CHECK_STATUS value for the code above.
• void_date — date the payment was voided, if any.
• reversal_exist, replacement_exist — YES_NO decoded flags.
• replacement_cheque_date, replacement_cheque_number, replacement_method_code, replacement_method — details of the superseding payment.
• original_method_code, original_method — the pre-replacement method.
• person_id, assignment_id, payroll_id, org_pay_method_id, business_group_id — join keys.
• date_earned, overriding_date — earning context.
• payroll_action_id, assignment_action_id, pre_payment_id — links back to payroll and prepayment transactions.
• bg_security_flag_code — 'Y' when the row belongs to the session's business group, enforcing HR_SECURITY behavior.

Common Use Cases and Queries

Typical usage includes reconciliation of issued versus voided checks, identification of payments superseded by replacements, and extracts feeding treasury or bank systems.

• List all paid checks for an assignment with their decoded status.
• Find checks that have been voided but not yet replaced.
• Report replacement cheque numbers for reconciled items.

Sample query:

SELECT full_name, assignment_number, cheque_number, cheque_date,
       payment_method, value, status, void_date,
       replacement_cheque_number
FROM   apps.paybv_check_payments
WHERE  person_id = :p_person_id
  AND  status_code IN ('P','R','MR','DMP')
ORDER BY cheque_date;

Because of business group security, results are automatically filtered to the session's business group, so no explicit predicate is generally required.