My Oracle Support Banner

HESA Statutory - COMDATE Calculating Incorrectly When It's Value Is "today" (Doc ID 2663205.1)

Last updated on APRIL 24, 2020

Applies to:

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

Symptoms

On Campus Solutions 9.0 Bundle 47, When the HESA Create Extract Process (SSR_HE_DATA) is run, and the COMDATE (or Start Date of Instance) is today's date, then the COMDATE is set to the effective date of the HESA Instance.
i.e. ps_ssr_he_instance.ssr_he_comdate is set to ps_ssr_he_instance.effdt_when ssr_he_comdate is the same as the date the process is run.

The %coalesce function returns the first none Null value in the preceding set of defined fields, in this case COMDATE and “Today’s Date”. It then compares the value it has found to Today’s Date and if there is a match, it updates the COMDATE with the Effective Date of the HESA Instance. If the value doesn’t equal Today’s Date then nothing happens.

It is expected the process will always complete.

The issue can be reproduced at will with the following steps:

  1. Run the HESA Return process.



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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.