Cashiering GL Interface Ignores Business Unit (Doc ID 1489227.1)

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.

Symptoms

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.

For example:
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.

EXPECTED BEHAVIOR
-----------------------
It is expected the Target Key for the specific entity is used.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. setup Tarket Ket details for Business Unit 1
  2. setup Tarket Key details for Business Unit 2
  3. run the Cashiering GL Interface process

Cause

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