Results for “replacement_method”

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

Overview

The view APPS.PAYBV_CHECK_PAYMENTS is a Payroll (PAY) module database object registered in Oracle E-Business Suite as a VALID view owned by the APPS schema. It presents a consolidated, human-readable picture of payroll check payments issued to employees, combining payment-level attributes (cheque date, cheque number, payment method, payment value) with the personal and assignment context of the payee (full name, assignment number, payroll name). Its distinguishing characteristic is the way it surfaces the lifecycle state of each payment — paid, reversed, replaced, or voided — through a decoded STATUS_CODE and matching STATUS description.

Because it draws together person, assignment, payroll, payment method, and pre-payment data, the view functions as a reporting and integration layer for payment investigations, check-reconciliation reporting, voided-check analysis, and feeds to downstream financial or third-party payment-reconciliation systems.

Underlying Base Objects

The documented referenced objects span several EBS schemas and object types:

• Payroll payment objects: PAY_PRE_PAYMENTS, PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_ACTION_INTERLOCKS, PAY_ORG_PAYMENT_METHODS_F, and the PAY_PAYROLLS_F view.
• Person and assignment objects: PER_PEOPLE_F, PER_ASSIGNMENTS_F.
• Utility packages: HR_BIS, HR_GENERAL, HR_PERSON_NAME, HR_PRE_PAY, and HR_SECURITY.

The most significant dependencies are the HR packages. HR_BIS.BIS_DECODE_LOOKUP performs the lookup decoding that produces user-facing status, replacement-method, and yes/no indicators, while HR_SECURITY supplies the business-group security profile used in the BG_SECURITY_FL expression. HR_PERSON_NAME and HR_PRE_PAY provide the name-formatting and pre-payment logic respectively.

Key Columns

• Person and assignment: FULL_NAME, ASSIGNMENT_NUMBER, PERSON_ID, ASSIGNMENT_ID, PAYROLL_NAME, PAYROLL_ID.
• Payment detail: CHEQUE_DATE, CHEQUE_NUMBER, PAYMENT_METHOD, VALUE, PROCESS_DATE, DATE_EARNED, OVERRIDING_DATE.
• Void handling (the searched term): VOID_DATE is exposed directly and is the pivotal column in the STATUS_CODE DECODE. When VOID_DATE is NULL, the payment is not voided and the status resolves to 'P' or 'RWV'. When VOID_DATE is not NULL, the nested DECODE yields 'V' (voided), 'C' (replaced by employee), 'R' (replaced by cheque), 'RWMP', or 'MR', depending on whether a replacement exists, its method, and whether a replacement cheque number is present.
• Status and replacement: STATUS_CODE, STATUS (decoded via the PAY_CHECK_STATUS lookup), REPLACEMENT_CHEQUE_DATE, REPLACEMENT_CHEQUE_NUMBER, REPLACEMENT_METHOD, plus the reversal/replacement yes/no indicators.
• Security: BUSINESS_GROUP_ID and BG_SECURITY_FL, which evaluates to 'Y' when the row's business group equals the session's security profile.

Common Use Cases and Queries

A frequent requirement is identifying voided checks by date, which is precisely what the void_date search reflects:

• Voided payment report:

  SELECT full_name, assignment_number, cheque_number, cheque_date, value, void_date, status
  FROM   apps.paybv_check_payments
  WHERE  void_date BETWEEN :p_from AND :p_to
  AND    bg_security_fl = 'Y';

• Replacement check tracing: filter on REPLACEMENT_CHEQUE_NUMBER IS NOT NULL to review checks reissued after a void.
• Payroll reconciliation: aggregate VALUE by PAYROLL_NAME and PAYMENT_METHOD for a PROCESS_DATE range, excluding voided rows.
• Security-scoped extracts: always include BG_SECURITY_FL = 'Y' to honor business-group access in a multi-BG environment.

The view should be treated as read-only and its decoded statuses relied upon only when the underlying lookup values are unchanged.