Spike analysis: EOR update without validations

Requirement: CMD1-4446 -BBU for EORI update Done

Validations:

Test Scenarios/validations applies.	Sub scenarios
Workflow pending customers are not allowed.
Customer Status	Active customer is allowed for updates.Suspended customers are not allowed.Inactive customers are not allowed.
Country check Russia and Belarus customers not allowed for updates.
Reference Type validation	Type code checkValue format check as per country rulesMandatory validation. Example If via BBU user is trying to remove a EOR for customer but for customer's country EOR is mandatory. Error message should be thrown.
External System identifiers	As external system identifier is the unique identifier in the downstream systems, validation will still be needed.
Test Scenarios/validations Skipped.	Sub scenarios.
Customer's Other data validations	City, region (Customer address rules)Tax details.Communication detailsMandatory field validations as per Country rulesSCPI Rules validationsBrands

Is it Possible to use existing BBU Customer Tax Template?

• Yes, it's possible to use existing BBU customer tax template by making minor modifications to code.
• Vinesh Asokan , Ajit Vijay Daware Please confirm whether to use existing tax template.

Publishing customers with invalid data to EMP

Jira ID: CMD1-4506 -Publish customers with invalid customer records and check the impact in downstream applications Done