My Oracle Support Banner

Some imported Journals lost LE information and therefore an Accounting Sequence Number cannot be generated (Doc ID 2702928.1)

Last updated on AUGUST 31, 2020

Applies to:

Oracle Fusion General Ledger Cloud Service - Version 11.13.20.01.0 and later
Information in this document applies to any platform.

Symptoms

Some journals imported through the interface have lost LE, resulting in failure to generate Accounting Sequence Number.
In the same Journal batch, LE Identifier is not populated for some Journal headers while it is populated for the other Journal headers.

This problem happens intermittently by accident and cannot be reproduced at will.

The flow is that the external system will fill the data to the interface table in real time, using a webservice.

Import journal request plans to run once every 5 minutes.  

 

 

Changes

 

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


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