Sales Orders

CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. supports the ordering and purchase of hardware and software, such as handsets, devices, peripherals and software licences.

The lifecycle of an order is as follows:

• A new order is requested, for example by a CSA Customer Service Agent, Advisor, or Assistant. A (usually) customer-facing role in telecommunications, such as an agent in a call centre. Variations include CSR (Customer Service Representative) or CEA (Customer Experience Agent) in AgentView The graphical user interface of the CMP that is typically used by Customer Service Agents to access CMP customer and billing data. In versions prior to CMP 8.0, this was called the CMP GUI..
• Products and items are added to the order, which may involve a stock check to confirm if a warehouse has the ordered items in stock. Order status = Awaiting Generation.
• The order is generated and sent to the warehouse. Order status = Awaiting Dispatch.
• The warehouse fulfils the orders and dispatches it, sending details of the outcome to CMP. Order status = Complete (or Error).

This is handled by the following jobs.

• Sales Order Request

  After orders are created and products are added to them, the next step is to generate the order. This job generates the order at the correct level of granularity The scale or level of detail in a set of data. (i.e. what a line in the order request actually represents) for the warehouse. Then the job prepares the order for sending to different warehouses by creating batches on a per warehouse basis. The Sales Order Request job supports performing a fraud check on a sales order prior to sending the order to the warehouse. The fraud check verifies the delivery name, address and contact details. The element, "contactDetails" in the Order Request JSON JavaScript Object Notation. JSON is a lightweight format for storing and transporting data, often used when data is sent from a server to a web page. (orderrequest.schema.json) appears after the postal address in the order array and contains the contact numbers (telephoneNumber & telephoneNumber2) that are defined depending on whether the address is a business or personal one. The element, "fraudCheckRequired" is in the Order Request JSON after the contact Details in the order array. Whether a fraud check is required can be controlled via the job property, sales.order.request.job.fraudcheckrequired. The job can be triggered to run as soon as an order is awaiting generation or it can be scheduled to run when appropriate.

• Sales Order Dispatch

  This job updates CMP with information from the warehouse once the order has been dispatched, and bills for those order items where appropriate. The information from the warehouse includes details of what was dispatched and possibly associated attributes of the items that were dispatched such as serial numbers, for example. To support fraud checks, the job supports an order status of Review, which indicates that the initial fraud check failed and a secondary manual check is required,.

The following daemons are associated with Sales Orders:

Type	Category	Activity	Details
Load	Sales Orders	From Generic Format	This daemon collects and decrypts generic CMP files and creates CMP batches, which are available for processing into CMP by the appropriate batch job.
Extract	Sales Orders	To Generic Format	The daemon creates and encrypts generic CMP files, which are available for conversion into a third party format.