Oracle EBS R12 Concurrent program "Journal Import" exceptions

Usually the concurrent program “Journal Import“ runs without any problems. Once in a while the program ends in a warning. Checking the output file gives you some information but usually it doesnt give you the whole GL-key. To solve these issues you do need that whole key.

Luckily the output file also has the Journal import “Group ID” it’s usually at the very start.

Once you have that “Group ID” you should then be able to query the table with name “XLA_GLT_<Group ID>“.

With below query you can then dive deeper into the specific entries, maybe even temporarily enable one of the gl-keys if that is required.

Dont forget to modify the segmentX entries to accomodate your GL key setup.

select t.status,
       t.accounting_date,
       t.entered_dr,
       t.entered_cr,
       cc.segment1 || '.' || cc.segment2 || '.' || cc.segment3 || '.' || cc.segment4 || '.' || cc.segment5 gl_key,
       cc.start_date_active,
       cc.end_date_active,
       cc.enabled_flag
  from XLA_GLT_1011023 t
  join gl_code_combinations cc
    on t.code_combination_id = cc.code_combination_id
 where status not in ('PROCESSED', 'P');

As a final note the concurrent program “Purge Temporary Journal Import Interface Tables Created By Subledger Accounting“ (XLADRPGLT) should be scheduled periodically.