EGL9.2: Journal Unpost Is Locking Allocation Journal.
(Doc ID 1927877.1)
Last updated on FEBRUARY 06, 2019
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
User runs an allocation with edit and post options unchecked. Subsequently, user runs batch edit/post from the Edit Journals and Post Journals pages. Entry is Posted and goes to Posted, Valid status. Afterwards, user runs the Unpost Journals process. All header rows generate a corresponding Unposted header row, and the Journal unpost sequence number on the original header rows is changed from 0 to 1 for all header rows. However, one header row from the original journal which was previously in a Posted, Valid status is changed to Valid, Valid status and the Journal entry becomes Locked. User cannot initiate the Unlock Journal process from the Monitor Background Process > Unlock Journals page. However, upon querying the PS_JRNL_HEADER table, the Journal is Locked. When trying to retrieve the Journal on the Create/Update Journals page, the user receives an error that the journal is locked.
Receive error that journal is locked.
Steps to Replicate:
1. Run Allocation with Edit and Post option unchecked.
2. Concurrently, run batch edit/post process .
3. Mark Journal for Unpost on Mark Journal for Unpost page.
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