EAR9.2: AR_DUNNING Dunning Letter is Generated With Incorrect Level
(Doc ID 2860161.1)
Last updated on OCTOBER 02, 2023
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Dunning level that is used to define the letter code (setup to print the severest letter) is also taking items into account that should not really impact the Dunning level.
1. Navigate to Customers / Customer Information / Create Customer Information and Create new customer and select Dunning ID
2. Navigate to Setup Financials/Supply Chain -> Product Related -> Receivables -> Credit/Collections -> Dunning Methods and Setup Dunning Method
Set interval to 0 day so I can test multiple letters on the same day
3. Create Items (debit and credit) for first letter for Customer
4. Verify Entry types to include in Dunning: IN and CR
5. Navigate to Accounts Receivables /Customer Interactions / Dunning Letters / Extract Dunning Letter and Run Dunning extract (and print):
6. Check History of Letters:
First Letter (sequence 1 with letter code 1)
7. Run Dunning second time:
8. Check Second Letter (sequence 2 with letter code 2)
9. Now remove ITEM “IN” from open balance
10. Add new Invoice Item "IN"
11. Run Dunning as both the old credit (which was already in level2) and the new item which is not on any letter) are overdue
12. Check History of Letters:
Letter prints in sequence 3, so the credit invoice is the factor that decides the level where you would normally not expect payment for a credit (similar to an on account payment)
Attached OSS.docx replication file.
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