E1: 03B: Known Invoice with Amount (R03B50D) does not use Alternate Payor (PYR) to find invoices to match
(Doc ID 2628637.1)
Last updated on JULY 08, 2021
Applies to:JD Edwards EnterpriseOne Accounts Receivable - Version 9.1 and later
Information in this document applies to any platform.
When one customer, e.g. Customer A, pays for the invoice of another customer, e.g. Customer B, the Known Invoice with Amount algorithm (R03B50D) does not find Customer B’s invoice for the receipt. This is even if the Address Number (alias AN8) of Customer A is set as the Alternate Payor (PYR) for the invoice in the Customer Ledger table (F03B11).
STEPS TO REPRODUCE
- P0000: activate Auto Receipts for company 00000 and the test company.
- BV: set up versions for the following UBEs:
- P03B50: set up an Execution List with the R03B50D version.
- P03012 & P01012: create two customers:
- Set up one as the Alternate Payor for the other, but NOT as the parent.
- P03B2002/P03B11: create two invoices, one for each customer.
- R09801: post the invoices.
- P03B121: create an electronic receipt for the ‘child’ customer and put the AN8 of the Alternate Payor in the Customer Number field.
- Run R03B551.
- Run R03B50.
- Verify the outcome via Standard Receipts (P03B102), Customer Ledger Inquiry (P03B2002), and Electronic Receipts Revisions (P03B121).
The system specifically searches for and assigns the Payor of an invoice to the receipt, before it assigns the Customer of the invoice to the receipt. Per the definition of the required field called Address Number (RUAN8) in Appendix B of the A/R guide:
Enter the address book number of the customer. The number that you enter must exist in the Address Book Master table (F0101).
If you leave this field blank and complete the Customer Bank Account (RUCBNK) and Customer Bank Transit (RUTNST) fields, the system uses the bank account information to identify the payor and then assign the payor number to the customer.
If these fields (RUAN8, RUCBNK, and RUTNST) are blank, but the Document Number field (RUDOC) or the Generic Matching field (RUGMFD) is not blank, the system uses the invoice information in these fields to locate the payor number and then assign the payor number to the customer. If the Document Number and Generic Matching fields are blank too, the system either uses the default value entered in the processing options for the Update Receipts Header program to get a payor and customer number or generates a logged receipt record.
To increase performance, enter the customer's address book number so that the system does not to retrieve the value from another table.
Since it does specifically search for the payor to assign to the receipt first, the system should use the payor value first to find invoices to match to the receipt.
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