AP Open Interface Import: Invoice GL Date Defaults Incorrectly In Closed Accounting Period
(Doc ID 2313501.1)
Last updated on OCTOBER 03, 2017
Applies to:Oracle Lease and Finance Management - Version 12.2.5 and later
Information in this document applies to any platform.
When importing Payable invoices from Oracle Lease and Finance Management into Oracle Payables, the 'Invoice GL Date' defaults incorrectly in a Closed accounting period. Due to this, they are stuck in the AP Interface tables with a rejection reason of "GL Date is not in an open period."
The requirement for us is that OLFM should not hardcode the GL Date field in a funding transaction so that the expected scenario works.
The issue can be reproduced at will with the following steps:
1. Created a Funding request # ‘xxxx’ for the above contract for $ 11,000. Invoice date is 15-Jan-17
2. Processed the ‘Pay Invoices Creation of Auto-Disbursement Process’ request. Output does not show our contract / funding created above
3. Processed the ‘Pay Invoice Prepare for AP Transfer’ for the above Contract. In the output, it clearly shows the ‘GL Date’ is also populated as ’15-Jan-17’
4. Process the ‘Pay Invoices Transfer to AP Invoice Interface’. The funding data is transferred to the AP Interface table
5. Query the Invoice in the ‘Open Interface Invoice’ form
6. The header line shows the GL Date populated with 15-Jan-17.
7. The lines shows the Accounting Date populated with 15-Jan-17
8. IF Jan-17 was a closed period in Payables, this invoice will NOT be processed by the ‘Payables Open Interface Import’ – and will be stuck in the interface table. Will then need manual intervention.
9. If we remove the data in the GL Date and Accounting Date fields in the interface table, the ‘Payables Open Interface Import’ imports these invoices successfully – and the GL Dates are populated based on the Payables options setup
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