My Oracle Support Banner

EGL 9.2: GL_YC Year End Close Re-run or Undo Runs Commitment Control and Does not Clear 999 Entries and May Cause Performance Issues (Doc ID 2480716.1)

Last updated on AUGUST 27, 2020

Applies to:

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


Year-End Close re-run or Undo triggers Commitment Control and does not remove period 999 entries

Commitment Control should be skipped when running YE Close process. Undo or re-run should clear period 999 and Period 0 entries created by previous run.

The issue can be reproduced at will with the following steps:
1. Enable Commitment Control (KK) for GL on Installation Options
2. Turn on KK on Ledgers for a Unit for desired BU/Ledger Group
3. Create Budget Journal(s) for related period (say, 2018)
4. Enter GL Journal(s) that would exceed the budget
5. Override the budget and Post the GL journal(s)
6. Run GL_YC YE Close for related BU/Ledger Group for year 2018
  - Year 2018 period 999 and 2019 period 0 ledger and journal entries are created
7. Request Close Undo or re-run Close for same parameters

  - Message log includes below:
    "Commitment Control Budget Processing has begun"
    "Request Statistics. Documents Processed 2; Errors 1, Warnings 1" (numbers maybe different)
    "Commitment Control Budget Processing Complete"

  - Previous closing journal entries are removed and period 0 ledger entries cleared, but period 999 entries were not cleared from the ledger

Refer attached replication steps


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.