Interface Purge

Job type: Java A widely used object-oriented programming language that is designed for use in the distributed environment of the internet. It is the most popular programming language for Android smartphone applications

Batch job name: Interface Purge

Archive: None

For more information on this job, see the Job Details in the 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.: In the console, navigate to System Maintenance > Jobs. In the Job List, click the name of job to open its Job Details screen.

This job purges transaction data that has been successfully committed to CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers.. Once data is successfully moved into the CMP database, there is no need to store the information in the equivalent interface batch detail tables. Inbound batch jobs, for example Rated Usage, set the isRetain field on InterfaceBatchDetail tables to false, which effectively moves the record into the discard partition, which is in turn sub-partitioned by creation date. The Interface Purge job removes discarded partitions and thus transaction data from the InterfaceBatchDetail table and by default the UsageBatchDetail table if the partitions' creation date is outside a cut-off point - the calculated purge date. Once the job is complete, information such a 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. level, customer reference, and transaction description are either empty or removed.

The job creates an InterfaceBatchHeader record for each invocation, and initially sets the stage to Batch and status to In Progress. Then it drops the InterfaceBatchDetail, UsageBatchDetail and UsageAllowanceBatchDetail partitions. The job also drops daily partitions older than 90 days from the following tables:

• Order Request Batch Detail

• Order Dispatch Batch Detail

• Order Dispatch Line Batch Detail

• Order Dispatch Line Attribute Batch Detail

• Usage Allowance Batch Detail.

Next the job creates an InterfaceBatchDetail record for each partition that is removed as follows:

• Customer Level =Empty

• Customer Reference =Empty

• Transaction Description = e.g. usage The consumption of services, for example a subscriber using call minutes. partition 15-Jan-2020 removed

• ensures that the isRetain field is set to true.

After all partitions are removed, the job updates the InterfaceBatchHeader record, by setting the status to Complete.

Selection criteria

The job accepts a single parameter - Days to Retain. This represents the number of days worth of data to retain. The job subtracts this parameter from the current date to calculate a purge date. Only data dated on or before the calculated purge date is purged. Partitions are created daily; any partitions with a creation date prior to the calculated purge date are removed. Any transaction data prior to the retention period will be permanently removed.

A value of zero (0) is not allowed as a parameter.

Tables Impacted:

• InterfaceBatchDetail
• UsageBatchDetail
• UsageAllowanceBatchDetail

Running the purge job

In the Administration Console, you can create a schedule for the purge job or run it as needed.

To run a job:

1. Navigate to Daily Operations > Jobs.
2. In the Job List, select the checkbox for the job that you want run.
3. Click Run Now.