EGL 9.2: GL_YC Year End Close Processing BU That is not Included in Request When Document Sequencing is On
(Doc ID 2525850.1)
Last updated on JULY 06, 2020
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Year-End Close Message log shows other Business Units that were not included in Close Request
EXPECTED BEHAVIOR
-----------------------
Only BUs entered for processing on Close Request should be included in message log
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enable Document Sequencing - Set Up Financials/Supply Chain > Install > Installation Options
2. Turn on Doc Sequencing for BUs US001 and US005 - Set Up Financials/Supply Chain > Business Unit Related > General Ledger > General Ledger Definition
3. Run GL_YC Year End close for US001 and US005
- Message log:
Unit "US001", Ledger Group "RECORDING": Journals Posted: 2; UnPosted: 0;
Reversals Created: 0.
Unit "US005", Ledger Group "RECORDING": Journals Posted: 2; UnPosted: 0;
Reversals Created: 0.
4. Run GL_YC Year End close for US001 ONLY using same run control and parameters
- Message Log (only US001 logged):
Unit "US001", Ledger Group "RECORDING": Journals Posted: 2; UnPosted: 2;
Reversals Created: 0.
Unit "US001", Ledger Group "RECORDING": Journals Posted: 2; UnPosted: 0;
Reversals Created: 0.
5. Run GL_YC Year End close for US005 ONLY using same run control and parameters
- Message Log (both US001 & US005 are logged):
Unit "US001", Ledger Group "RECORDING": Journals Posted: 0; UnPosted: 0;
Reversals Created: 0.
Unit "US005", Ledger Group "RECORDING": Journals Posted: 2; UnPosted: 2;
Reversals Created: 0.
Refer replication document attached.
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 |