Provide Functionality To Allow Per Unit Setup In Third Party Contracts
(Doc ID 2642207.1)
Last updated on FEBRUARY 24, 2020
Applies to:PeopleSoft Enterprise CS Student Financials - Version 9.2 and later
Information in this document applies to any platform.
DESCRIPTION OF SUGGESTED ENHANCEMENT:
REASON CURRENT PRODUCT FUNCTIONALITY IS INSUFFICIENT
There is a trend where third party sponsors are willing to pay a set dollar amount per credit hour. Delivered third party contract set up does not allow for this.
DETAILED DESCRIPTION OF THE ENHANCEMENT REQUEST
One method to handle this automatically, would be to add a field at the contract or student level, setting the per unit rate that the sponsor wishes to pay.
HOW THE PRODUCT CAN BE CHANGED TO ACHIEVE THE DESIRED RESULT
Add a field at the contract or student level setting the per unit rate that the sponsor wishes to pay. The system would then adjust the credit to be equal to the rate x billing units, up to the student max. There should probably be a check box to include wait-listed hours, so that schools can match their tuition policies.
BUSINESS IMPACT IF THE ENHANCEMENT IS NOT CONSIDERED
The accounts of approximately 20% of our third-party-sponsored students must be babysat throughout the term, watching for drop/add activity. We have heard rumors that this could expand to ROTC populations, which would drastically increase this ratio.
DESCRIPTION OF THE BUSINESS FLOW THAT IS AFFECTED BY THIS ENHANCEMENT
The existing 3rd Party Contract process would use this enhancement. Overall business impact would be minimal as this would provide an alternative configuration that would not be required.
REASONS TO CONSIDER THE ENHANCEMENT REQUEST
This is a growing trend in the industry for sponsored (3rd Party) students. Having this functionality would help schools cut down on a large amount of manual intervention on sponsored accounts.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document