Customer Relationship assignment

Description

Currently in CMD a customer can be assigned with three different types of relationships

1. Concern relationship
2. CBU relationship
3. Master duplicate relationship

Concern relationship

1. Concern relationship is the process of tagging the customer under a single active concern group as either IS_CONCRN (parent customer) or CONCRN_MEM (child customer).
2. The relationship could be linkable and de-linkable
3. Please go through this doc (click here) to understand more about concern functionality

CBU relationship

1. CBU refers to collection business unit. A CBU is specific geographic business locations of MAERSK where customer is mapped for business transactions.
2. In order to map a customer to a CBU, A relationship needs to be assigned between both of them using this API
3. This relationship could be linkable and de-linkable

Master duplicate relationship

1. If a customer is found duplicate of another customer. we can suspend the duplicate customer by creating a master duplicate relationship.
2. By creating a master duplicate relationship, the duplicate customer will be suspended with Duplicate reason.
3. In case of customer reactivation is required, customer will be sent workflow, once the workflow is approved then master duplicate relationship will be removed

Schema: API Specification contract

Validations

General Validation

1. Both child customer and parent customer should have active customer status and shouldn't pending in workflow
2. Country shouldn’t be restricted list. Current Russia and Belarus are business restricted countries, so no transactions are allowed on these country’s customers.
3. Request should come from valid Source system. Input source system name is validated against the accepted sources system names list maintained by CMD reference data.
4. Input request should have valid relationship type name. This will also be validated against list of acceptable names mantained in CMD reference data

Concern specific validation:

1. Can not assign multiple IS_CONCRN relations to same concern group (when passing in same request)
2. IS_CONCRN is active member of another concern group
3. CONCRN_MEM is active member of another concern group
4. Updates on relationship are not allowed for this concern since there is at least 1 child customer that is pending workflow approval.

CBU specific validations:

1. Valid CBU ID
2. LCL_CBU and Customer should be of same country
3. Relationship already exists btw CBU ID and customer

Master duplicate specific validations:

1. Valid parent and valid child – active state - linking
2. Delinking - child customer – suspended state – Master-dup

Flow Chart