EGL9.2.Journal Cannot Be Posted After Approving It If Nonanchor BU Does Not Have Same Source Set Id As Anchor BU
(Doc ID 2897747.1)
Last updated on SEPTEMBER 23, 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
When having a journal source that differs from BU anchor to Bu non-anchor and creating an interunit journal , journal cannot be posted after approving the journal.
The issue can be reproduced at will with the following steps:
1.Go to Set Up Financials/Supply Chain- Install-Installation options-General Ledger and :
uncheck= Automatically approve non anchor Bu Journals
check= Validate Journal Source in Journal Copy
check= Generate IU LInes for Non-zero Balanced Lines
2.Set Anchor BU set id for source is SHARE: Tableset control for US001 FS_11 Sources=SHARE.
Non anchor BU US004 has a different set id for source FS_11=US004.Navigation:PeopleTools >Utilities >Administration > Maintain TableSet Controls
3.Source ONL only exists in SHARE set Id but not in US004 set id.Navigation :Set Up Financials/Supply Chain > Common Definitions > Journals > Define Journal Source.
4.Try adding an IU journal for with BU US001 as anchor and BU US004 as non anchor.
4.Edit the journal and then click on ‘Return to Search’.
5.Open the journal from search page again. For non anchor Approval check Active becomes NULL.
6.Submit the journal approval.
7.Check JRNL_PROCESS_REQST flag from record PS_JRNL_HEADER. For non anchor BU US004 it always remains as ‘N’.
8.Log in as approver and approve the journal.
9.After approval check Process request flag.
10.It can never post the Journal as None of the Business units are going to process request ‘P’ (Postable) status.
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 |