SUBV MVP 2.0 Solution design

Requirement: CMD1-4994 -Sub Vertical MVP 2.0 Done

Index:

• VERT & SUBV mapping is representation in database level.
• VERT & SUBV mapping in reference data service API level.
• Backend logic
• portal view

VERT & SUBV mapping is representation in database level.

• A New table is created in MDM_SMDS schema to hold the mapping.
• Table name is REF_SUB_SEGMENTATION_MAPPINGS
• Below is mapping in table.

VERT & SUBV mapping in reference data service API level.

• In Segments Reference data API, a new field is introduced, which will represent the mapping between VERT and SUBV
• New field name is parentSegmentValueCode
• Below is mapping in API response.

Backend logic

Functionality:

1. SUBV is automated to concern members.
2. SUBV cannot be added directly to concern members.
3. SUBV can be added only on parent customer level if VERT is already present.
4. SUBV that falls under existing VERT category should only be allowed to add on customer.
5. If VERT is updated/deleted, then auto delete the SUBV segments under it.

Technical changes:

1. Database changes
   1. Add SUBV segment to Application config’s Inheritable segment list and remove from non-inherit list.
2. Service changes.
   1. Validation for SUBV - VERT
      1. Only SUBV → don't' allow.
      2. SUBV + VERT but mapping conflict → don’t allow.
      3. Don’t allow SUBV to be added on concern member.
   2. If VERT is updated/deleted, then auto delete the SUBV segments under it.
   3. SUBV segment updates should be inherited by child customers.