Error26 - Showing Insufficient Access To Ledger Or Segment Value In The Secondary Ledger. (Doc ID 2225913.1)

Last updated on JANUARY 23, 2017

Applies to:

Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

 On : 12.1.3 version, Journal posting form

When attempting to post journal to be replicated in secondary ledger, the following error occurs.

ERROR
-----------------------
Error26 - Showing insufficient access to ledger or segment value

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Responsibility: General Ledger Superuser
1. Create a journal in the primary ledger

2. Use autopost to post the batch

3. Review journal in the primary ledger . Status is posted.

4. Review journal in the secondary ledger. Journal has been created but has the status
Error26 - Showing insufficient access to ledger or segment value

5. Log file for the primary ledger posting show:

SHRD0180: glpubr() - Performing action >> autopost_sl_batches...
SHRD0026: Current system time is: 20-OCT-2016 14:37:55

SHRD0181: glpubr() - tmpbuf = CONCURRENT SQLGL GLPPOSS 2344 1244 101 97291 Y
SHRD0180: glpubr() - Performing action >> Submitting Posting in secondary ledger...
SHRD0026: Current system time is: 20-OCT-2016 14:37:56

SHRD0180: glpubr() - Performing action >> Posting spawned in secondary ledger...
SHRD0026: Current system time is: 20-OCT-2016 14:37:56

Posting manually the secondary ledger journal works fine.

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