Termination V3 – Reverse Termination on Inactive Assignment Causing Multiple Primary Assignments

Summary:

We are currently implementing the Termination V3 process and have identified a scenario that appears to create data corruption related to the Primary Assignment flag.

As per system design, only one Primary Assignment should exist per Work Relationship at any given point in time. However, during our testing, we observed a situation where multiple assignments are marked as Primary, which should not be possible.

Scenario Details

Current State

• Assignment 6032XX-8
  • Status: Active
  • Primary: Yes
  • Effective: 01-OCT-2025 to EOT
• Assignment 6032XX-6
  • Status: Primary until 30-SEP-2025
  • Status from 01-OCT-2025: Inactive
  • Primary: No (post 01-OCT-2025)

Action Performed

• Executed Reverse Termination on