500 System Operations Guide

System Operations Guide for

Singl.eView Convergent Billing V5.00

Trusted by over 1 million members

Try Scribd FREE for 30 days to access over 125 million titles without ads or interruptions! Start Free Trial Cancel Anytime.





































Printing History

First Printing, June 2002

Document Number

VA500-55-1015-BR3, V5.00

Disclaimer

Although every effort has been made to ensure the accuracy of the information contained in this document, ADC Software Systems Ireland Limited makes no warranty, expressed or implied, with respect to the quality, correctness, reliability, currency, accuracy, or freedom from error of this document or the products it describes. ADC Software Systems Ireland Limited may make improvements and/or changes to the products and services described in this document at any time. ADC Software Systems Ireland Limited disclaims all liability for any direct, indirect, incidental, consequential, special, or exemplary damages resulting from the use of the information in this document or from the use of any products described in this document. Mention of any other product not owned by ADC does not constitute an endorsement of that product by ADC Software Systems Ireland Limited. Data used in examples and sample data files are intended to be fictional and any resemblance to real persons or companies is entirely coincidental. Persons reading this document should rely on their own enquiries in making any decisions touching on their own interests.

Licence Agreement

The software described in this guide is supplied under a licence agreement and may only be used in accordance with the terms of that agreement.

Copyright Information

\u00a9 2000 ADC Software Systems Ireland Limited. All rights reserved. Apart from any use permitted under the Copyright Act, no part may be reproduced by any process without the written permission of ADC Software Systems Ireland Limited, IDA Business Park, Dangan, Galway, Ireland. The following is a trademark of ADC Software Systems Ireland Limited:

The following are third party trademarks used in this document: Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation in the USA and other countries. FrontPage is a trademark of Microsoft. TEX is a trademark of the American Mathematical Society. PostScript and Acrobat Reader are trademarks of Adobe Systems Incorporated. UNIX is a registered trademark of The Open Group. TUXEDO is a registered trademark of BEA Systems, Inc. Oracle is a registered trademark of Oracle Corporation. AIX is a registered trademark of International Business Machines Corporation. InstallShield is a registered trademark of InstallShield Software Corporation. Java is a trademark of Sun Microsystems, Inc. SQR is a trademark of Brio Technology, Inc.











































Table of Contents

Preface ....................................................................................................................................... v

Welcome to Singl.eView Convergent Billing ............................................................................ v Who Should Read this Guide .................................................................................................... vi Before Beginning....................................................................................................................... vi How this Guide is Structured ................................................................................................... vii Other Singl.eView Convergent Billing Documentation ........................................................... vii Conventions Used in this Guide .............................................................................................. viii Obtaining Help .......................................................................................................................... ix The Online Help System ............................................................................................... ix Form Help ...................................................................................................................... x Context-sensitive help ................................................................................................... xi Hint text ........................................................................................................................ xii Help on Confirm window options ................................................................................ xii Help on error messages ............................................................................................... xiii

Part 1 \u2013 Billing Operations Chapter 1 \u2013 Introduction to Rating and Billing ................................................................. 1-1

Overview of Rating and Billing............................................................................................... 1-1 Events .......................................................................................................................... 1-3 Balance Management .............................................................................................................. 1-5 Event Rating ............................................................................................................................ 1-6 Event Rating Broker (ERB) process ........................................................................... 1-7 Event Normalisation (ENM) process .......................................................................... 1-9 Event Rating (ERT) process...................................................................................... 1-10 Event Rating Output (ERO) process ......................................................................... 1-11 Rating errors .............................................................................................................. 1-12 Parallel tariffing ........................................................................................................ 1-13 Recurring charges...................................................................................................... 1-13 Billing .................................................................................................................................... 1-14 Rental Generation Process (RGP) ............................................................................. 1-15 Bill Generation Process (BGP) ................................................................................. 1-16 Invoice Generation Process (IGP) ............................................................................. 1-17 trerwdb ...................................................................................................................... 1-17 trerodb ....................................................................................................................... 1-18 General Output Process (GOP) ................................................................................. 1-18 Working with invoices .............................................................................................. 1-18 Invoice templates....................................................................................................... 1-18

Chapter 2 \u2013 Rating ................................................................................................................ 2-1

Managing Rating Files ............................................................................................................ 2-1 Running a Rating Task ............................................................................................................ 2-3 Preparation .................................................................................................................. 2-3 Running the rating task ............................................................................................... 2-3 Checking the results .................................................................................................... 2-4











































Table of Contents

Correcting Rating Errors ......................................................................................................... 2-8 Unsuccessful rating task.............................................................................................. 2-9 Correcting corrupted events ........................................................................................ 2-9 Correcting error events ................................................................................................ 2-9 Correcting wrong charges ......................................................................................... 2-11 Revoking a rated and reprocessed file ...................................................................... 2-12 Removing unwanted events and charges .................................................................. 2-12 Rating Schedule Types .......................................................................................................... 2-12 Using selection criteria.............................................................................................. 2-13

Chapter 3 – Billing ................................................................................................................ 3-1

The Bill Run Process ............................................................................................................... 3-2 Processing billing operations ...................................................................................... 3-3 Bill run operations ....................................................................................................... 3-5 Tracking the status of a bill run .................................................................................. 3-5 Server process ............................................................................................................. 3-6 Configuring the customer node ................................................................................... 3-7 Setting priorities .......................................................................................................... 3-7 Performing a Bill Run ............................................................................................................. 3-8 Preparation .................................................................................................................. 3-8 Supported task types ................................................................................................... 3-8 Setting up a bill run ..................................................................................................... 3-8 Bill Run Types ............................................................................................................ 3-9 Bill Run Schedule Parameters ................................................................................... 3-11 Modifying a bill run .................................................................................................. 3-11 Performing an operation on a bill run ....................................................................... 3-11 Stopping a bill run ..................................................................................................... 3-12 Revoking a Billing Task ............................................................................................ 3-13 Checking the results .................................................................................................. 3-13 Suppressing Invoice Generation ............................................................................... 3-14 Correcting Billing Errors ....................................................................................................... 3-15 Billing Schedule Types.......................................................................................................... 3-17 Billing of Customer Hierarchies ............................................................................................ 3-20

Chapter 4 – Batch Printing .................................................................................................. 4-1

Invoice Output using the Scheduler ........................................................................................ 4-2 GOP schedule configuration parameters ..................................................................... 4-2 GOP schedule processing............................................................................................ 4-3 Invoice Output using a Bill Run .............................................................................................. 4-4 Bill run configuration parameters ............................................................................... 4-4 Setting up a bill run to print invoices or statements .................................................... 4-5 Printing invoices on a previously-completed bill run ................................................. 4-5 Single invoice printing ................................................................................................ 4-6 Printing Document Images ...................................................................................................... 4-7 Preparation for printing ............................................................................................... 4-7 Checking the output .................................................................................................... 4-7











































Table of Contents

Configuring Output Processing for the GOP........................................................................... 4-8 Output method type ..................................................................................................... 4-8 Output device .............................................................................................................. 4-9 Scripts for output ....................................................................................................... 4-10 Output device examples ............................................................................................ 4-11 Output method definition .......................................................................................... 4-13 Output method example ............................................................................................ 4-13

Part 2 – The Transaction Engine Chapter 5 – The Transaction Engine (TRE) ...................................................................... 5-1

Part 3 – Task Automation Chapter 6 – Scheduling Server Tasks ................................................................................. 6-1

Scheduling Overview .............................................................................................................. 6-2 Terms used in scheduling ............................................................................................ 6-3 Working with Schedules .......................................................................................................... 6-5 Submitting a schedule ................................................................................................. 6-5 Re-submitting a task .................................................................................................... 6-5 Changing the frequency of a schedule ........................................................................ 6-5 Deleting a schedule ..................................................................................................... 6-6

Chapter 7 – Schedule Types ................................................................................................. 7-1

Schedule Type Details ............................................................................................................. 7-7 Apply & Allocate Invoices .......................................................................................... 7-8 Apply & Allocate Invoices for Customer ................................................................... 7-9 Apply Invoices .......................................................................................................... 7-10 Apply Invoices for Customer .................................................................................... 7-11 Apply Transactions ................................................................................................... 7-12 Archive ...................................................................................................................... 7-13 Billing Suppress ........................................................................................................ 7-14 Billing Unsuppress .................................................................................................... 7-16 Complete Bill Run..................................................................................................... 7-17 Complete Bill Run for Customer .............................................................................. 7-18 Contract Cancel/Notify ............................................................................................ 7-19 Create Partitions ........................................................................................................ 7-21 DIL Validation .......................................................................................................... 7-23 Dunning Letter Generation ....................................................................................... 7-24 ECP Command .......................................................................................................... 7-25 Explain BGP Hierarchy Passes ................................................................................. 7-26 Full Database Validation........................................................................................... 7-27 General Bulk Output By Task ................................................................................... 7-28 General Bulk Output Process .................................................................................... 7-29 Generate Invoice Images ........................................................................................... 7-30 Generate Invoice Images for Customer ..................................................................... 7-31 Invoice Generate Image 7-32











































Table of Contents

Invoice View Image .................................................................................................. 7-35 Partition Maintenance ............................................................................................... 7-36 Print Invoices ............................................................................................................ 7-38 Print Invoices for Customer ...................................................................................... 7-39 Purge Error Events .................................................................................................... 7-40 Purge Events (non Error) .......................................................................................... 7-42 Purge Files ................................................................................................................. 7-43 Quality Assurance Bill Run ...................................................................................... 7-44 Rate Files................................................................................................................... 7-45 Re-analyze tables....................................................................................................... 7-46 Re-rate Error Events .................................................................................................. 7-47 Re-rate Error Events (bulk) ....................................................................................... 7-48 Re-rate Events (bulk) ................................................................................................ 7-50 Re-rate File ................................................................................................................ 7-52 Reconfigure Auditing ................................................................................................ 7-53 Report Reference Type (RRRT) ............................................................................... 7-54 Reprocess Error Events ............................................................................................. 7-55 Reprocess Event ........................................................................................................ 7-57 Revoke Bill Run ........................................................................................................ 7-59 Revoke Bill Run for Customer .................................................................................. 7-61 Revoke Event File ..................................................................................................... 7-62 Revoke File and move back ...................................................................................... 7-63 Revoke Invoice Images ............................................................................................. 7-64 Revoke Invoice Images for Customer ....................................................................... 7-65 Revoke Invoice Print Settings ................................................................................... 7-66 Revoke Invoice Print Settings for Customer ............................................................. 7-67 Revoke Invoices ........................................................................................................ 7-68 Revoke Invoices (keep Rentals) ................................................................................ 7-69 Revoke Invoices (keep Rentals) for Customer .......................................................... 7-70 Revoke Invoices for Customer ................................................................................. 7-71 Revoke Rental Events ............................................................................................... 7-72 Revoke Rental Events for Customer ......................................................................... 7-73 Revoke Reprocessed File .......................................................................................... 7-74 Rotate Partitions ........................................................................................................ 7-75 Standard Bill Run ...................................................................................................... 7-78 Switch Files ............................................................................................................... 7-79 UnApply & Deallocate Invoices ............................................................................... 7-80 UnApply & Deallocate Invoices for Customer ......................................................... 7-81 UnApply Invoices ..................................................................................................... 7-82 UnApply Invoices for Customer ............................................................................... 7-83 Unarchive .................................................................................................................. 7-84 Update Account Unbilled.......................................................................................... 7-85 Update Charge Categories......................................................................................... 7-86 Update Invoice Unbilled ........................................................................................... 7-87 Update Lists .............................................................................................................. 7-88 Verify Charge Partition ............................................................................................. 7-89 Verify Charge Partition Range .................................................................................. 7-90













































Preface

Welcome to Singl.eView Convergent Billing Singl.eView Convergent Billing has been designed specifically for new

Singl.eView Convergent Billing is based on industry standard

This guide describes the facilities provided in Singl.eView Convergent

•

Billing operations.

•

The Transaction Engine (TRE).

•

Scheduling server tasks using the client workstation scheduler.

Note: Throughout this manual the name 'Singl.eView Convergent Billing' has been abbreviated to 'Convergent Billing' wherever an abbreviated form contributes to easier reading.











































Preface

Who Should Read this Guide This guide is specifically aimed at staff responsible for controlling Convergent Billing server operations for a range of tasks, including: •

Rating and billing.

•

Generating invoices and letters.

•

Batch printing of invoices, statements, and letters.

This guide does not discuss the preparation and printing of reports, which can also involve server processes. This is discussed in the Reports Guide.

Before Beginning This guide assumes that the reader has some experience in using: •

Microsoft Windows

•

UNIX

•

SQL.

It also assumes a through knowledge of the company's system operation and billing procedures.











































Preface

How this Guide is Structured This guide consists of seven chapters, divided into three parts: Part 1 provides details on billing. This part consists of the following four chapters: •

Chapter 1, Introduction to Rating and Billing Overview of rating and billing.

•

Chapter 2, Rating Normalisation and rating of events.

•

Chapter 3, Billing Billing and invoice creation.

•

Chapter 4, Batch Printing Batch printing and other output methods available.

Part 2 provides information on operational aspects of the Convergent Billing Transaction Engine, used to interface Convergent Billing with other applications. This part consists of the following chapter: •

Chapter 5, The Transaction Engine (TRE) Overview of the Transaction Engine.

Part 3 provides information on using the Scheduler to automate server tasks, and on the types of schedule which can be defined. This part consists of the following two chapters: •

Chapter 6, Scheduling Server Tasks Describes the use of the Scheduler, and how tasks are created.

•

Chapter 7, Schedule Types Lists schedule types in the base installation that are available for users. It also explains how to create new schedule types.











































Preface

Conventions Used in this Guide The following conventions are used in this guide:

File ➩ Exit

Indicates that the File menu should be opened and the Exit option selected.

Save button

Button on the toolbar or on a form.

Customer Detail form

Name of a specific form.

Account Status field Name of a field on a form. UNIX output

In interactive and code examples, this typeface is used to indicate system output.

UNIX input

In interactive examples, this bold typeface is used to show user input.

Ctrl+F4

In procedures, a key sequence indicates that the Ctrl key must be held down while another key is pressed. In this example, the Ctrl key must

Use of a mouse in Singl.eView Convergent Billing is identical to that in

Select

Highlight one or more characters to perform an operation on those characters.

Click

Point to an object, then press and release the left mouse button.

Double-click

Point to an object, then press and release the left mouse button twice in quick succession.

Drag

Point to an object, hold down the left mouse











































Preface

Obtaining Help Online help is currently available in the form of: •

The Online Help System, which provides access to task based

•

Form help associated with each form.

•

Context-sensitive help associated with each form, field, and control.

•

Hint text associated with each form, field, and control.

•

Help on Confirm window options.

•

Help on error messages.

These help facilities are described briefly in the following subsections.

The Online Help System

The Online Help System has been designed to provide information to suit

•

Task based (procedural) help that provides step-by-step

•

Reference information to assist operators new to Singl.eView

•

Full text search and keyword (index) search facilities to locate information in the help system.

•

Examples and video demonstrations, to show by example how to perform some of the more common procedures.

•

Glossary of terms, which defines each of the terms used in Singl.eView Convergent Billing.













































Preface

Options to access the Online Help

Help menu. For example, to access the Welcome Screen, select the Contents option from the Help menu.

Form Help

Forms are used to enter, view, and modify data. A form may contain tabs

To display help for a specific form: 1.

Make the form active.

2.

Click the Help button on the toolbar.

Details about the form are displayed in a separate window.

1. Make the form active

2. Click the Help button











































Preface

Where a form contains one or more tabs, a link is provided on the Form Help window to details relevant to that tab. Such information is displayed in a pop-up window. For the majority of forms, links are also provided to the task based help in the Online Help System.











































Preface

Hint text

Hint text is provided for each form field. Sample hint text for the Family Name field is shown below.











































Preface

Typically, a Confirm window displays a Help button in addition to a Yes, No, and Cancel button. Clicking the Help button provides details of what options are available.

Help on error messages

Whenever an error occurs, an error message is displayed in a separate

To obtain further details of the error: 1.

Click the Help button on the Error window. The Error Message Help window is displayed.











































Preface

Note: Access to the errors, warnings, and messages displayed by Singl.eView Convergent Billing are also available through the Online Help System.













































Part 1 Billing Operations

This part provides details on billing. This part consists of the following four chapters: •

Chapter 1, Introduction to Rating and Billing

•

Chapter 2, Rating

•

Chapter 3, Billing

•

Chapter 4, Batch Printing













































White text













































Chapter 1 Introduction to Rating and Billing

This chapter provides an overview of Convergent Billing rating and billing processes. Full details are provided in the following chapters: •

Chapter 2, Rating

•

Chapter 3, Billing

•

Chapter 4, Batch Printing.













































Introduction to Rating and Billing

•

The billing engine, which generates invoice data, creates the

•

The General Output Process (GOP), which selects and sorts

The rating engine and the billing engine are described briefly in later sections of this chapter, and in detail in the following chapters: •

Chapter 2, Rating

•

Chapter 3, Billing.

The GOP is described in Chapter 4, Batch Printing.














































Events

Any event that results in a charge or benefit being passed on to a

Table 1–1 lists the terms used in Convergent Billing to describe the different kinds of event.

Table 1–1 Convergent Billing Event Types Term

Definition

Alpha event

Event supplied as input to Convergent
















































Term

Definition

Error event

An error event is either a normalisation

Mediated or pre-

Event that has been pre-processed in
















































Balance Management The balance management functionality described in this section is
















































Once the call is complete, the complete event can be passed on to the
















































The rating engine runs under the control of the Event Rating Broker
















































3.

If no ENM, ERT, and ERO processes are associated with that

4.

If all processes are running on one machine, the ERB performs






































































































































































































































































































Generation Program

option are processed runofasrunning TREby servers the a Process range billing and ofare engine billing automatically operations, to generate executed from billing adjusting data, with and the rental start-up eventually of events the system. to un-applying invoices The GOP forinvoices. printing , used toor Ifprint invoices delivery the final are to the generated, invoices customer (orthey output by electronic canthem be means. to sent file), to an is Figure an output independent 1–4 device, showsas process the well architecture asthat applied runsof to asthe customer required. billing accounts. engine. Generation









































Generation Process (RGP)

corrections during line billing may required tonot generate beto continuous, existing rentaladvance events for example, and rental rental ifcharges theadjustment service if the was details events not of the before have rental invoices available changed or for statements part since ofthe theare charge period. generated. was made. In rental For example, generation an mode, rental refersmay adjustment to any be required recurringifcharge, the service suchwas as anot subscription available to tothe a service or









































from product. If thethe details rental 'Normalised charges Theof generation RGP existing incurred applies Event', advance mode. by these 'Charge', a customer The tariffs rental period 'Service', exactly charges nodeis(and specified once 'Customer have bywhen any changed as child Node', certain a nodes since or events for the associated charge which this configuration 'Customer', was node with made, is a specified product rental and item application adjustments lifecycle attribute, as the invoicing occur. environment with areaused Activation node), default toof and make value 'Rating' and to calculate the of cancellation 90 or required 'Billing'. days. totalsof a product correction. and subtotals. instance, For example, facility angroup adjustment instance, may orbe service required can ifresult the rental in one-off









































Generation Process (IGP)

global customer, transactions individual discount template readyflow tariffs for ones. using output each rather Aggregation customer the using TUXEDO than the charge ormeans General two-phase tariffs; that Output node. the for commit. individual example, Process DataThe insertion (GOP). if charges a It is The processing through the IGP iscustomer as follows: does this Transactional arebyaggregated customer's based retrieving on server Convergent usage advertises invoice into is higher one Billing data or services than more from expressions. apre-defined that the preset database read limit and groups for and write the substituting for to specified the the it 1. into an billing database purpose invoice and ensures cycle, template. of obtaining then theaCurrent integrity volume a totalConvergent discount of value the for transactions. could that Billing grouping. be applied releases For more In touse general, the total









































control from statements, images thebefore the database. appearance either committing by The printing of purpose the them final orto of bycustomers' bill the generating displayed read-only accounts. files to server the for customer, electronic isFor to separate morethey transfer services of information also accounting playthat a significant on read information. billing database schedule role in The information processing types, procedures refer from thefor to data services Chapter doing thatthis is that 3,displayed Billing are need explained .to on commit data, in them. Chapter so that4,the Batch transaction Printing load is shared across the TRE servers. In









































type events For a file more ofalready in the information order event processed tothey generate about contain cannot processing normalised and, be if processed. necessary, events eventsfrom and Including some remote charges. indication the hosts, Itdate also known ofand the describes as date time Real range ofTime creation methods covered Rating, infor the by refer checking the fileevents. to name thethat ensures System events Administration that have it isbeen unique. correctly Guide. The normalised and rated, and for correcting events that contain errors.







































are a filemoved in the error theBilling directory archiveinstance with data/server/error progress and status details are the error directory, paths toto conventionally the input, archive, and error directories . The file has (for the more directory the original file name and a '.e' from the rating process home directory same name information as onthe creating original and file, configuring with a .e extension. ENM processes, refer to the extension







































are either not required orarbitrary have been as changes in list and and database 'Rate being Files'. rated resources should Byevt using be may aselected; schedule, reduce performance, if events a rating ofrun, task different both can for be types the rating at are specified being process rated, the characters then contain text (perhaps arun time stamp), charge category are automatically to itself, intervals; it is necessary and for an Immediate concurrent for each Task Convergent tocan have run its Billing anot own single processes. ENM rating andtask schedule. Ifextended possible, immediately the have the extension .itaddefinitions .one existing product rating to (refer task Chapter should be 6, Scheduling runinstances. when other Server system Tasks demands for more are information at a minimum. on scheduling).







































parsed by charge the ENM by is incorrect the orENM; the ERT; (for such such corrupted error because events eventsof are are the saved written wrong in to definition the a file in mandatory expressions parameter being evaluated is included asexample, part in each of normalisation; Normalised Event the value generated selected by the database. of a ENM product or directory tariff); the with event and same charge name are as stored the source in the file should the task. match theerror type of event in the the files. and a.e extension. database. Errors of this kind are often difficult to detect.







































directory. The file has the same name as the original event file, with a .e extension. The data/server/error directory should also be checked for any such corrupted event files.







































should correspond to event an field event inerrors the original ERT, or it (each is in stored the event Normalised as an error Error event; Event if the Count is for flagged asflagged beingfile. in by error There it may be multiple event typeserror per file). by the the ENM. ENM, is stored as a normalised event. The Norm alised





































Billing installations, details in of the call Normalised records forinput example Event within to Error detect theDetail specified abnormally displays dates, high the and reason charges a summary why (for of the charges more information the event that resulted ison inthese error. (for reports, more refer information, to the Reports refer toGuide the Reports ).





































appropriate tariff/product changes

remove successfully rated events that have not been billed?

and move back to input directory to be rated





































corrupted events

detected during normalisation them events: to the input or rating, directory; the event it is suggested is termedthat an the error To dealcontaining with corrupted event. error file be renamed to reflect its origin and current status. 1.





































itself, whatever particular or has steps type; been are for caused required example, by to another if correct the error problem the'No problem, charges such as then were a wrongly run a defined task generated of type tariff, for 'Re-rate derived this event' Error attribute, has Events the function, Error (bulk)'; Message or thisother allows ID rating 2950, entry the of component; selection criteria for example, to identify a derived the error attribute events lookup to be rerated. table that These does events not are contain processed all the directly, possible without lookup the values needmay to assign have been them to defined. a file. An otherwise valid event might be treated as an error event because the lookup failed.





































all button. normalised The Assign/View events, error Existing events, Rerated and New charges File Search that were form fields and click the Creat e button. The Rerated File form closes. and generated Check by the that file. the The file original name chosen event file displayed is re-created closes, the error event is assigned tois the new file.in the(except for any corrupted events), and placed back in the input directory.





































unwanted rated and reprocessed events and file charges

purge to the unwanted events), if the unwanted come from duplicate charges already processed), they can be removed by running a selected date from normalised a specified events directory. andevents This can variety of sources. associated be used forcharges housekeeping. from the database. task of a schedule type:





































selection criteria to confine theand operation ofare the resulting task selected events. associated charges events, Any are error charges charges dependent charges events for without fordiscarded on the the the file, associated assigning value and and reofto a subset them tosubtotals. events re-calculated; rating creates are the ainfile. discarded original any error event rerating and re-calculated; filefile. (except in thethose file for listed of events. The criteria available each case areevents taken from any are also errorvary rerated. events events). the Theto file re-created are also is be used in Table 2–2 (the actualcorrupted criteria fromincase case), andfile may rerated. remains moved the theinput archive directory. directory. in combination to further refinetoin selection criteria.





































ENM as incorrectly process which defined rated during the events a certain is known period(provided of time. After just one correcting ENM the tariff, process had rerating been used all events to rate that all the used events the in wrong error), tariff thatduring ENM process that period is required. could be chosen.













































































































refercharges and to Chapter to produce 1, Introduction invoice information to Rating andand Billing invoice . The images outputfor of customers invoice images and customer to printersnodes. or other In output addition, devices this chapter using the describes General methodsProcess Output for checking (GOP) that is described invoice data in Chapter and images 4, Batch are Printing correct,. and for making any corrections that may be required.





































to produce node set up the occur the of success or possible before bill a batch run statements, orthe process, failure schedule ofbill customer run of which as types the iswell aborted. operation nodes can that asbe control can by used Ifperforming and errors later for the its quality be do quality duration. executed occur, a assurance bill of it run. the For on is process. only this bill The purposes runs particular ability For to for bill example, processing necessary or perform run. customer For the to separate multiple more revoke user information can information, customers, the billing review billing (for operations initial operations more refer the statistical invoices information, toallows Billon Run before the information Types user customer refer theto later tomajority easily Setting isnodes in recorded this configure of up that a for the billing chapter. customer each actually operation failed nodes process. (for and have more summarised For been example, information, processed; for thethe user refer ifoverall the can tofirst Correcting generate bill invoices run (for rental Billing contain more events Errors errors, without the information, later bill in run this producing can chapter). refer be to stopped. invoices. Tracking For Additional the more status information, operations of a bill runcan refer later also to inProcessing be this performed on existing bill runs. For more information, refer to Bill run operations chapter). later in this chapter.





































billing operations

Generation' customers that are b)passed Invoice on toa'Invoice bill toGeneration each run Image have bill run two Generation', operation common in parameters the turn. totalAfter number that identifying control of eligible how all the operations eligible customers c)customers Invoice is 1500 will Image and for be performed: the the Generation specified customer Customer operations, batch size Batch the is 100, Size customers then and the theare Number processing of prioritised is as follows: and grouped into batches of the specified size. The requested range of billing operations is then sequentially performed on each batch in turn.





































3.03 Operation processing set soon toor as 3,earlier then one Record. streams stream the versions. first This completes used 3 highest record Intoearlier process priority processing summarises versions the batches customers. aof the customer Convergent of results 100 Each customers batch, of the Billing, batch operation it will of thebe on the batch to customers allocated immediately processing ofis was customers, the starts processed three equivalent processing child and onto processes a appears all single the customers next stream. inand the available their Auditing being billing processed batch tab operations on inthe order as Bill part will of Run of priority. be a performed Specifying single batch a concurrently. on number a single of parallel-processing processing stream. streams can improve server utilisation and billing throughput. It can also minimise the impact of a certain customer batch stalling, due to the batch containing customer nodes that take a long time to process. If multiple parallel-processing streams are specified, other customer batches can be automatically started and completed while the long-running customer batch is still processing.





































status of a bill run

success operation orID, isfailure performed and the ofGeneration the quality on operation a set assurance ofRevoke customers. and its indicator duration. Theisresults passed For bill of to runs each the that Invoice/Statement invoices/statements operation interface. process batches on In each addition ofcustomer customers, to these, is the recorded biBillRunExecute& statistical and therefore information also passes provides is recorded the alist complete for Invoice/Statement Image audit of each root operation trail. customer Bill and run nodes. operations summarised For biBillRunExecuteForCustomer& can forbe the performed overall bill onrun. individual This , the statistical customers or onthen TRE information a specified returns is displayed group statistical ofoncustomers. the information Auditing Information on the operation, tab:





































TRE interfaces for each operation. All revoke operations are run by the EPM trerodb process, except 'Unapply Invoices', which is run by the trerwdb process. The primary server responsible for each operation is shown in the following table:





































of functions defines billing nodes. executed configuration Selecting the available to perform the and billing correct each operation configurations. billing of theto operations configuration the TRE There function configured ensures are three that for that is types a to the bill run.bill ofThree be billing called run uses steps configurations to invoke the areappropriate necessary it. The supplied user tofunctions. configure can with add Convergent customer For newexample, configuration nodes Billing: forfor a a bill runs: corporate 'Default', 'High mappings customer to theVolume BillingConfiguration withService', a large hierarchy, and table. 'Large Ifthe nothing Corporate corporate is billing Hierarchy'. added configuration to this table can be for selected the newtobilling ensure configuration, that the bill run the is operationsexecuted efficiently defined in using the 'Default' parallel processing. configuration will be used.





































for task inclusion that run, is aon not bills bill sent have run, to been the or task acustomer successfully part thereof andfor rated, for not apaid; specific and this anyinformation, customer corrupted can be used orrefer for off resources runs may aQA single reduce rating performance, immediately both the (for billing more processes and for normalisation quality hierarchy. error assurance purposes have been and corrected. quoting. concurrent to Chapter 6, users. Scheduling Ifevents possible, Server the Tasks bill ). run Several shouldbilling be runschedules when other for system demands different customers areor atgroups a minimum. of customers can be set up.





































month. help defined, relative to determine after to the the start task theof has outcome the been month. run, of aaIt bill message is run therefore schedule is received strongly andin are recommended a pop-up defined Example: Last Friday of month. window using that bill the (if runs Bill the user Run including Type is logged Definition rental on); generation ifthe the form. user is operations not loggedare on,run an email on the same notification basis, to avoid is sent potentially advisinginconsistent of completion calculation of the task. of the day number. This requires the selection of a Repeat type of 'Month Day' when defining the bill cycle schedule.







































Billing

The bill run type allows the user to specify the following for bill runs using this specific type: •

Quality Assurance flag, which indicates whether the bill run is used for quality assurance purposes or not.

•

Bill Run Validation, which specifies the entity validation that is used to configure the display of the general statistics for all bill

•

Operation Validation, which specifies the entity validation that is used to configure the display of the general statistics for all bill run operations associated with bill runs of this type.

•

Currency, which indicates the currency in which billed or revoked amounts are stored for bill runs of this type (and bill run operations associated with it).

•

Summary Function, which specifies the function that is used to summarise the current state of a bill run after the current task or

•

Supported Tasks, which is the list of schedule types that can be performed on bill runs of this type. Only these tasks will be displayed on the list of available operations in the Perform Operation window (accessible from the Bill Run Detail or Customer Bill Run Detail f o r ms ).











































Billing

Bill run

Important schedule parameters for new bill runs include: •

Bill Run Type

Refer to Bill Run Types earlier in this chapter. •

From Operation and To Operation

These two codes specify the range of operations which are to be executed for the bill run. •

Customer Batch Size, and Number of Child Processes

Refer to Processing Operations earlier in this chapter. •

Error Thresholds

The bill run will fail if the total number of customers with errors equals or exceeds this parameter. •

Where Clause

Allows a refining of the selection of customers (to be processed)

CUSTOMER_NODE_TRE_V.BILLING_PRIORITY and then by CUSTOMER_NODE_TRE_V BILLING_CONFIGURATION_CODE.

Modifying a bill run

Once a bill run is set up using the Schedule Definition form, any

A bill run schedule that was set up using the One-off Task Definition

Once a bill run is actually executed, the details cannot be directly modified. Additional operations can however be performed later (refer to Performing an operation on a bill run later in this chapter).

Performing an

Additional operations can be performed on existing bill runs for either a batch of customers or for a single customer: •

To perform an operation on a batch of customers, select the Perform Operation… button from the Bill Run Detail form to display the Perform Operation for Bill Run form.

•

To perform an operation for a single customer, select the











































Billing

Both of these forms list the bill run operations that can be subsequently

Stopping a bill run

A bill run that is in progress can be stopped by entering the appropriate expression, including the function biBillRunStop&(), in the Expression Test form. To stop a bill run: 1.

Select the Server Tasks ➩ Bill Runs option. The Bill Run Search form is displayed.

2.

Enter the appropriate search criteria and click the Search… button. A list of matching bill runs is displayed in the Bill Run List f o r m.

3.

Select the appropriate bill run and click the Details… button. The Bill Run Details for Bill Run form is displayed.

4.

Note the bill run ID, last modified date, and the task ID (this information is used to stop the bill run).

5.

Select the Maintenance ➩ Data Definition ➩ Expression Test option. The Expression Test form is displayed.

6.

Enter biBillRunStop&() in the Function Name field.

7.

Enter the appropriate expression to stop the bill run in the Expression field. For example: {

return biBillRunStop&(lBillRunId&,

} 8.

Click the Evaluate button. The result of the expression is displayed in the Results field.

When all processes have stopped, all operations with a status of 'Running' are changed to a status of 'Error' and the bill run is updated.











































Billing

Revoking a billing task

A bill run operation or task, which has already been executed in a

Operations window can be used to revoke individual operations. For more information, refer to Performing an operation on a bill run earlier in this chapter.

Checking the results

Information on the results of a bill run is displayed on the Bill Run Detail

Results for an individual customer node can be viewed by clicking the Bill Run Details… button (Billing tab) on the Customer Detail form. Techniques for correcting bill run errors are provided in Correcting Billing Errors later in this chapter.

Invoice Data and Images To view invoice data and images for a customer account: Select the Accounts ➩ Invoices option. The Invoice Search 1. form is displayed. 2.

Enter the appropriate search criteria and click the Search…

3.

Double-click on the invoice in the list with an issue date matching the bill cycle. The Invoice Detail form is displayed.

4.

Select the Transactions tab to view adjustments and payments that have been received since the last invoice.

5.

Select the Images tab and click the Invoice Image… button to

Display Types for Invoice Images Convergent Billing offers the ability to view different types of invoices











































Billing

Output Image Type

Display Image Type

.txt

txt

.txt.Z

txt

.txt.gz

txt

.pdf

pdf

.xml

xml

.xml.gz

xml

.xml.Z

xml

Producing and checking appropriate reports Billing reports are defined for the installation of Convergent Billing. For more information, refer to the Reports Guide.

Suppressing

There are two possibilities for invoice suppression: •

Suppress invoice generation in bill runs for particular customers. It is possible to suppress invoices for individual customers,

Customer Details f o r m. Invoices are suppressed for a specific type of customer using the Customer Type f o r m. Invoices for customer groups or hierarchies are handled using a

Customer Type f o r m. •

Automatically suppress certain types of invoices. Invoices can be suppressed based on calculated invoice values.

For more information on configuring invoice types, refer to the System Administration Guide.













































Billing

Correcting Billing Errors This section describes the techniques used to correct any errors that may arise as the result of bill runs. When creating bill runs, the number of errors permitted before the bill run is stopped can be specified on the Schedule Definition or the Oneoff Task Definition form in the Error Threshold parameter. If a bill run results in the specified amount of errors, the errors can be fixed, the

Once errors are generated, or a bill run schedule has failed, the following must be done: 1.

View the Bill Run Detail form for the particular bill run and

2.

If no operations failed, but the bill run results are in error, determine at which point in the operations the error occurred.

3.

Revoke any operations that succeeded that were in error.

4.

Correct the problem.

5.

Complete the bill run.

The flow chart in Figure 3–2 summarises the process of correcting any











































Billing

Run a Standard Bill Run schedule

Check schedule status Complete the Bill Run

Did schedule fail? Check schedule

No

Schedule post-billing reconciliation reports and reconcile billing output

Yes View Bill Run Details

Revoke the operation in

Yes

Billing details OK?

No

End Rated Billed charges incorrect

Correct Tariff/ Subtotal/Customer details

Reason for incorrect details

Invoices not printed

Invoice

Correct printing problem

Fix invoice templates

Complete the Bill Run

Figure 3–2 Billing Error Flow Chart

Correct tariffs and re-rate appropriate events











































Billing

Billing Schedule Types Table 3–1 lists the schedule types that are available for billing tasks, for an entire bill run, with a brief explanation of each.

Table 3–1 Billing Schedule Types for Bill Runs Name

Function

Apply & Allocate Invoices

Applies invoices to the appropriate

Apply Invoices

Applies invoices to the appropriate customer accounts for a specific bill run.

Complete Bill Run

Completes a standard bill run, QA run, or

Generate Invoice Images

Generates invoice images for a specific bill run.

Print Invoices

Prints invoices for a specific bill run.

Revoke Bill Run

Revokes a standard bill run, QA run, or part thereof.

Revoke Invoice Images

Rolls back invoice images in the database.

Revoke Invoice Print Revokes the ‘Printed’ flag, so that the Settings batch can be printed again. Revoke Invoices

Rolls back all invoice data and images associated with the specified billing task.











































Billing

Table 3–2 lists the schedule types that are available for billing tasks, for individual customers, with a brief explanation of each.

Table 3–2 Billing Schedule Types for Individual Customers Name

Function

Apply & Allocate

Applies invoices for a specific customer

Apply Invoices for Customer

Applies invoices for a specific customer.

Complete Bill Run for Customer

Completes a standard bill run, QA run, or

Generate Invoice

Generates invoice images for a specific customer.

Print Invoices for Customer

Prints an invoice for a specific customer.

Revoke Bill Run for Customer

Revokes a bill run for a specific customer.

Revoke Invoice

Revokes invoice images for a specific customer.

Revoke Invoice Print Clears the print settings for a specific customer. Revoke Invoices

Revokes invoices and images, but keeps rental events, for a specific customer.











































Billing

Table 3–3 lists the schedule types that are available for related billing tasks with a brief explanation of each.

Table 3–3 Related Billing Schedule Types Name

Function

Apply Transactions

Applies future dated payments and adjustments.

Billing Suppress

Suppresses invoice generation for

Billing Unsuppress

Halts suppression of invoice generation.

Dunning Letter Generation

Allows creation of dunning letters for

General Bulk Output Runs the General Bulk Output Process for by Task a specific task. General Bulk Output Allows invoice or letter images to output to Process a printer or other output device. Refer to Chapter 4, Batch Printing. Invoice Reprint Generation

Generates new invoice images for

Invoice View Image Used internally by Convergent Billing for viewing invoice images on request. Quality Assurance Bill Run

Creates and executes a QA bill run for a

Revoke Rental

Revokes rental events.













































Billing

Billing of Customer Hierarchies Each customer node is assigned a reporting level, which can be one of these values: •

Invoice

•

Statement

•

None.

Invoices are produced for every node in the billing schedule with a

Nodes with a reporting level of 'Statement' receive a statement of charges incurred by that node only. Displayed invoice or statement details are almost completely configurable using the parameters of the biInvoiceReportAccount&() function (which is called in the generation of an invoice or statement image). Note: The root customer node can only have a reporting level of 'Invoice'.

The following example shows the effect of reporting level on invoice and











































Billing

Table 3–4 Node Details Node

Type

Parent

Reporting Level

ABC Banking

Root

East Branch

Child

ABC Banking

Statement

West Branch

Child

ABC Banking

Statement

Central Branch Child/ Parent

ABC Banking

Invoice

Loans

Child

Central Branch None

Investments

Child

Central Branch Statement

Invoice

The billing implications of this hierarchy are: 1.

ABC Banking (the root node) receives an invoice for its own charges, and those for East Branch and West Branch.

2.

Central Branch receives an invoice for its own charges, and those for Loans and Investments.

3.

East Branch, West Branch, and Investments receive statements of their own charges.

4.

Loans receives nothing.











































Billing











































Chapter 4 Batch Printing

This chapter describes the General Output Process (GOP) and how it

It also describes dunning letters (with its configuration) and how to set up

Scheduler • Output Device, which defines the commands used by the server to direct the output to the required printer or other device. •

Output Method Type, which defines the location in the database











































Batch Printing

Invoice Output using the Scheduler The following schedule types can be used for the output of invoices or dunning letters using a schedule or an immediate task: •

General Bulk Output Process Generates bulk output for a previous schedule (bill run, dunning generation, or invoice re-print).

•

General Bulk Output By Task Runs the General Bulk Output Process by task ID.

•

Dunning Letter Generation Generates dunning letters for particular customers. Dunning letters are used to remind customers about unpaid accounts.

By using a schedule, a task can be run at specified intervals; an

GOP schedule

The GOP requires these schedule parameters for the schedule types 'General Bulk Output Process' and 'General Bulk Output by Task': •

Schedule to output (General Bulk Output Process)













































Batch Printing

•

Percentage Unpaid (%) Unpaid percentage of the total sum due that is required to trigger a dunning letter; this can be used in combination with the Days Overdue parameter.

•

Days Overdue Number of days the sum is overdue and which triggers a dunning letter; this can be used in combination with the Percentage Unpaid (%) parameter.

•

Extension File extension for the output file used when creating the report.

GOP schedule processing

The GOP retrieves all the document images stored in the database by the













































Batch Printing

If the criteria table is empty (that is, if the output is treated as a single

Invoice Output using a Bill Run The General Output Process is able to print images generated by previous

The numbers of customers for whom invoices are printed is determined













































Batch Printing

Parallel processing between separate report, invoice, and statement images is supported. Parallel processing within a single report, Note:

MAX_CHILD_PROCESSES attribute. However, other invoice and

statement images can be generated at the same time.

Setting up a bill

Bill runs are set up using the Scheduler. Several billing schedules for different customers or groups of customers can be set up. A new bill run schedule (that is, not completing an earlier run) uses one of the following supported schedule types: •

Standard Bill Run, which generates an invoice that is sent out to customers. The Custo

e Batch Size (a bill

eter) o t ols













































Batch Printing

The graphic below displays the window for performing additional operations on a bill run.













































Batch Printing

Printing Document Images This section describes the steps required to prepare for printing and checking the output.

Preparation for printing

The following conditions should be met before billing output can begin (each site may have additional requirements): •

The number of documents awaiting output is established. This information can be obtained from the Results tab of the Task Detail form for the task that generated the document images.

•

Required reports are produced and analysed, and any problems rectified.















































Batch Printing

•

Do selected documents match the data in the database?

•

Are there any extra procedures required at this stage? If so, have they been carried out successfully?















































Batch Printing

Table 4–1 Singl.eView Convergent Billing Output Method Types Name

Description

Print invoices

Print invoices from an invoice run. Updates the INVOICE table.















































Batch Printing

Table 4–2 Pipe and Concatenate Options Option Selected Result

Concatenate

The Run command is executed after all















































Batch Printing

Output device examples

Example 1: PostScript output through Samba to printer















































Batch Printing

Note: The only Convergent Billing output file format that can be concatenated is .txt.

Example 3: Images piped to the null device using cat

















































Batch Printing

















































Batch Printing

















































Part 2

















































white text

























































































































































































































specified control intervals, ofto or the run tasks Scheduled thethat schedule. run Task only Dispatcher Ifonce, an instance either (STD) immediately is not process specified, and or at the the a date Task schedule and Launch time is runchosen. onand theMonitor default Once set instance (TLM) up, these process. defined tasksThe for runthe client automatically Scheduler. workstation's at (The the scheduling default chosen features time instance without are is defined used further toincontrol intervention, the STD these Configuration processes, and then notify Item.) collectively the user referred on completion. to as the









































one or more tasks that are queued until the date and time specified, when they run automatically. On completion of each task, a message is sent so the user can verify that the task executed successfully.









































'Complete'. to instance creates example, time create, on tasks which name, ifthe the Ifas program the the schedule tasks required; last schedule associated date that calls ais the is complete not for submitted, schedule with adefined, task the schedule attasks schedule then the monthly schedule the runs, is effectively first can intervals what be task continues run parameters runs turned with on aa specific preoff,are required, instance and schedule immediately. indefinitely. cannot of count and Convergent create similar of five, tasks. information then Billing. five If tasks (for an instance are more created information, is not when specified, the refer schedule to theChapter task is is run on the default submitted. A new task instance is generated defined for whenever the Scheduler. the earliest The one default completes, instance the keeping is defined numberinofthe advance STD Configuration tasks at five, Item. until the Thelast Instance date isName reached. field will be enabled only if the reference type ATA_INSTANCE contains more than 2 rows.







































database, information repeat this is the used typedepending same of in from Month conjunction asthe the Day on database; first the and with date processing a repeat for the (unless example, defined unit required the ofrepeat first 2a means billing date byunit the that task has (task. ntasks already in may the For are befollowing the passed first required scheduled examples). when task inthe the to schedule every schedule, run The in repeat two early is months. this submitted, types September, is the available same when but asare: the using thetask schedule's the starts dataimmediately); for effective August. date; In this st August . schedule's case, the effective thereafter, the task firstdate date effective would and date the be repeat set is controlled to 31 factors by control the the start date. effective date and the repeat factors.







































frequency of a schedule

are schedule start was pending installed. date.orWhen one for Before the that the old can STD afrequency. new be receives modified schedule To theto is minimise re-submitted defined, fit requirements. the check number task, whether it Schedules of finds pending there that is are the defined, start tasks an existing date andmaintained, prevent is schedule in thecomplications, past, and or and one modified therefore that use can using abe schedules preschedule the modified Schedule the tocount Definition fit new requirements. task of 1 form. immediately. when defining schedules.







































tasks will also be deleted. All tasks must be completed before deleting the schedule.







































validation, required for the definition of user parameters (forthe Billing and how base to run installation, it. The schedule including typethe also server defines command the parameters that thethat task more refer to the Customer Care Configuration user needs executes, and toinformation, provide any parameters when a schedule required. ofItthis alsotype provides is defined. information on defining new schedule types.







































base installation; reportpart schedule types are included (for more Invoices for allocates and customer allocates thereof credit hierarchies, that credit payments hasnot payments previously causing and and these been Customer on these, refer adjustments. hierarchies interrupted, to failed, be skipped or revoked revoked. for a information to the Reports Guide ). by schedules running customer. specific types such as 'Complete Bill Run'.





































Images for Customer

customer (bill set supported of ofrun, customers invoices. dunning hierarchy format The associated for generation, passes GOP the source must with theor be BGP afile invoice given run on performs re-print). a specified schedule. separateby on schedule the the Invoice specified to re-print ID.customers. the invoices.





































Settingsfor Images for Customer

the specified normalised specification real-time events, and rating event charges schedule, of all feeds file AUDIT_TABLE for that that soathat file. file, were usethe and The rating entire file successfully configuration subtotals. remains replaces bill run can in the the be rated. file items. archive printed in the data again. directory. directory.





































Deallocate (keep Rentals) Invoices for Customer for Customer

system, bill assigns adjustment run for all otherwise normalisation the amount specified accounts for abill specific error may cycle events be schedule.incorrectly. associated customer. updated with it.





































arrays for services orany customer services nodes or customer that need them. that nodes Onlyneed needs them. to beOnly run ifneeds new to be charge run if new categories derived are attributes assigned aretoassigned products to products that that areare in use. in use.





































Billing base installation; report schedule types are not described (for more information on these, refer to the Reports Guide).





































withoperation this root customer errors. The is nodes being bill run to bewill fail performed. processed once it reaches by a single or exceeds process thisat any given time. number.





































Invoices for Customer

which this operation this operation is being is being performed.





































withoperation this root customer errors. The is nodes being bill run to bewill fail performed. processed once it reaches by a single or exceeds process thisat any given time. number.





































which this thisoperation operationisisbeing being performed.





































invoice able to re-calculate and RT allocations multi-currency aretransactions performed transactions automatically. Multi-currency exchange Currency are tousing havecurrent their Transactions and allocations rates. payment transactions having amounts associated payment itemsreare NOT recalculated, based on the current inserted under these conditions. exchange rates. Otherwise, set to ‘No’.





































duplicate data?

archive data updated before before a commit. starting If this not specified, the commit is on a archive. table-by-table basis.





































customer hierarchies, causingform these hierarchies to be skipped Node Type which or more ofinvoice an customers services prime SQLgeneration account accounts WHERE with with a names network name a clause ofwill name node thisbeby Name suppressed. type type. matching name name matching thethis matching WHERE this keyword), pattern. this name. schedules using types such as(minus 'Standard Billpattern. Run', 'Quality Assurance based on the Bill Run', and 'Complete Bill Run'.





































Bill Cycle Count', should be specified, in order to determine when invoice generation should recommence. If both parameters are entered and they do not match, the date parameter will be taken as default.





































Node Type Name

form or more of an customers services prime SQLaccounts account WHERE with with a names network name a clause ofnode name this type name type. matching name (minus matching thethis matching WHERE pattern. this keyword), pattern. this name. based on the





































Child processes

formoperation this root with customer errors. of an SQL The lies nodes WHERE bill outside run to be clause will of the fail rangeitofreaches processed once (minus the the by WHERE 'To' a single or and exceeds keyword), 'From' process thisat operations, any number. using given fields time. then from only the customer nodes for this bill run which have successfully completed this operation (taking into account any revoking) will be eligible.





































Run for Customer

or part thereof that has previouslywhich been this interrupted, or revoked for operationfailed, is being a specific customer on a bill run. performed.





































Expired Notification Contracts? Function

ignore before contract notification task fails. messages If this are generated. is not entered, the parameter script will stop on the first error encountered. If no message is generated, no update will be performed for that contract (including cancellation where a message function has been specified).





































date passed Notification remote functions Function, to thewith script. or an Expiry application The exception Notification environment is setting Function of 'Any', the reminder a parameters context dates and of determining 'Any', mustand be specified. take if athe re-reminder following is parameters: necessary, these are done using the current date and time. When updating a contract to cancel, the status is set to 'Cancelled' and the





































scripts. If the environment is configured appropriately, (for example, the ATA_PARTITION environment variable is set to a non-zero value) this includes generating the SQL to create the set of partitions specified by this script.







































Schedule Types

Notes For the partitions to be created, or recreated in the database, dbsync

can then be imported into the newly created set of

partitions.

Sizing and tablespace information for these partitions and their associated indexes is specified in $ATA_DATA_SERVER_CONFIG/ata_create.db. This script is mainly designed for use on new database installations,

The last partition is deliberately not given an end date of the end of time











































Schedule Types

DIL Validation

This schedule type validates Data Interface Language (DIL) definitions.

Server command dil

Schedule Type Parameters None.











































Schedule Types

Dunning Letter Generation

This schedule type generates letters for customers with overdue invoice Task' type.

Server command dunning

Schedule Type Parameters Parameter

Type

Description

Dunning Template

List

TEX template used for building the letters.

Percentage Unpaid (%)

[Integer]

Unpaid percentage that triggers the letter generation.

Days Overdue [Integer] Number of days overdue which triggers the letter generation. Extension

List

Select a file extension for the











































Schedule Types

ECP Command

This schedule type executes an expression.

Server command ecp_cmd


Type

Description

Expression

Text

Expression to be executed.











































Schedule Types

Explain BGP

This schedule type generates an explanation of the customer hierarchy passes the BGP performs on the specified customer.

Server command bgp_explain


Type

Description

Bill Cycle Schedule

List

List of all current billing cycle schedules.

Customer Node Name

Text

Name of the customer in the pass.













































Schedule Types

Full Database Validation

This schedule type runs the full database validation process.

Server command dvp












































Schedule Types

General Bulk Output By Task

This schedule type runs the General Bulk Output Process for a given task.

Server command gop -q


Type

Description

Task

Integer

Task ID that specifies the entities requiring bulk output.

Output Method

List

Specifies the output method,

Directory for temporary data

Text

Directory to store temporary











































Schedule Types

General Bulk Output Process

This schedule type generates output for a given previous schedule (bill run, dunning generation, or invoice reprint).

Server command gop


Type

Description

Schedule to output

List

Schedule from which to select the last successful task for output.

Output Method List

Output method to use (refer to Chapter 4, Batch Printing).

Directory for Text temporary data

Directory to store temporary data and working files.











































Schedule Types

Generate Invoice Images

This schedule type generates invoice images for a specific bill run.

Server command bill_run_wrapper –c 40 40 40


Type

Description

Bill Run Id

Integer

Identifier of the bill run for which

Customer Batch Size

Integer

Maximum allowable number of

Number of Child Processes

Integer

Number of child processes to handle the customer batches.

Error Threshold

Integer

Maximum number of customer











































Schedule Types

Generate

This schedule type generates invoice images for a specific customer on a bill run.

Server command bill_run_cust_wrapper –c 40 40


Type

Description

Bill Run Id

Integer

Identifier of the bill run for

Customer Node Id Integer

Identifier of the customer for













































Schedule Types

Invoice Generate Image

This schedule type generates the invoice image for a single invoice.

Server command generate_image


Type

Description

Invoice Identifier

Integer

Invoice ID needed as the argument

Sequence Number

Integer

Sequence number.











































Schedule Types

Invoice Print Image

This schedule type prints or reprints the image of a single invoice.

Server command print_image


Type

Description

Invoice Identifier

Integer


Sequence Number

Integer

Sequence number.

Output Device List

Output device (printer).











































Schedule Types

Invoice Reprint Generation

This schedule type generates the data required to reprint a set of invoices,

Server command dunning -r












































Schedule Types

Invoice View Image

This schedule type generates the viewing image file in any supported

Server command ivp


Type

Description

Invoice Identifier

Integer


Number

Integer

Sequence number.

Output Image Type

List

Output Image Type.











































Schedule Types

Partition Maintenance

This schedule type runs the Table Partition Maintenance schedule.

Server command update_partitions


Type

Description

Archive Directory

Text

Directory in which archived files are placed.

The update_partitions script is used to update a set of partitions in SCHEDULE_ID associated with, an

Partitions with a REQUIRED_OPERATION_CODE specified have that REQUIRED_OPERATION_CODE is cleared on completion.

Partitions with a DESIRED_STATUS_CODE different from their ACTUAL_STATUS_CODE and aDESIRED_STATUS_CODE of 'Dropped' require the following steps to be performed:













































Schedule Types

•

If this partition does not have the highest TO_CHARGE_START_DATE, then a Split Partition command is generated for the next partition with a value equal to the DESIRED_TO_CHARGE_START_DATE of the current partition. If the partition is the last, then an Add Partition command is generated.

•

The contents of the old partition are imported back into the table.

•

All local indexes on the split partitions (or added partition) are

•

The actual dates and status are set to equal the desired dates and status.

The dbrebuild script is executed to regenerate the partition definition scripts. If the environment is configured appropriately, (for example, the ATA_PARTITION environment variable is set to a non-zero value) thi will include generating the SQL to create the set of partitions as specified













































Schedule Types

Print Invoices

This schedule type prints invoices for a specific bill run.



Type

Description

Bill Run Id

Integer

Identifier of the bill run for which

Customer Batch Size

Integer

Maximum allowable number of













































Schedule Types

Print Invoices for Customer

This schedule type prints invoices for a specific customer on the bill run.

Server command bill_run_cust_wrapper –c 70 70


Type

Description

Bill Run Id

Integer

Identifier of the bill run for

Customer Node Id Integer

Identifier of the customer for













































Schedule Types

Purge Error Events

This schedule type purges normalisation error events, using selection criteria.

Server command reprocess_bulk_assign –p


Type

Description

ENM Process

[List]

ENM process used to process the purged events.

Native File Type File Process Start Date

[List] [Date]

Normalised event file type used to purge the events. Earliest file processing date for selecting files.













































Schedule Types

Parameter

Type

Description

Event Where Clause

[Text]

SQL WHERE clause on the

File Where Clause

[Text]

NORMALISED_EVENT_ERROR t able

to select events to be purged. SQL WHERE clause on the

NORMALISED_EVENT_FILE table to

select events to be purged.















































Schedule Types

Purge Events (non Error)

This schedule type purges normalised events using selection criteria.

Server command reprocess_bulk_assign –n –p

Schedule Type Parameters















































Schedule Types

Purge Files

This schedule type deletes specified files older than the task's effective date from a given directory.

Server command purge_files















































Schedule Types

Quality

This schedule type creates and executes a quality assurance bill run for a set of customers associated with a given schedule.

Server command bill_run_execute -q















































Schedule Types

Rate Files

This schedule type rates files in an ENM's data directory that are older than the task effective date.

Server command rate_files















































Schedule Types

Re-analyze tables

This schedule type recomputes optimiser statistics for all tables.

Server command dbanalyze

Schedule Type Parameters

















































Schedule Types

















































Schedule Types

















































Schedule Types

















































Schedule Types

















































Schedule Types

















































Event File Name

















































































Reference Type (RRRT)

and generates derived information about it into a number of other tables. This derived information is used to display summary of change details about CSR entities, and by certain reports such as the Call Detail Display









































reports with that are have the a charge how associated specified this the many specified error startchargeable error date with message events files on orthat wouldthis commenced completed after before party identifier. normalised identifier. have this date. processing date. event been processing processed type.ononoror instead after before this this ofdate. reprocessing date. all









































a charge events that start candate be reprocessed. after this If the amount of error events date. based on the above selection









































have reports are charge the specified associated the start start how specified date many chargeable date with on normalised on events, or files orafter before party that this charges, commenced completed date. this identifier. event date. type. accounts, processing processing andon services onoror wouldthis after before have this date. date. been processed instead of reprocessing all qualifying events.







































that can be reprocessed. If the amount of error events based on the above selection criteria exceeds the specified number, they will not be processed.







































Adjustment' a part thereof. and The the Revoke To Operation Billform Runoperation parameter schedule type could allows set the to operator 'Apply Child this customer with errors. of annodes SQL The lies WHERE to operation outside be be processed clause ofwill the fail to Processes range by if (minus itathe reaches single of the theWHERE process or 'To' exceeds and at keyword), 'From' any this given specify Invoices'. which This operations would mean within that the specified operations bill run 'Rental need event to be generation revoked. operations, time. number. using fields then fromand only the'Invoice/Statement customer (RGP)', 'Invoice/Statement generation (BGP)', nodes forrevoked. this bill run which have Image generation (IGP)' would also be failed or are not yet up to this specified operation will be eligible.







































b) failed a revoke operation corresponding to the ToOperation, or c) are not yet up to the ToOperation, but have completed operations







































Adjustment' a part thereof, and forthe a specific To Operation customer parameter onthis a bill could run. be The set Revoke to 'Apply Bill Run which operation is being performed. for Customer Invoices'. Thisschedule would mean type that allows the the operations operator 'Rental to specify event a specific generation customer, (RGP)', 'Invoice/Statement in addition to thegeneration operations(BGP)', within the and specified 'Invoice/Statement bill run need to be revoked. Image generation (IGP)' would also be revoked.







































events, and charges associated with the file. The file remains in the Event File Name directory, and the unbilled amount of any accounts associated archive with the revokes changes is the updated.





































events, and charges associated with the file. The file is moved to the data Event File Name directory.





































Child Processes

errors. The customer nodes bill run to be will processed fail onceby it a single process reaches or exceeds at any thisgiven number. time.





































Images for Customer

which this operation is being performed.





































Child Processes






































Print Settings for Customer

the print setting for all invoices on theThe specified that Child customer errors. nodes bill run to schedule be will processed fail so once by it the Processes aagain. single process or exceeds at any thisgiven number. time. entire bill run can be printed reaches





































need to be run as well (for example, Unapplying Theby Child customer errors. The nodes bill run to Invoices). be will processed fail once it Processesof using the Revoke a single reaches process orschedule exceeds at any thisgiven number. time. advantage Invoices type is that all revoke operations are specified in one step.





































Child Processes






































(keep Rentals) for Customer






































needrental and to be adjustments, run as well (for forexample, a specific Unapplying customer on Invoices). a bill The For which this operation is run. being performed. example, itof advantage deletes using all theinvoices Revoke generated Invoices for inCustomer the last bill schedule run in the type is specified that all revoke bill cycle operations schedule are for specified the specified in onecustomer. step.





































Child Processes






































Events for Customer






































Reprocessed File





































perform kept that the the isscript’s table kept partition in before themaintenance table being the specified data .inThe three major optimiser. archived. before being sorted. archived. This tasks are: parameter is ignored if the affected data is also set to be 'dropped'.





































either all dropped partitions are updated, or a partition is updated with a DESIRED_TO_CHARGE_START_DATE greater than or equal to the effective date.





































unusable covers during the load. , then This an should error isbe output performed and all automatically changes are by rolled back. when run in direct mode. It can also be performed manually SQL*Loader for a partition by using the Partition Maintenance form to update the status of a partition. This improves performance if the import command (imp) is used to import data into a new partition. If an import is applied across multiple partitions (or the entire table), then the ata_dropcit command can be used to drop all indexes on the table prior to importing the data. In this case, dbsync should be used to recreate the indexes.





































Child Processes

form errors. customer with of annodes SQL TheWHERE to bill berun processed clause will fail by a single once (minus it reaches the WHERE process or exceeds at keyword), any given this time. fields from the number. using





































the specified directory to <filename> YYYYMMDD where YYYYMMDD is the task's effective date.





































Deallocate Invoices

Child Processes






































Invoices for Customer

Child Processes








































Schedule Types

UnApply Invoices

This schedule type un-applies invoices for a specific bill run; the invoices must already be de-allocated.



Type

Description

Bill Run Id

Integer

Identifier of the bill run for which this operation is being performed.

Customer Batch Size

Integer

Maximum allowable number of root

Number of

Integer


Error Threshold

Integer

Maximum number of customers with











































Schedule Types

UnApply Invoices for Customer

This schedule type un-applies invoices for a specific customer on a bill run; the invoices must already be de-allocated.



Type

Description

Bill Run Id

Integer

Identifier of the bill run for which this operation is being performed.

Customer Batch Size

Integer

Maximum allowable number of root

Number of

Integer


Error Threshold

Integer

Maximum number of customers with











































Schedule Types

Unarchive

This schedule type unarchives selected tables and other data.

Server command client_unarchive


Type

Description

Archive file name

Text

Name of the archive import file.

Import buffer size (in bytes)

Text

Changes the default Oracle import buffer size (in bytes).

Report missing [List] data?

Select 'Yes' to report and view the missing data.

Unarchive mode

[List]

Select the mode for handling existing data during unarchiving.

Archive Format

[List]

Select the archive data format.

Other archive flags

Text

Any other archive flags not supported by prompts.











































Schedule Types

Update Account Unbilled

This schedule type validates and updates the unbilled amount of an account. This script should only be run when there is no rating activity on the system; otherwise, the account may be updated incorrectly. Note:

Server command update_unbilled_account


Type

Description

Account Number

Text

Account number to update.

Notes If an account is specified, then the unbilled amount of that account is

Validation of an account involves examining all charges that reference account_aggregate_ind_code = 1. This summed charge total is

then compared to the account unbilled amount. If the amounts differ then the account unbilled amount is updated by that difference. After the database changes have been committed, all updated accounts are purged from the account cache.











































Schedule Types

Update Charge Categories

This schedule type generates new charge categories for any services or

Server command update_cc














































Schedule Types

Update Invoice Unbilled

This schedule type validates and updates the unbilled amount of an invoice.

Server command update_unbilled_invoice


Type

Description

Invoice Number

Integer

Invoice number to update.

Notes If an invoice is specified in the invoice number parameter then the

Validation of an invoice involves examining all charges that reference

account_aggregate_ind_code maintains a running total of all

unbilled charges for an account. These charges will not include billing

When the invoice is applied to the account, the unbilled amount in the account table is decremented by the unbilled amount in the invoice table. This script only needs to be run if the charge has a tariff with the Add Charges to Account in Real-time? check box selected. If this script is











































Schedule Types

Update Lists

This schedule type generates new empty derived attribute arrays for any

Server command update_list


Notes A check is done in three parts. 1.

A check is done for each product; all customers, customer nodes,

2.

All customers and customer nodes are checked to ensure they have all the derived attributes required by their customer type.

3.

All services are checked to ensure they have all the derived attributes required by their service type.











































Schedule Types

Verify Charge Partition

This type verifies that the UNINVOICED_IND_CODE (indicating whether uninvoiced charges exist in the CHARGE table) is correct in the ATLANTA_TABLE_PARTITION table for all charge table partitions w a calculated date range. The calculated starting date is the schedule's effective date minus the

If there are no longer any uninvoiced changes left in the partition, the UNINVOICED_IND_CODE is cleared. Because the biller automatically uses this code (no flags need to be set) to check which charge table

Frequency of usage for this schedule type depends on the bill cycle and

Server command update_partitions_uninvoiced -n


Type

Description

No Of Units

Integer

Number of units to use in the date range calculation.

Units

List

The type of units to use in the

Notes For each partition found, this function:











































Schedule Types

Verify Charge Partition Range

This type verifies that the UNINVOICED_IND_CODE (indicating whether uninvoiced charges exist in the CHARGE table) is correct in the ATLANTA_TABLE_PARTITION table for all charge table partitions w the specified start and end dates.

If there are no longer any uninvoiced changes left in the partition, the UNINVOICED_IND_CODE is cleared. Because the biller automatically uses this code (no flags need to be set) to check which charge table

Frequency of usage for this schedule type depends on the bill cycle and

Server command update_partitions_uninvoiced


Type

Description

Start Date

Date

Start date of the range to verify.

End Date

Date

End date of the range to verify.

Notes For each partition found, this function: •

Checks the CHARGE partition for any uninvoiced charges

•

Updates the

ATLANTA_TABLE_PARTITION.UNINVOICED_IND_CODE as

required •

Outputs a message to advise the date and time of completion of the task, with notification of any uninvoiced charges.











































Index

Account cache 1-8 Apply Invoices 7-10 Apply Invoices for Customer 7-11 Apply Transactions 7-12 Apply&Allocate Invoices 7-8 Apply&Allocate Invoices for Customer7-9 Architecture billing and rating 1-3 billing engine 1-14 Convergent Billing 5-2 rating engine 1-7 Archive schedule types 7-13 Balance Management concept 1-5 Batch Printing 4-1 BGP (Bill Generation Process) 1-16 BGP Hierarchy Passes explanation 7-26 Bill Generation Process (BGP) description 1-16 steps in billing 1-16 Bill Run configuration 3-7, 3-9, 3-10, 3-11 correcting errors 3-15 customer batch size 4-5 Customer Batch Size 3-3 INVOICE_PRINT 4-4 modifying 3-11

schedule parameters 3-11 schedule type 3-8 server processes 3-6 set up 3-8 status of 3-5 stopping 3-12 task type 3-8 tracking 3-5 types 3-9, 3-10 Billing architecture 1-14 correcting errors 3-15 overview 1-14 performing a bill run 3-8 schedule types 3-17 Billing Processes Bill Generation Process (BGP) 1-16 customer hierarchies 3-20 General Output Process (GOP) 1-18 Invoice Generation Process (IGP) 1-17 overview 3-1 Rental Adjustment Mode (RGP) 1-16 Rental Generation Program (RGP) 1-15 trerodb 1-17 trerwdb 1-17 Billing Schedule Types for bill runs 3-17 for individual 3-19 for individual customers 3-18













































Index

Complete Bill Run 7-17 Complete Bill Run for Customer 7-18 Configuring bill run customer 3-7 Context-sensitive Help xii Contract Cancel/Notify 7-19 Conventions document ix Convergent Billing architecture overview 5-1 Convergent Billing Architecture three-tier 5-2 Convergent Billing Processes Balance Management 1-5 Bill Generation Process (BGP) 1-16 Event Normalisation (ENM) 1-9 Event Rating (ERT) 1-6, 1-10 Event Rating Broker (ERB) 1-7 Event Rating Output (ERO) 1-11 General Output Process (GOP) 1-18 Invoice Generation Process (IGP) 1-17 rating errors 1-12 recurring charges 1-13 rental adjustment mode (RGP) 1-15 Rental Generation Program (RGP) 1-15 trerate 1-5

schedule DIL Validation Document Images printing Dunning Letters generating Duplicate event checking ECP Command

6-6 7-23 4-7 4-2, 7-24 1-10, 1-12 7-25

assigning to rerating file 2-11 correcting 2-9 re-rating 7-47 viewing 2-6 viewing and correcting 2-10 Error Events (bulk) re-rate 7-48 Error Files ENM process 2-5 Error Messages xiv Errors correcting (billing) 3-15 correcting (rating) 2-8 ERT See Event Rating (ERT) Process











































Index

re-rating 7-50 Executing expressions 7-25 Form Help xi Full Database Validation 7-27 General Bulk Output By Task 4-2, 7-28 General Bulk Output Process 4-2, 7-29 General Output Process (GOP) description 1-18 output device 4-8, 4-9 printing document images 4-7 process 4-8 processing 4-3 schedule types 7-29 using a schedule or task 4-2 Generate customer invoice image 7-31 dunning letter 7-24 invoice image 7-30, 7-32 invoices reprint 7-34 viewing image file 7-35 Help context-sensitive xii error messages xiv form xi online x IGP (Invoice Generation Process) 1-17

Normalised Files retrieving details Online Help Output Device examples overview Output Method components defining example Output Method Type Output Method Types searching Output Processing configuring Output scripts Parallel Processing support for Parallel Tariffing description Partition Maintenance Pipe/Concatenate options Printing bill run configuration bill run set up

2-6 x 4-8 4-11, 4-12 4-9 4-1 4-8 4-13 4-13 4-1 4-8 4-8 4-10 4-5 1-13 7-36, 7-37 4-9 4-4 4-5











































Index

Rating architecture archive directory correcting errors directory structure errors managing files overview schedule types Rating and Billing overview Rating Processes Event Normalisation (ENM) Event Rating (ERT) Event Rating Broker (ERB) Event Rating Output (ERO) trerate trerodb Rating Subtotal cache Rating Task checking results data feed reconciliation report description error files log-out file notifying completion

1-7 2-2 2-8 2-2 1-12 2-1 2-1 2-12 1-1 1-9 1-10 1-7 1-11 1-5 1-5 1-8 2-4 2-7 2-3 2-5 2-5 2-4

Re-rate error events 7-47 error events (bulk) 7-48 event file 7-52 events (bulk) 7-50 Re-rate File assigning error events 2-11 creating 2-11 Revoke bill run 7-59 billing task 3-13 customer bill run 7-61 event file 7-62 file and move back 7-63 invoice image settings 7-64 invoice images for customer 7-65 invoice print settings 7-66 invoice print settings for customer 7-67 invoice settings 7-68 invoices (keep Rentals) 7-69 invoices (keep rentals) for customer7-70 invoices for customer 7-71 rental events 7-72 rental events for customer 7-73 reprocessed file 7-74 Rotate











































Index

General Output Process (GOP)

7-29

7-30 Invoice Generate Image 7-32 Invoice Print Image 7-33 Invoice Reprint Generation 7-34 Invoice View Image 7-35 Partition Maintenance 7-36, 7-37 Print Invoices 7-38 Print Invoices for Customer 7-39 Purge Error Events 7-40 Purge Events (non Error) 7-42 Purge Files 7-43 Quality Assurance Bill Run 7-44 Rate Files 7-45 rating 2-12 Re-analyze Tables 7-46 Reconfigure Auditing 7-53 Report Reference Type(RRRT) 7-54 Reprocess Error Event 7-55 Reprocess Event 7-57 requirements 7-1 Re-rate Error Events 7-47 Re-rate Error Events (bulk) 7-48 Re-rate Events (bulk) 7-50 Re-rate File 7-52

UnApply&Deallocate Invoices 7-80 UnApply&Deallocate Invoices for Customer 7-81 Unarchive 7-84 Update Account Unbilled 7-85 Update Charge Categories 7-86 Update Invoice Unbilled 7-87 Update Lists 7-88 update partitions 7-37 Verify Charge Partition 7-89 Verify Charge Partition Range7-89, 7-90 Schedules deleting 6-6 description of terms 6-3 frequency 6-5 overview 6-2 server tasks 6-1 working with 6-5 Search for output method type 4-8 Server processes 5-1 Transaction Engine (TRE) 5-1 Server Commands schedule types 7-7 Server Processes











































Index

UnApply invoices invoices for customer Unarchive selected tables Update account unbilled charge categories invoice unbilled lists Update Partitions Update Partitions Uninvoiced Verify Charge Partition Verify Charge Partition Range View error events invoice data

7-80, 7-82 7-81, 7-83 7-84 7-85 7-86 7-87 7-88 7-36, 7-37 7-89 7-89 7-89, 7-90 2-6, 2-10 3-13

Report "500 System Operations Guide"

Your name

Email

Reason

Description

Copyright © 2024 IDOC.TIPS. All rights reserved.
About Us | Privacy Policy | Terms of Service | Copyright | Contact Us | Cookie Policy

Sign In

Email

Password

Remember me Forgot password?

Our partners will collect data and use cookies for ad personalization and measurement. Learn how we and our ad partner Google, collect and use data. Agree & close

500 System Operations Guide

Recommend Documents