Negative Request Id Stored in Secondary Ledger Journal
(Doc ID 2329027.1)
Last updated on FEBRUARY 23, 2019
Applies to:Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.
Secondary ledger journal submitted for posting from primary ledger journal has negative request id stored in journal batch.
Steps To Reproduce
The issue can be reproduced at will with the following steps:
1. Create journal on primary ledger.
2. Post journal.
3. Secondary ledger journal is created automatically and posted.
4. Request_id in gl_je_batches is set as negative number.
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