Using Xla_journal_entries_pub_pkg g_batch_name VARCHAR2(50) unsync JE_BATCH_NAME VARCHAR2(100)
Last updated on MARCH 08, 2017
Applies to:Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.
User faced error after using the xla_journal_entries_pub_pkg in a custom program.
When using xla_journal_entries_pub_pkg for creating journals, Import Journal(1) failed.
But when Import Journal(2) started next time, previous journal (that failed in Import journal(1)) gets processed fine.
xlaaptrn.pkb - g_batch_name VARCHAR2(50) should be changed VARCHAR2(80) to be almost in sync with - JE_BATCH_NAME VARCHAR2(100) from GL tables.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms