My Oracle Support Banner

11i: General Ledger Journal Import Troubleshooting Guide (Doc ID 330821.1)

Last updated on MARCH 29, 2018

Applies to:

Oracle General Ledger - Version 11.5 to 11.5.10.2 [Release 11.5.0 to 11.5.10]
Information in this document applies to any platform.
Executable:GLLDEL - Delete Journal Import Source
Executable:GLLEZL - Journal Import
Executable:GLLEZLSRS - Executable to allow submission of Journal Import through the Standard Request Submission
Form:GLXJICOR.FMB - Correct Journal Import Data
Form:GLXJIDEL.FMB - Delete Journal Import Data
Form:GLXJIRUN.FMB - Import Journals


Purpose

This troubleshooter can provide a solution for some of the most frequent problems related to General Ledger (GL) Journal Import functionality.

You may also wish to check <Note 342391.1> General Ledger Journal Import FAQ

About Journal Import

Journal Import, sometimes also called EZLINK or EASYLINK, is the process which creates General Ledger Journal Entries for the Accounting transactions that originated as a result of normal business activities in Financial and Manufacturing modules of Oracle Applications, as well as in external and legacy modules.

  1. Each subledger populates the GL_INTERFACE table using their own specific process. Some can automatically launch the Journal Import program.
  2. The Journal Import process validates the data in the the GL_INTERFACE table and loads the validated data into General Ledger tables, creating unposted batches.
  3. If the data is invalid it will not be imported and will stay in the GL_INTERFACE table, flagged with an error label, waiting for corrective actions or deletion.
  4. After correction of the errored lines, Journal Import can be submitted again.
  5. At the end of the process, the lines successfully imported are deleted from the interface table.
  6. The Journal Import process generates the Journal Import Execution report with a summary of the Journals successfully created and a summary of the batches with validation errors.
    A log file showing possible execution errors is also produced.

Please note that if you are using the Multi-Table Journal Import feature, the references to the GL_INTERFACE table must be changed to the interface table name you are using.

Troubleshooting Steps

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
Purpose
 About Journal Import
Troubleshooting Steps
 
 A) Form GLXJIRUN: Import Journals
 A-1) FRM-41830: List of values contains no entries for Group_id
 A-2) FRM-40212: Invalid value for field Group_id
 A-3) APP-00268: Please specify a valid printer
 A-4) Cannot select some Batches with previous import errors
 A-5) The 'All Group_ids' option is missing
 A-6) The Group_id default value changed to All Group Ids
 A-7) Labels with garbage Arabic characters
 
 B) Standard Report Submission for Journal Import (SRS)
 B-1) GLLEZLSRS errors with FND-CANNOT FIND FILE
 B-2) Missing option 'All Group IDs' in GLLEZLSRS program parameters
  
 C) GLLEZL errors during the Journal Import execution
 C-1) Import Validation Errors
 C-1.1) Interface Data is Correct:
 C-1.2) Source system data can be fixed and re-transferred
 C-1.3) Source system data cannot be fixed and/or re-transferred
 C-2) Import Execution Errors
 C-2.1) ORA-00054 Error in gllaar
 C-2.2) ORA-00604, ORA-00904 Error in gllcje
 C-2.3) ORA-00904 Error in gllcje
 C-2.4) ORA-00942, ORA-06512 Error in gluddl
 C-2.5) ORA-01003 Error in gllcje
 C-2.6) ORA-01041 Error in fdfgcd
 C-2.7) ORA-01400 Error in gllchd
 C-2.8) ORA-01403 Error in gllccl
 C-2.9) ORA-01403 Error in gllcje.gllale
 C-2.10) ORA-01403 Error in gllcnt
 C-2.11) ORA-01403 Error in gllcoa
 C-2.12) ORA-01403 Error in glldhkc
 C-2.13) ORA-01403 Error in gllseq
 C-2.14) ORA-01403 Error in gllsys
 C-2.15) ORA-01403 Error in glpiil
 C-2.16) ORA-01410 Error in gllcje
 C-2.17) ORA-01455 Error in gllsys
 C-2.18) ORA-01632
 C-2.19) ORA-01652
 C-2.20) ORA-01653
 C-2.21) ORA-01654
 C-2.22) ORA-03113 Error in gllcje
 C-2.23) APP-00416 sfmmll cannot allocate memory
 C-2.24) APP-FND-01388
 C-2.25) LEZL0008: Found no interface records to process.
 C-2.26) SQL-2112 Error in gllsys
 C-2.27) Terminated by Signal 11 or Signal 10
 
 D) Import Performance
 
 E) Import Printing Errors
 E-1) Execution Report doesn't print
 E-2) Only Report Title is printed
 
 F) Data issues on Imported Journals
 F-1) Account - Default Values on NULL segments
 F-2) Account - Disabled segment values imported
 F-3) Account - Security Rules are ignored
 F-4) Amounts - Negative amounts imported
 F-5) Amounts - both Debit and Credit on the same line
 F-6) Amounts - converted amounts are zero
 F-7) Batches Merged by Journal Import
 F-8) Currency - currency type changed to 'User'
 F-9) GL_Interface_History issues
 F-10) How is the imported journals Batch Name derived?
 F-11) How are the accounting Periods and Dates derived by Journal Import?
 F-12) The imported journal lines description is always 'Journal Import Created'.
 F-13) How are imported lines ordered in a journal and how can this be controlled?
 F-14) How are the imported journals Names derived?
 F-15) Journal Entry not updateable
 F-16) Missing Journal Lines
 F-17) Missing Journals imported from a sub-ledger
 F-18) References - not being imported
 F-19) Tax fields not populated on Imported Journals
 
 G) Form GLXJIDEL: Delete Journal Import Data
 G-1) Cannot delete ADI journals when logged with NLS language
 G-2) The List of Values does not contains the desired data
 G-3) Translation problems
 
 H) During Delete Journal Import Source process
 H-1) Data is not deleted from GL_INTERFACE
 
 I) Form GLXJICOR: Correct Journal Import Data
 I-1) Entered Account Code Combinations are not verified by the defined Secutity Rules
 I-2) Error APP-00812 plus ORA-1722
 I-3) Error FRM-40505 plus ORA-1722 or FRM-40734
 I-4) Error FRM-40654
 I-5) Frozen journal Source allowing updates
 
J) On Interface Data Transformer
 
Still Have Questions?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.