Skip Customer validation while suspending customer

Epic link: CMD1-4242 -CMD validation on customer suspension To Do

Duplicate Suspension

1. Suspending customer with Duplicate reason, MASTER_DUPLCIATE relationship should be assigned between Parent and child customer via Assign relationships API.
2. Now While Suspending customer for Duplicate reason, Customer’s entire data validation(s) (address, Phone number, Tax, SCI, Brands etc.) won’t get Triggered. Hence there is no need to skip any validations.
3. Validations present in assigning Master duplicate relationship are:
   1. Customer Status check
   2. Workflow check
   3. Russia and Belarus check
   4. relationship eligibility check
   5. source system check

NMB Suspension

1. NMB Suspension is done via NMB-Endpoint dedicated where only SAP source system is allowed.
2. Validations in NMB suspension are:
   1. Source system check
   2. Customer status check
   3. Russian and Belarus status check
   4. Workflow check
   5. etc. (Not any Customer data validations)
3. NMB Suspension also, doesn't have any Customer’s entire data validation(s) (address, Phone number, Tax, SCI, Brands, etc.) won’t get Triggered. Hence there is no need to skip any validations.

Conclusion on Duplicate and NMB suspension:

• In both the suspensions there as there is no Customer Data validations present, hence there is no Impact on these, Behavior of these suspensions will remain same and untouched.

Advantages:

1. On Suspending customer without validation, doesn't enforce to add missing mandatory details/Invalid details, hence user can go and suspend the customer.
2. Less Request Tickets, requesting for suspending customer or updating customer details.

Risk Factors:

1. On Suspending customer without validation, doesn't enforce to add missing mandatory details, hence customer will still have invalid details like
   1. City
   2. Tax number
   3. Phone number
   4. Missing mandatory details
2. On Publishing such suspended customers to downstream systems might cause issues at their end

[V] Yashwanth Kurru (Deactivated) I have created an epic for the clean-up and testing with downstream systems prior to releasing the feature. CMD1-4439 -Clean-up of active customers To Do

Functional Queries:

1. Is Russia and Belarus customer allowed for suspension? [V] Russia and Belarus customers are already suspended.

Low Level Considerations:

1. customer payload without validation might cause data constraint violation issues while saving to database.
2. Database constraint should be verified, below fields of customer has foreign key constraints.
   1. source_of_last_update, source_of_create
   2. customer_group_type
   3. account_group_type
   4. customer_status_cd
   5. isd_country_code, isd_dialing_code
3. Customer Status reasons should be verified before saving to database.

Compulsory validations on customer, irrespective of skipping data validations.

1. Workflow check: Workflow pending customer won’t be allowed for any updates.
2. RU and Belarus customer won’t be still allowed for udpates
3. Country check
4. Source system and user check
5. Customer Status reasons check: Checking whether correct reason name is provided or not, Important to avoid breaking the existing persisting logics.
6. External System identifiers check: Check to prevent any illegal updates on external identifiers.