Cashiering GL Interface Ignores Business Unit
Last updated on JULY 11, 2016
Applies to:PeopleSoft Enterprise CS Student Financials - Version 9 and later
Information in this document applies to any platform.
On CS 9, The Cashiering GL Interface process produces incorrect results.
Your institution has multiple associated Business Units and each have their own Cashiering Target Keys with different effective dates. All Business Unit have the same name for the Target Key. When the Cashiering GL Interface process is run the incorrect transaction set is processed because only the max effective date is used.
Business Unit 1 has Targey Key CASHALL with eff date of 01/01/1901
Business Unit 2 has Target Key CASHALL with eff date of 01/01/2001
When the Cashiering GL Interface is run the target Key for Business Unit 2 is used with transaction for Business Unit 1.
It is expected the Target Key for the specific entity is used.
The issue can be reproduced at will with the following steps:
- setup Tarket Ket details for Business Unit 1
- setup Tarket Key details for Business Unit 2
- run the Cashiering GL Interface process
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