Standard Tasks

In this section

• System Tasks
• Tasks Within Divisions
• Tasks Related to Objects

Make sure to monitor task statuses. In case of errors you are to contact tech support.

System Tasks

Task	Description	Settings
Analyzing database schema	Gathers statistics on tables in the AIS_NET schema. Up-to-date statistics allows the database to choose optimal plans for executing requests.	Percentage to estimate — a percentage of table rows to estimate. Gather statistics only on frequently changing tables — the analysis is carried out only for tables with data that has significantly changed since last statistics collection. Invalidate cursors immediately — if selected, dependent cursors are invalidated immediately.
Archiving database tables	Archives fast-growing DB tables after a specified period by moving outdated records from the main to a separate table space.	Maximum execution time — a time interval after which an executing task is aborted. Traffic CDRs aging period — a period for storing logs on completed PPP sessions in the main table space. Application sessions aging period — a period for storing logs on completed application sessions in the main table space. Provisioning data aging period — a storage period in the main table space of the provisioning data that is no longer used in the system.
Deleting inactive register records	Deletes outdated records from special tables containing details on providing services, active credit limits, etc.	Maximum execution time — a time interval after which an executing task is aborted. Aging period of credit limit register records — a period for storing records on outdated credit limits.
Executing deferred tasks	Runs procedures that allow asynchronous processing by extracting them from the special queue. Such procedures are: issuing charge logs and discount certificates after payment, updating certain materialized views and indexes, and re-creating equipment profiles by a template. To process the queue faster, several task instances can be created in the system. If the queue is empty, the task will continue running while awaiting new procedures.	Maximum execution time — a time interval after which an executing task is aborted.
Monitoring materialized views refreshing	Monitors refreshing materialized views that are necessary for the quick search. Performs fast refreshing of all views. If fast refreshing is not possible and the check box Allow full refreshing of materialized views is selected, carries out full refreshing.	Allow full refreshing of materialized views
Optimizing Oracle Text indexes	Optimizes the quick search performance.
Purging exception queues	Deletes obsolete messages that are in error queues because they were not delivered by the system queues to a receiving application.	Message storage period — a storage period of messages in the error queues.
Refreshing materialized views for quick search	Carries out fast refreshing of materialized views used for the quick search if initial data has changed.

Tasks Within Divisions

Task	Description	Settings
Archiving charge logs	Archives executed and canceled charge logs according to the parameters specified in service providing schemes. Saves table space thus increasing the DB performance. If the task does not run for a long time, the system performance may noticeably drop.	Maximum execution time — a time interval after which an executing task is aborted.
Activating non-payment suspensions	Detects customers with insufficient funds, i.e. those who do not have enough funds on their accounts to issue further charge logs under one contract. If the period after the last charge log ended is equal to Grace period before non-payment suspension from division parameters, the task issues a charge log with a service of the Non-payment suspension type. And the contract becomes Suspended. If a suspension service is not available (for example, it was not added to a price specification), a contract is not suspended and is not checked during further task runs. To repeat the attempt to suspend such a contract after adding a suspension service you need to select the Process customer accounts using new suspension parameters check box in the task settings.	Process customer accounts using new suspension parameters — select this check box after changing suspension parameters (decreasing a grace period, or adding a suspension service to a price specification). Then the task will once again check customer contracts that were previously skipped due to a longer period before suspension activation or inability to match a corresponding service. New suspension parameters will affect only the contracts that have not been suspended yet. If there is already a charge log with a suspension service under a contract, the changes will not affect it.
Archiving data processing requests	Archives outdated requests for processing data that were created when building reports, and deletes data corresponding to them in DB tables. Saves table space thus increasing the DB performance.	Aging period since planned execution date — a request will be archived if the number of days passed since its planned execution date exceeds the specified number. Allowable number of report table rows — if after archiving all old requests, the number of rows in the DB table with report data exceeds the one specified here, the task will archive the oldest requests until the allowable number of rows is achieved.
Calculating business indicators	Calculates business indicators for widgets except for including data for the current date into calculations.	Period for indicators calculation — a total number of months to be taken into consideration when calculating indicators. Period without using any services to consider customer inactive — is used when detecting customer activity. Region hierarchy type to calculate penetration — a federal or municipal hierarchy. Recalculate indicators — if selected and the previous task run was less than 1 day ago, the task will recalculate indicators, after that, the check box will be cleared.
Canceling expired prepared payment orders	Changes statuses of payment orders from Prepared to Canceled if the time elapsed from their creation exceeds the one specified in the task settings.	Timeout — a period of time after which a prepared payment order is transferred into the Canceled status.
Closing and putting in force charge logs	The task does the following: changes statuses of reserved charge log rows into Charged if their charging date has come and thus charges corresponding amounts to customer accounts, puts in force prepared charge logs which start dates have come, closes charge logs that are in force, i.e. makes them Executed if their period is over, generates events on deactivating additional services that expired before a charge log validity period, closes expired credit limits. If for some reason the task becomes locked, customers will not be charged for current services as well as no expired credit limits will be closed. As a result, customers will be able to continue using services even with insufficient funds on their accounts. The following successful run, when funds will be charged for the whole task downtime, will then lead to customer debts.	Task execution time when profiling results are shown — if the task runs longer than specified in this parameter, its log will contain durations of each of its steps. Relative error threshold to consider task run failed — if the ratio of failed operations to the total number of operations within one task run exceeds the threshold value, the run will be aborted with the Error status. Trace when runtime threshold is reached — if selected and the runtime threshold is exceeded, the task run will be traced. Runtime threshold for tracing. Tracing duration — a time interval during which the task run is traced.
Closing expired application sessions	Closes sessions from the Service Provider Console and the Customer Self-Care Portal applications when the period after their last activity exceeds the one specified in the task settings.	Period since last session activity
Creating payment requests	Creates payment requests and autopayments according to the rules specified in Administration → Parameters → Payment requests.
Monitoring customer account balances	Detects discrepancies between customer account balances and payment and charges amounts. If a warning about a discrepancy appears in task logs, be sure to contact tech support.	Allowable number of errors — the number of accounts with mismatching balances, at which the task will be terminated with an error. Recalculate erroneous balances — if selected, erroneous balances are to be recalculated. Be sure to consult with tech support before selecting this check box. Enable logging — if selected, the task logs will contain details on accounts with discrepancies.
Monitoring overdue receivables	Monitors overdue customer receivables. When detected, the task closes a current invoice for a service. Charges late payment fees and early termination fees for contract commitments due to unpaid receivables.	Charge log end dates for subscriptions with overdue receivables — you can use this parameter if due some reasons the task has not run for a long time. With the next run, charge logs with overdue receivables will be closed with end dates equal to the specified date. If the date is not entered, the charge logs will be closed with end dates equal to corresponding due dates. The parameter value is used only at the first task run. After it the value is deleted.
Monitoring payment allocation registers	Monitors matching customer payments to receivables. If a warning about a discrepancy appears in task logs, be sure to contact tech support.	Allowable number of errors — the number of accounts with incorrect allocation, at which the task run will be terminated with an error. Recalculate invalid values — if selected, invalid values are to be recalculated.Be sure to consult with tech support before selecting this check box. Enable logging — if selected, the task logs will contain details on accounts with discrepancies.
Obtaining provisioning commands execution results	Retrieves from the incoming queue results of equipment control commands that are executed by the HEX agent, and saves them into a system table.
Preparing charge logs for recurrent services	Analyzes customer subscriptions to services. If time remaining before the current invoice ends is less than a number of hours specified in the Period for creating new charge log before current one ends division parameter, a new charge log is issued in accordance with the subscription that is active at the time the previous charge log ends. A start date of the new charge log is equal to the end date of the previous one plus one second. The new charge log is created with the Prepared status. If in the task settings Period closing date is specified and a corresponding day of the month comes, the task creates a period closing memo with a period equal to the previous calendar month. For example, if in the settings the 10th day is specified as the closing date then on the 10th day of the current month the task will create a period closing memo with the period from the 1st to the last day of the previous month. Task locking or a failure during its run leads to the situation when charge logs for a new period will not be issued, thus, subscription fee will not be charged and services may become unavailable.	Period closing date — a day of a current month for closing a previous month. Warn about enabled deferred payment without fixed billing date — if selected and there are charge logs to be issued for subscriptions without fixed billing dates and enabled deferred payment, there will be warnings in the task logs. Relative error threshold to consider task run failed — if the ratio of failed operations to the total number of operations within one task run exceeds the threshold value, the status of this run will be Error. Trace when runtime threshold is reached — if selected and the runtime threshold is exceeded, the task run will be traced. Runtime threshold for tracing. Tracing duration — a time interval during which the task run is traced.
Processing recommended payments	For each active customer, the task estimates the closest date of any provided service deactivation. If the number of days before deactivation is less than specified in the task settings, a recommended payment is calculated for the customer. If the recommended payment is greater than 0, the Recommended payment exists event is raised for the customer. If the deactivation date is not estimated, for example, when a customer uses services with Providing condition set to Sufficient balance is not required, then, with the non-zero promised payment, the event will be also raised.	Period for creating notification before service deactivation
Processing session RADIUS accounting data in provisioning module	Rates traffic services on the basis of RADIUS accounting data for customer sessions preliminarily loaded by agent HARD into Hydra Billing.
Processing system message queue	Retrieves from the system queue messages sent by external applications, and executes commands sent via this messages.
Re-executing provisioning commands	Re-creates and sends to the execution queue such commands that have not been successfully executed, or no result was received over the period specified in task settings. The number of attempts to re-execute a command is limited by the corresponding parameter value.	Execution timeout before command re-execution — a waiting period after a command is queued for execution upon which it can be sent for re-execution. If not specified, a default timeout value is 30 minutes. Maximum number of command re-executions — unless specified, the default value is 5.
Synchronizing sessions with profiles in provisioning module	Generates commands for terminating or changing parameters for active sessions that are bound to inactive at the moment equipment profiles or those which exceed a maximum number of simultaneous sessions specified in the corresponding profile.	Timeout for hung sessions — the task generates commands to terminate active sessions that violate the restriction for the number of simultaneous sessions with the period since last update shorter than the one specified in this parameter.
Terminating service contracts and disabling customers	Changes statuses from In force into Terminated for expired contracts unless there are open subscriptions, as well as contracts with a fully provided service of the Non-payment suspension type. In case after that a customer has no contracts in force he or she becomes Disabled.
Updating current profiles in provisioning module	Switches active profiles when changing the current time interval, and also changes the state of profiles according to their validity periods.
Updating equipment in provisioning module	Retrieves messages from the system queue that concern changes of statuses and parameters of CPEs and addresses bound to them, and accordingly refreshes data on these CPEs in provisioning module. After refreshing data, it creates missing profiles and configurations for the CPEs. If the queue is empty the task will continue running while awaiting new messages.	Maximum batch size — the maximum number of messages retrieved from the queue at once.
Updating service statuses in provisioning module	Retrieves from the system queue messages concerning changes of statuses and parameters of services provided on CPEs, and accordingly refreshes data on these services in provisioning module. Creates missing profiles and configurations for new subscriptions to services. If the queue is empty the task will continue running while awaiting new messages.	Maximum batch size — the maximum number of messages retrieved from the queue at once.

Tasks Related to Objects

Task	Description	Settings
Obtaining data collector statistics	Is automatically added (while locked) when an object is transferred into the Active status, if this object was created on the basis of the Data collector product catalog entry from the Network services section. Rates traffic obtained from SNMP data collectors. If traffic volume matters for customers (when traffic is not free, or a bandwidth depends on it, etc.), a lock of the task or an error may lead to customer debts or incorrect service providing parameters.	Allow statistics without address — if cleared and no CPE IP address is specified in statistics, traffic is considered unaccounted. Group statistics by address — if selected and CPE has several IP addresses, traffic for them will be accounted and logged into a charge log separately; if cleared, traffic for several addresses is summed up and recorded in one row of a charge log. Trace during next run — if selected, the next task run will be logged in detail.
Obtaining traffic collector statistics	Is automatically added (while locked) when an object is transferred into the Active status if this object was created on the basis of the Traffic collector product catalog entry from the Network services section. Obtains statistics and rates traffic collected by the aggregator. If traffic volume matters for customers (when traffic is not free, or a bandwidth depends on it, etc.), a lock of the task or an error may lead to customer debts or incorrect service providing parameters.	Allow statistics without address — if cleared and no CPE IP address is specified in statistics, traffic is considered unaccounted. Group statistics by address — if selected and CPE has several IP addresses, traffic for them will be accounted and logged into a charge log separately; if cleared, traffic for several addresses is summed up and recorded in one row of a charge log. Trace during next run — if selected, the next task run will be logged in detail. Session attribute with customer IP address — a name of a session attribute which is used when searching for it while rating.
Synchronizing with equipment manager	Is automatically added (while locked) when an object is transferred into the Active status if this object was created on the basis of the Active equipment manager product catalog entry from the Network services section. Prepares and transfers generated managing commands to agent HAMD, processes obtained replies. If the task does not run for some reason, commands will not be transferred to equipment. As a result, for example, customers may be denied access regardless of a new billing period start. Or, on the contrary, customers will continue using services even with disabled access service, or without a charge log for a new period.	Reply timeout — a period in seconds during which the task waits for the HAMD agent respond with commands results. If the response is not received on time, the task is aborted with an error. With the task next run, commands previously transferred to the HAMD agent will be re-executed.

External Tasks

Task	Description
Executing data processing requests	Processes the data processing requests queue including requests for building reports.
Synchronizing with external service	Is used for replicating data to external services.