Banner - How to Resolve Duplicate IDs

Overview

Duplicate IDs occur when new ID numbers are created for existing students in error. Such duplicates must be consolidated when found, so each student only has one UH ID number. Student data on the IDs must be reviewed and compared to determine which ID to use going forward (retained ID). All other IDs must be marked as Do Not Use (DNU IDs) and cleared of student data. This article provides instructions on how to identify which ID to keep, move data between IDs, clean out DNU records, and report duplicated records.

 

Determining Which ID to Keep

Some data is harder to move between student records, so determining which ID to consolidate all the student's information under (retained ID) is critical. For the smoothest consolidation, the record with the most data in the below categories should be kept. (Banner pages to help review this data are noted.)

  1. Financial aid -- Check with your campus financial aid office; if aid has already been paid, it will show up in TSAAREV (Aid Year column)
  2. Academic history -- SHACRSE
  3. Accounts receivable -- TSAAREV 
  4. Current enrollment -- SGASTDN
  5. UH username, student details, and/or admissions data -- SGASTDN/SAAADMS

To help with the review process:

  1. Open two sessions of Banner to review data side by side. Different browsers or private/incognito mode should be used to open more than one Banner session at a time.
  2. Run GUASYST to see the general areas of data on the IDs.
    Screenshot of GUASYST page
     

Back to Top

 

Moving Data and Cleaning Records

GUASYST can be used to help narrow down which Banner pages should be reviewed for the record to be discarded (DNU ID). If the ID to be retained does not have the same data as the DNU ID, data must first be copied over to the retained ID before deleting. Click the items below for a list of screens related to GUASYST categories, additional instructions, and/or troubleshooting issues while transferring data between IDs.

 

Admissions

  • SHATRNS
  • SGASTDN -- If moving a username, delete only after the username has been moved. Deleting the SGASTDN record if the username is active will trigger the deprovisioning process. Please note the need to move the username when reporting cleaned records.
    • When deleting from DNU ID:
      • If you receive the following *ERROR* Cannot delete student record Attribute records exist:
        • Go to SGASADD.
        • Enter the ID and Term related to the SGASTDN record to be deleted.
        • Click into the Student Attribute - Attribute Code.
          If you can’t click into it, restart the process using the term noted in the From Term box.
          Screenshot of SGASASS screen with student attribute attribute code highlighted
        • Click Delete.
        • Click OK to clear the warning alert that changing student attribute values may impact Registration Fee Assessment.
        • Save.
      • If you receive the following *ERROR* Cannot delete student record academic history records exist:
        • Double check that all academic history pages were cleared out, especially SHAINST.
        • Double check that SGASADD is also clear (see above).
           
  • SGAADVR
    If advisors have been assigned to the DNU ID, a message will display when attempting to delete the SGASTDN record.
  • SIAINST
  • SSASECT
  • SPAIDEN
    • When copying to retained ID
      • Campus must determine which name to use following their policies if record names differ. Any names on the DNU ID will be cleared out, so the different name(s) should be documented in some form.
        • If the campus has name change documentation (as required by the campus), update the name in SPAIDEN on the Kept ID.
        • If the campus does not yet have name change documentation either: 
          • Add the name from the DNU to Alternative Identification as Name Type: P (Previous/Other); or
          • Add a SPACMNT entry, Comment Type: 100 (General Comment) to document the different name.
             
    • When deleting from DNU ID
    • Rename record using the following format:
      Last Name: DO NOT USE
      First Name: SEE 22222222 (where 22222222 is the correct ID)
      Middle name: RTD
      Note: The record name should be changed first as it generates another entry in the Alternative Identification tab.
       
    • Delete all entries in each tab, including Alternative Identification.
    • If unable to delete data from the Biographical tab due to a financial aid record, clear each field individually (tab into each field and delete the data) via SPAPERS
    • If an UH email is type as OTHR and not CAMP on the duplicate ID and the retained ID has the same UH email as CAMP, it is okay to delete the OTHR email from the duplicate ID.
       
  • SOAFOLK

Campus Business Offices will need to be involved in moving data. Payment records should be left on the original ID and not deleted.  

  • TSAAREV
    • This is a “manual change”. Moved AR records will say "moved from [old UH ID#]" (as opposed to “Web credit card payment”, etc.) when the student tries to view their Payment History.
  • TFADETL

Campus Financial Aid offices will need to be involved in moving data. This should generally be done as one of the last steps as parts of SPAIDEN/SPAPERS need to be cleared first.

If there is any financial aid data needed to be kept on the DNU ID, create a RHACOMM comment on the kept ID referencing the DNU ID. 

Back to Top

 

Transferring Usernames

Students with two UH IDs and usernames may prefer one username over another. If a username needs to be moved from the UH ID to be discarded (DNU ID), either a SAAADMS or SGASTDN record must be kept on the UH ID temporarily. This keeps the username “live”. The DNU ID cannot be marked DO NOT USE until after the username has been moved.

Back to Top

 

Reporting Cleaned Records

UH IDs are used for many UH systems, not just Banner. Once records have been marked as Do Not Use, they must be reported to ensure the student's ID number in synced across systems. Before reporting duplicate records: 

  1. Double check the record(s) to be discarded (DNU ID) are marked Do Not Use, unless a username move is needed; and
  2. All SPAIDEN information has been removed, especially the Alternative Identity tab. 

The naming convention on SPAIDEN should be:

Last Name: DO NOT USE
First Name: SEE 22222222 (where 22222222 is the correct ID)
Middle name: RTD

Form to report duplicate IDs using this form (link)
If a reporter is unsure of anything regarding the duplicate IDs, please add it to the Notes section of the form.

 

Back to Top

 

Print Article

Related Articles (2)

How to delete Electronic Data Exchange (EDE) records from student's records to prevent incorrect Common Origination and Disbursement (COD) system processing and reporting.
This article provides instructions on how to resolve various issues that could cause an individual's record to get stuck as an @ID.

Related Services / Offerings (1)

Request to resolve duplicate banner records