WebADI Journal Templates Using Reverse Journal = No or Blank (Null) Fail Upload Validation With 'Balance checking has failed to identify the Journal on the current line'
(Doc ID 2949323.1)
Last updated on OCTOBER 10, 2023
Applies to:Oracle General Ledger - Version 12.2 and later
Oracle Web Applications Desktop Integrator - Version 12.2 and later
Information in this document applies to any platform.
After applying patch 32926671 non-reversal journals (using journal template parameter 'Reverse Journal' = No or Blank (Null)) fail validation and will not successfully upload unless the reversal period is populated.
The following error is seen in the Messages column of each journal line in the Excel template when this occurs:
This error is seen with the parameter settings: Reverse Journal=No or Blank (Null) and blank (null) Reversal Period/Date.
If the Reversal Journal parameter is set to Yes and the Reversal Period/Date is populated there is no issue seen with the upload.
Steps to recreate this issue:
1) Using a General Ledger responsibility, navigate using Journals -> Journal Wizard and create a journal template with Reversal Journal and Reversal Period/Date parameters included in the layout.
2) Populate the Reversal Journal parameter with No or leave it blank (null). Do not populate the reversal period, leave it blank (null).
3) Populate the balance of the journal data and submit the journal for upload.
4) The upload fails with the following validation error in an Excel dialog box:
The upload process has completed with the following status:
# row(s) failed validation and 0 row(s) successfully uploaded.
In the template each line has a red frown face with the following error repeated for each line:
'Balance checking has failed to identify the Journal on the current line'.
Setting profile BNE: Enable OOXML Standard set to No this issue is not seen.
Also by populating the Reversal Period value, even with Reverse Journal set to No will allow the journal to be uploaded.
Patch 32926671 was applied, prior to this this functionality was working as expected.
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