My Oracle Support Banner

EGL9.2:Elimination Audit Report (GLS2005) GLS Not Capturing Duplicate Lines. (Doc ID 2894426.1)

Last updated on SEPTEMBER 12, 2022

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Consolidation (GLPOCONS) process was run and got error about duplicated elimination lines:

   'Duplicate Elimination Lines caused SQL error.
    Please process 'Elimination Set Audit' report first.
    No elimination identified for this Consolidation request
    Consolidation ended.  Request Completed: 0 Successfully, 1 Errors.'

However, when Elimination Audit Report was run, it appeared that it did not capture the duplicate lines in Elimination Set.  
It was only found out user manually checks the Elimination Set and saw the duplicate lines in it.  Had it pick it up, it had been corrected and Consolidation process return no error.

Steps to replicate:

Setup:

Elimination Set = EffDt: 04/01/2022
Consolidation Set = EffDt: 01/01/2021
GLS2005 As-Of Date = 04/01/2022

1.  Define Elimination Set = TEST2
    In the Elimination Lines, enter duplicate Values to Eliminate.
      Line #1:  Account = 5835
                Business Unit = US101
      Line #2:  Account = 5835
                Business Unit = US101
    (General Ledger > Consolidate Financial Data > Consolidation > Define Elimination Set)

2.  Define Consolidation Set = TESTCS1
    (General Ledger > Consolidate Financial Data > Consolidation > Define Consolidation Set)
    
3.  Print Elimination Audit Report defining the Consolidation Set = TESTCS
    (General Ledger > Consolidate Financial Data > Reports > Print Elimination Audit Report)
    Run Status = Success    
    Elimination Set TEST is shown in the report but not TEST2.
    Report should capture the duplicates for Elimination set TEST2.

See replication here.

NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample (based up made up data used in the Product name test environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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.