EGL: Orphaned Lines On KK_ACTIVITY_LOG Can Occur After Budget Checking (FS_BP) Journals To More Than One GL BU (Doc ID 2032459.1)

Last updated on SEPTEMBER 29, 2015

Applies to:

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

Symptoms

On : 9.1 bundle #34 or 9.2 prior to PUM Image 15, KK-Budget Checking

Orphaned lines are left on KK_ACTIVITY_LOG and LEDGER_KK.

A journal is created with multiple business units on the lines.  This journal is edited and valid.  The journal is sent for approval.  The approver changes a line business unit and re edits and re budget checks.  

The original rows remain on KK_ACTIVITY_LOG, KK_SOURCE_HDR, LEDGER_KK.


Two Test Scenarios
-----------------------
Scenario (A)
journal header - US005
journal lines - US005 / US006 >> change to US005 / US005 --> results in incorrect KK Activity Log row for US006

Scenario (B)
journal header - US005
journal lines - US007 / US006 >> change to US005 / US006 --> results in incorrect KK Activity Log row for US007

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