Resolving Basket Submission Errors Caused by NOCHANGE Configuration Mismatches

Symptom

When submitting a basket (SOF), an error occurs related to NOCHANGE configurations having incorrect MRR (Monthly Recurring Revenue) delta values. Configurations marked as NOCHANGE should have a $0.00 MRR delta, but they show non-zero values indicating a mismatch between original and new MRR.

Cause

NOCHANGE configurations develop MRR delta mismatches, causing the submission validation to fail. This can occur when configuration values are inadvertently modified or when pricing recalculations alter values on configurations that should remain unchanged.

Resolution

Step 1: Close All Deal Management and Solution Console Sessions

Navigate to Deal Management and close it. This releases any locks on the basket/solution.

Step 2: Reopen the Solution and Reset NOCHANGE Configurations

Open the Solution Console for the affected solution. For each configuration marked as "NOCHANGE":

• Verify the original MRR matches the new MRR
• Reset any pricing or quantity changes
• Ensure the configuration status is correctly set to NOCHANGE

Step 3: Quick Save

Click "Quick Save" (do NOT submit yet). This persists changes and triggers re-pricing/validation. Check the basket summary to confirm MRR Delta values show $0.00 for all NOCHANGE items.

Step 4: Retry SOF Submission

Attempt to submit the SOF again. Verify the MRR deltas now show $0.00 for NOCHANGE items.

Why NOCHANGE Configs Get Modified

During basket submission, the change management engine validates configurations based on their change type. Configurations marked as NOCHANGE are expected to have zero MRR delta (i.e., original MRR equals new MRR). The validation compares cscfga__Recurring_Charge__c values between the original and current configuration.

NOCHANGE configurations can be inadvertently modified by re-pricing triggers, open Solution Console sessions that update values, or recalculation cycles. The Quick Save step forces re-validation through the Configurator Service without submitting the basket, allowing mismatched values to be corrected before submission.

Additional Notes

• Always close other DM/Solution Console sessions before attempting to fix, as open sessions can hold locks
• If the issue recurs frequently, investigate whether custom pricing logic or triggers are inadvertently modifying NOCHANGE configurations
• The same pattern applies to any change order basket where existing configurations show unexpected delta values