ODS / Release Guide / 3.1

Section 4 Problem Resolutions
Accounts Receivable
Section 4
Problem Resolutions
This section contains the impact and resolution for all defects included in this
release. Defects and their resolutions can also be accessed through the Customer
Support Center.
Accounts Receivable
1-1D02G9
Impact
The AN_PAYROLL_DISTRIBUTION composite view on the Banner side errors if
Banner Finance is not installed. There is a call to a Banner Finance delivered
function that errors because the function has not been installed on the Banner side.
Resolution
The call to build dynamic sql from the TOKODSF package was removed into the
GOKODSF package so that it can be used by all product scripts. Also added the
F_GET_FINANCE_DESC and F_GET_FINANCE_STATUS functions into
FOKODSF. There were some tables missing that retrieve descriptions and statuses
for the ODS.
1-THYQI
Impact
If neither the Name nor Address were entered into Banner 4x through 6x, the
TBBMISC record was not created by the TFA/TSAMISC forms. Thus, an outer join
is needed between the two records to accommodate old Banner data. Otherwise all
miscellaneous charges will not be pulled into the
AT_MISCELLANEOUS_TRANSACTION view.
Resolution
An outer join was added to TBBMISC_RECEIPT_NUMBER so that if there was no
corresponding record in TBBMISC, the TBRMISD record would still be returned.
Administrative User Interface
1-13CPZA
Impact
Because a comma was being used to delimit the parameter stream for a Job, if a
WHERE clause for a Single Freeze table job contained a comma-delimited list (like
using the IN operator for example), the parameter string was not interpreted
April 2007 Operational Data Store Release 3.1
Confidential Release Guide 27