E1: 03B/04: Credit Reimbursement Doesn't Set Error On Future GL Date But Doesn't Create Nor Update Any Records Either (R03B610)
(Doc ID 2232120.1)
Last updated on FEBRUARY 02, 2024
Applies to:
JD Edwards EnterpriseOne Accounts Receivable - Version 9.0 and laterJD Edwards EnterpriseOne Accounts Payable - Version 9.0 and later
Information in this document applies to any platform.
Symptoms
When a future date is used in the G/L date processing option on the 'Defaults' tab of the Credit Reimbursement (R03B610) processing options, the UBE does not create an voucher with document type (DCT) NO, nor does it close out the credit memo it was run for.
However, neither the R03B610 PDF nor the work center show any errors.
The UBE log for the R03B610 shows the following error:
Error 0066 - Date Is in a Future Month (PACO)
CAUSE.......... The date being edited is not in the current month or the next month, but in a future month.
RESOLUTION..... This is a Warning. Either change the date or press Enter or the appropriate function key to accept it.
Note: In some cases the R03B610 returns Error 4473 - Date Is In Future Fiscal Year
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 |