Skip to main content

CALPADS error brief · SPRG

SPRG0070

Overlapping Program Records
Severity Fatal
Error type Input Validation
Record type SPRG

Official CALPADS rule

What CALPADS is rejecting

SSID has an existing/matching overlapping Education Program record existing in Staging or ODS

Focus fields

Fields validated

3.05 - School of Attendance 3.13 - Education Program Code 3.15 - Education Program Membership Start Date 3.16 - Education Program Membership End Date 3.17 - Education Service Academic Year 3.18 - Education Service Code

Recommended correction path

Suggested resolution

How CALPADS identifies the conflict

  • 3.05 School of Attendance
  • 3.13 Education Program Code
  • 3.15 Membership Start Date
  • 3.16 Membership End Date
  • 3.17 Service Academic Year
  • 3.18 Education Service Code

For programs other than 122, the conflict centers on student, school, program, and overlapping membership dates. For Title I Part A Basic Targeted 122, Service Academic Year and Service Code also distinguish the record.

Do not shorten dates until you know whether there are two facts or one duplicate. The existing record may be hidden by access restrictions, especially NSLP records that require the Free/Reduced Lunch role.

Where to search

Current fileDuplicates and same-batch overlaps
StagingUnposted submission records
ODSPreviously posted history
Restricted viewsNSLP records may require role

Overlap examples

ExistingSubmittedInterpretation
08/12–12/2012/01–openOverlap from 12/01 through 12/20.
08/12–open01/10–openSecond open segment begins inside the first.
08/12–12/2012/21–openAdjacent, not overlapping, if both events are supported.

Recommended correction path

  1. 1

    Preserve the submitted segment

    Capture full key, dates, transaction, and submission ID.

  2. 2

    Find every matching record

    Search file, Staging, ODS, and restricted NSLP view when applicable.

  3. 3

    Reconstruct the program history

    Decide whether this is a duplicate, continuation, correction, or truly separate segment.

  4. 4

    Correct the appropriate key/dates

    Remove duplicate generation, close the supported prior segment, or replace an incorrect Start Date safely.

  5. 5

    Verify and broaden

    Confirm no overlap remains and audit the affected program population.

Official SPRG0070 page