Bug In Milestones Process With Incorrect Prior Effective Date
(Doc ID 3015052.1)
Last updated on APRIL 10, 2024
Applies to:
PeopleSoft Enterprise CS Student Records - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
On : 9.2 version, Student Records Enrollment
When attempting to add a new milestone using the batch process once another milestone has been deleted, the old process adds the new milestone, but also puts back in the old milestone.
The record used in this SQL should be STDNT_MLSTN, not STDNT_CAR_MLSTN.
Then the process will really take the prior effective date instead of ‘the prior effective date containing at least one milestone’.
The issue can be reproduced at will with the following steps:
1. Records and Enrollment -> Student Milestones
2. Remove an existing Milestone and save
3. Run the Batch process to add a new milestone (Records and Enrollment -. Process Milestones)
4. Return to Student Milestones and note that both the old and new milestone are there
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |