Deposit Fee Pymnt Does Not Update App Status When There is Prior Unpaid App (Doc ID 623001.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 200770406



Checked for currency July 16, 2010.


Symptoms

Deposit Fee Pymnt Does Not Update App Status When There is Prior Unpaid App


The posting program is not updating the correct ADM_APPL_DEP row, and subsequently not updating the application status when a row exists in ADM_APPL_DEP for a prior term that has not been paid.  When a student has applied to a program for a prior term and the deposit fee was assessed for this prior term but not paid, and the student applies to the current admit term, is admitted and a deposit fee for the current term assessed, payment of the current admit term record is updating the wrong ADM_APPL_DEP row.   The unpaid row from the prior application is selected.  If the status on the application from that prior term align with the deposit fee setup the old term could potentially be set to a new status.

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