CCCStart Application Processing — Technical Staff

Summary

Provides technical staff with an overview of how CCCStart applications are received, staged, matched, validated, and processed into Banner, including program and curriculum processing, student type and residency assignment, and troubleshooting guidance.

Body

Overview

This knowledge base article provides a technical overview of how CCCStart applications enter the IVC integration, move through staging and identity matching, are validated, and are ultimately written to Banner. It also identifies the primary objects involved and the key areas to review when troubleshooting processing errors.

End-to-End Flow

  1. CCCStart sends the application payload to the integration/Tech Center feed.
  2. The payload is loaded into SZRAPLY. The loader/procedure evaluates fraud and duplicate controls and maps accepted application data into SZRCCAP.
  3. IVC_CCCAPPLY_TO_SZRCCAP normalizes and stages identity, application, contact, academic, program, and term data.
  4. IVC_SZRCCAP_PROCESS validates the staged row and creates or updates Banner person, admissions, student, curriculum, and supporting records through Banner APIs.
  5. Processing results and Oracle error fields are recorded so technical staff can review failures and replay applications when appropriate.

Identity Matching

  • Existing Banner ID/PIDM, when supplied and verified
  • CCCID
  • Normalized nine-digit SSN
  • Name + date of birth
  • Name + date of birth + email

Important: Ambiguous or conflicting matches must stop for manual review. The process should not make an arbitrary PIDM selection.

Program and Curriculum

Hyphenated CCCStart values normally represent Banner PROGRAM codes. Legacy non-hyphenated majors are resolved by IVC_CCC_START_MAJOR using EDU_GOAL and live SOBCURR/SORCMJR/SORMCRL/SMRPRLE configuration. The materialized-view cursor is intentionally retained as a future performance option.

SZRCCAP_PROGRAM / SZRCCAP_MAJR_CODE_1
 → program_cursor_18
 → v_program, v_degc, v_dept, v_curr_rule, v_cmjr_rule
 → SB_CURRICULUM.P_CREATE (SORLCUR)
 → SB_FIELDOFSTUDY.P_CREATE (SORLFOS)
  • Current degree mapping is SOBCURR_DEGC_CODE → v_degc → p_degc_code.
  • All 98 CCCStart programs must exist and validate.
  • Noncredit programs may only use approved noncredit terms such as 202712; curriculum build is otherwise the same.

Student Type

Uploaded image

Residency

Uploaded image

Data No Longer Collected

  • Emergency contact processing is skipped; existing Banner contacts are not cleared.
  • Legacy residency-detail questions no longer drive residency.
  • Many service-interest and supplemental fields remain null and should not be interpreted as No.
  • Visa and optional contact processing runs only when meaningful data is present.

Primary Objects

Uploaded image

Support and Troubleshooting

  • Check application ID/confirmation, CCCID, term, program, fraud flag, and SZRCCAP Oracle error fields.
  • Validate term in STVTERM and program in active curriculum.
  • Review identity conflicts before creating a new person.
  • Do not manually default missing residency to nonresident.
  • For curriculum errors, verify program, degree, level, college, rule, and Major+Term/noncredit compatibility.

Details

Details

Article ID: 172777
Created
Tue 9/1/26 3:11 PM
Modified
Tue 9/1/26 3:34 PM