GLLEZL : Error EM17 in Journal Import (Doc ID 205926.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle General Ledger - Version 11.5.3 and later
Information in this document applies to any platform.
Executable:GLLEZL - Journal Import

Symptoms

Issue 1:

Why does the journal import fail with EM17 when the Sequential Numbering profile is set to not used for the General Ledger Application?

Issue 2:     

Why does journal import launched from payables using create journal entries fail with ' EM17 Sequential numbering is always used and there is no assignment for this ledger and journal entry category '.
In GL we have setup the sequential numbering profile to partially used at site level.

 Issue 3:

  • EM17 Sequential numbering is always used and there is no assignment for this set of books and journal entry category
  • Sequential numbering is not used on the consolidated set of books
  • Sequential numbering is used on the subsidiary set of books
  • Consolidation run using subsidiary responsibility

 Issue 4:

Attempting to import journals from ADI and receiving errors:
EM17 -Sequential numbering is always used and there is no assignment for this ledger and journal entry category

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms