My Oracle Support Banner

R12: AP: When Internal Bank Account Number is NULL User Defined Validation(Payee Document Number Required Validation) Set at Payment Template Level is not Stopping the PPR from Picking Invoices to Create Payments (Doc ID 2884299.1)

Last updated on DECEMBER 07, 2023

Applies to:

Oracle Payables - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

User Defined Validations to stop invoices being selected from Payment Process Request when the Internal Bank Account Number is NULL has been setup at payment template level but does not stop invoices without bank accounts assigned from being picked up when PPR Runs.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Responsibility: Oracle Payables
2. Path: Payment Manager: Payment Process Request
3. Create a Payment Process Request

User Defined Validations have been setup at payment template level to prevent the invoice from picking up in a PPR batch if the remit to bank account name or number is missing from Invoice .

Payables Responsibility ==> Set up ==> Payments  ==> Payment Administrator ==> Formats ==> Formats

Payment method level Validation Set is not an option because they do manual payments in the system which do have bank accounts assigned.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.