OTC: Order To Cash

OTC: Order To Cash

NOTE

this module is in development and is not in production!

1.1. Database

1.1.1. WorkFlow

1.1.1.1. Adding a customer

1.1.1.2. DB synchronization

  1. forward update: nmsprime –> nmsprime_ccc, via a ISP service user

  2. reverse update: nmsprime_ccc –> nmsprime, from customer via CCC

1.1.1.3. Solution Ideas:

  • @Patrick Reichel: Reverse update: only by ticket system (TODO) See Authentication API

  • forward update: DB update in nmsprime auto updates nmsprime_ccc, e.g. via Observer, just simply copy Model from Admin in CCC context and save, this could also be done scheduled (without Observers for heavy/mass assignments)

  • reverse update: defined merge rules (table), auto- and/or manual update mode
    manual mode: means a service admin performs updates based on nmsprime assumptions to update

  • migration synchronization with ProvBase or Billing Module:
    Solution: https://github.com/mrjgreen/db-sync – See Example 8:




1.1.2. availability/product checking

1.1.2.1. address / product mapping

required fields address table:

  • zip

  • city

  • street

  • house_number

1.1.3. Structure

 

 

 

DB name

nmsprime_ccc

 

DB user

nmsprime_ccc

 

 

 

 

required tables

contract

 

 

sepamandate

 

 

item

 

 

 

 

 

 

 

 

1.2. KDG OTC Example

Comments