My Oracle Support Banner

Journal In Secondary Ledger Erroring With Status " Error - Invalid or no journal lines" (Doc ID 2228227.1)

Last updated on MARCH 30, 2020

Applies to:

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

Symptoms

On : 11.1.11.1.0 version, Post Journal Entries

When attempting to Post a some Journal Batches in the secondary ledger (done automatically based in mapping settings between Primary and Secondary ledger), the following error occurs.

ERROR
-----------------------
- The journal batch for the secondary ledger shows batch status: Error - Invalid or no journal lines
- The posting log for the Secondary Ledger shows :
>> glperp() 09-JAN-2017 17:16:26
SHRD0181: glperp() - num_of_batches_in_error = 1.
SHRD0181: glperp() - batch_name = XXXX (The XXXX will show the particular customer's batch name).
SHRD0181: glperp() - err_str = Invalid journal entry lines.
SHRD0001: Error in afpoget() - trying to read MAX_PAGE_LENGTH

PROFILES-CANNOT READ (OPTION=MAX_PAGE_LENGTH)
SHRD0181: glperp() - batch_name = XXXX (The XXXX will show the particular customer's batch name).
SHRD0181: glperp() - hdr_name = JE to re-class unpaid items out of prepaid and YYYY Reversals . (The YYYY will show the particular customer's data).
SHRD0181: glperp() - err_str = Invalid entry.


STEPS
-----------------------
Originally the customer stated that the issue could not be reproduced at will , since the posting and mapping between the Primary and secondary ledger has worked perfectly fine for over a 1.6 years and this issue happened just with just one journal batch. Multiple other journals were posted the very same day that the particular batch failed.

After development analyze the customer's settings, it was detected that the user have reversal method set for the journal category as "NEXT PERIOD" and the next period for the specific journals that were failing was an adjustment period and it was closed.

1. Set Reversal Method for the journal category as "NEXT PERIOD".

2. Have the next period to be an Adjustment period and have it closed.

3. Post a Journal in the Primary Ledger that is supposed to be mirrored in the Secondary Ledger.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot close the period, since this Journals cannot be posted in the secondary ledger.



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
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.