EGL: How to Fix A Partially Posted Interunit Journal So The Rest Of It Can Be Posted (Doc ID 2114548.1)

Last updated on MARCH 08, 2016

Applies to:

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

Symptoms

On : 9.2 no PUM

The un-posting of an interunit journal locked it. All the journal headers with Unpost Seq 0 are in journal status 'U' for Unposted for all Interunit lines. All the journal headers with Unpost Seq 1 are in journal status 'P' for Posted, except for one journal header which is in journal status 'V' for Valid.

BU       JOURNAL_ID  UNPOST_SEQ  BUSINESS_UNIT_IU  JRNL_HDR_STATUS  JOURNAL_LOCKED
US001  0000033907         0           US001                    U         
US001  0000033907         0           US003                    U
US001  0000033907         1           US001                    V                          Y                       << note
US001  0000033907         1           US003                    P

When trying to access it online to review it, get the following 2 error messages:

"The journal is currently locked for process. Please try it later. (5010,138)"
Press OK
"The lines for some Business Units have already been posted. It cannot be modified. (5010,82)"

Tried unlocking the journal via the General Ledger / Monitor Background Process / Journal Unlock for the user who generated the journal, but that page didn't return any information. So now I have a partially-posted IU journal.

How to get the remaining journal headers to status 'P' for posted?

STEPS
-----------------------
The issue can be consistently replicated as follows:
1. Unpost an interunit journal where 1 or more of the journal headers gets locked and status V where all other headers get status P
2. Try to open the journal online and get the below messages:
"The journal is currently locked for process. Please try it later. (5010,138)"
Press OK
"The lines for some Business Units have already been posted. It cannot be modified. (5010,82)"

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