Last updated on SEPTEMBER 14, 2016
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 8.4 to 9.1 [Release 8.4 to 9]
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 200765740
***Checked for relevance on 15-Jun-2010***
***Checked for relevance on 12-Aug-2013***
Checked for relevance Dec-13-2011
Ledger Group XXXXXX is not valid for Business Unit XXX(5010,95) error.
When blank period and fiscal year is used on a business unit, the transactions errors when trying to create a new journal to a business unit/ledger group that has blank periods defined in the open period pages.
Financials transactions have the following error
Ledger Group XXXXXX is not valid for Business Unit XXX(5010,95)
The Ledger Group defined for this journal is not valid for the Business Unit. If you are adding a new journal, the invalid Ledger Group is the one defined for your UserID on the General Ledger User Preferences page.
The issue is caused by the workaround recommended for inactivating a business unit. There is not a delivered way to inactivate a business unit, but development has recommended that the periods and fiscal years be blanked out on the Open Periods Update page to make sure no new activity can be entered to the business unit.
The error message happens because Open Periods Update page is updated with the from period / from year and to period / to year are left blank. The Ledger Group is attached to the business unit, it simply does not have any open periods and it seems like the error should instead notified the user that the ledger does not have any open periods.
Additionally existing transaction can not be opened and reports can not be run (ie trial balance and gl activity report) The reports error with error: (SQR 4504) Fixed column placement #variable must be > 0. Use relative positioning, (5,+#col,0).
One other inconsistency when using blank open / closed periods is that journals are allowed to be created, and they can be saved but the amount fields are separate.dr/cr, There was no warning on journal entry page...so the user could enter the journal although they could not post the journal (the separate dr/cr amounts issue is reported in incident 664170000 and is not to be fixed)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms