My Oracle Support Banner

Using Xla_journal_entries_pub_pkg g_batch_name VARCHAR2(50) unsync JE_BATCH_NAME VARCHAR2(100) (Doc ID 2083203.1)

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.

Symptoms

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.


Changes

 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.

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
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.