Pre-saved WEBADI Templates Gives 'Journal Import finds no records in GL_INTERFACE for processing' During Journal Import
(Doc ID 1957466.1)
Last updated on OCTOBER 10, 2022
Applies to:
Oracle General Ledger - Version 12.1.3 to 12.2.5 [Release 12.1 to 12.2]Oracle Web Applications Desktop Integrator - Version 12.1.3 and later
Information in this document applies to any platform.
Executable:GLLEZL - Journal Import
Symptoms
Cannot upload WebADI spreadsheet into Journals after saving the file. An error message is displayed at Journal Import
ERROR
-----------------------
Journal Import finds no records in GL_INTERFACE for processing.
Check LEDGER_ID, USER_JE_SOURCE_NAME, and GROUP_ID of import records
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Connect to the eBS application using the local preferred language, that is Polish
2. Navigate to GL -> Journals -> Wizard and generate a 'Journal Import - Single' WebADI document
3. Fill-in the data in the spreadsheet and Upload the data using the 'Automatically launch Journal Import' flag (not saving yet the excel file).
Data are uploaded to the GL_Interface, journal import is submitted and finishes correctly generating the journals.
4. Now save the excel file, close it and reopen. Notice the WebADI menu option (Oracle Add-in) is in Polish, as desired. Retry to upload data checking 'Automatically launch Journal Import'. This time data reaches the GL_INTERFACE table but the Journal Import fails with the following message:
Journal Import finds no records in GL_INTERFACE for processing.
Check LEDGER_ID, USER_JE_SOURCE_NAME, and GROUP_ID of import records.
Notice that this time the automatically launched 'Journal Import' request is in English, whereas at step 3 (prior to save the file) the request that gets completed correctly is in Polish language.
Also, tried with both checked and unchecked 'Import Using Key' flag on journal sources but the issue remained.
The action can be performed with no problem for a newly created document but only before saving it.
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 |
Cause |
Solution |
References |