Student Records Run Controls - for Example for Graduation Processing and Process Milestones - Populate Wrong Values from Another User, a Result of Maintaining a Single Row per Unique Run Control ID (RUN_CNTL_ID) Shared Between Every User ID (OPRID) (Doc ID 2884870.1)

Last updated on MARCH 01, 2024

Applies to:

Symptoms

When running certain Student Records processes, only one version of any single run control id is available for all users who may run the process. An example process is Graduation Processing, SSR_GRAD_RPT, and the run control page SSR_RUNCTL_GRADRPT. The SSR_RC_GRADRPT and SCCPS_RUN_PARM records, behind the page, are only saved in the DB for one OPRID at a time.

Another example is Process Milestones.

It's expected that different users should be able to create and use the same run control id. Maintaining more than one row with the same run control id is permitted by the record structure which has both OPRID and RUN_CNTL_ID as key fields.

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

1. Navigate to Records and Enrollment > Graduation > Graduation Processing.
2. Add a new run control id, populate the parameters, and save the component.
3. Have a different user sign in and take the same steps. The 2nd user may see the 1st user's values already populated. If the run control id already displays in the search list, choose the existing id rather than trying to create a new one.
4. Make any changes to the component and save.
5. Query SSR_RC_GRADRPT and SCCPS_RUN_PARM and note there is only 1 row for the run control id, with the oprid that last updated the record.

Cause

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