Data Warehouse Extracts
Overview
The DWH
Data Warehouse. A central repository for data collected by an organization's business systems; usually used for reporting and data analysis. extract is made up of separate outputs covering the lifecycle of the customer
In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement.. All data is retrieved from the CMP
Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. database.
The DWH extract is produced by CMP batch process, comprising batch jobs such as the Unbilled Usage Analytics job, that can be run manually or scheduled using the CMP Administration Console
An operations web console that allows batch jobs to be scheduled, run manually and monitored. The console also provides for viewing and modification of business and user applicable system configuration.. The following table lists the batch jobs, the parameters that they take, and the extracts that they produce:
| Batch Job | Parameters | Extract |
|---|---|---|
| Account Analytics | Full/Partial* | Account Analytics |
| Agreement Analytics | Full/Partial | Agreement Analytics |
| Billed Usage Analytics | Invoice Run # | Billed Usage Analytics |
| Invoice Detail Analytics | Full/Partial | Invoice Detail |
| Payment Detail Analytics | Full/Partial | Payment Details Analytics |
| Prepaid Usage Analytics | Extract Date** | Prepaid Usage |
| Purchase Analytics | Full/Partial | Purchase Analytics |
| Statement Analytics | Full/Partial | Statement Analytics |
| Subscription Analytics | Full/Partial | Subscription Analytics |
| Subscription Feature Analytics | Full/Partial | Subscription Features |
| Subscription Service Analytics | Full/Partial | Subscription Service |
| Transaction Detail Analytics | Full/Partial | Transaction Detail Analytics |
| Unallocated Usage Analytics | Full/Partial | Unallocated Usage Analytics |
| Unbilled Usage Analytics | Extract Date | Unbilled Usage Analytics |
|
* Full mode retrieves all records. Partial mode retrieves all new records since the job was last run. The job checks the interface batch header for the last record produced. If no record is found, it runs in Full mode. |
||
For more information about these extract jobs, see the CMP Batch Jobs and JSON Schemas Guide. See also the jobs descriptions provided in the CMP Administration Console.
Scheduling
In MDS Global Business Operations implementations, the MDS Application & Billing team is responsible for scheduling the process.
In licence-only or Business Operations Partner implementations, the party responsible for operating CMP must determine the most appropriate point in the daily batch schedule to run the extract.
Flow
The start point for the extract is the submission of the process; either manually through the CMP Administration Console or automatically using the Console's scheduling function.
Error scenarios in the process can prevent the extract being produced. In such scenarios, the appropriate error is written to the operations message queue so that monitoring tools (such as Nimsoft) can trigger alerts/alarms. Administration Console probes can also be used as quality measures.
Successfully completed extracts are placed on the file system of the CMP server for collection by the consuming party (usually the service provider
The owner of the infrastructure in which accounts will be created. The Service Provider can host and operate the instance of CMP, or CMP can be provided as a Managed Service.).