Transaction Wash Uses Non Graded Component In Wash Logic (Doc ID 623083.1)

Last updated on JUNE 02, 2017

Applies to:

PeopleSoft Enterprise CS Student Financials - Version 8.9 and later
Information in this document applies to any platform.

This document was previously published as Customer Connection Solution 200770968



Checked for currency August 18, 2010.


Symptoms

Transaction Wash Uses Non Graded Component In Wash Logic

If the courses added or dropped have multiple components only the graded component has billing units greater than zero associated with it.  The wash process orders the adds and drops by these class order numbers regardless of whether or not there are billing units associated with the individual class number.  The first drop may be a non-graded component whose class number would have zero billing units associated to it.  The process will then attempt to wash the non-graded component with the first add it encounters on that same day.  It is therefore possible that a zero units component will try and wash with a single component add of 3 credits.  This washes the zero for the three credits, which does not accomplish a true transactional wash.  It then takes the first drops next component, which is the graded component with billing units attached, and tries to wash its three credits with the next added component it finds in the added course list for that day.  Not finding any other activity there is nothing for the graded component class to wash with.  What this means in reality is that it did not transactionally wash anything.

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