Table 17: Configuration parameter for automatically entering voucher items

Configuration parameter	Meaning
Accounting | SimpleCollector	Preprocessor relevant configuration parameter for controlling database model components, for automatically making vouchers for accounting. If the parameter is set, vouchers can be made automatically. Changes to this parameter require the database to be recompiled.
Accounting | SimpleCollector | ReportDir	Configuration parameter containing the path for storing reports.

Enter separate voucher items into a voucher. One voucher item corresponds to a bookable IT service. For example, software assigned to an employee or scheduled measurement of mailbox sizes can be consolidated in one voucher item. It is also possible to include data from external data sources for making vouchers. However, the methods used for this differ from company to company and, therefore, you should implement them to suit yours.

For the automatic creation of voucher items, you can use the collector functions of the One Identity Manager Service provided with the process component VI.JobService.JobComponents.InvoiceComponent. Using One Identity Manager reporting functionality, you can group vouchers in the form of an invoice and send then by email.

To simplify dealings with data imports and collection and if necessary to extend it, you can manage the accounting run using the Start accounting run task. All available events and the current processing status of a voucher are displayed on the form.

The executable events must be customized.

• Add the executable events for each voucher type in Accounting | Basic configuration data | Accounting runs. The order in which the events are displayed on the form is given by the sort order property. For more information, see Accounting runs.

The One Identity Manager default system contains examples of simple data collectors for voucher with the voucher type "Receipt" that can be controlled through the form. Use this to collect the data you want in the database, a new voucher item is created for each data set and linked to the voucher for which the event was triggered. There is also an example of how to generate an accounting report which can then be sent by email. Processes for the base object Invoice are defined for the events supplied. If you start and event from the form, it starts running the corresponding process.

Table 18: Data collector in the default system

Event	Description	Item
COLPERSONHASAPP	Collects software assignments for employees.	0
COLWORKDESKHASAPP	Collects software assignments for workdesks.	1
COLHARDWARE	Collects devices.	2
COLADSACCOUNT	Collects enabled Active Directory user accounts.	3
COLEX2KMAILBOX	Collects enabled mailboxes.	4
COLADSHOMESIZE	Collects home directory sizes.	5
COLEX2KMAILSIZE	Collects mailbox sizes.	6
GENERATE_PROFITCENTER_REPORTS	Generates reports for cost centers.	7

The processing state is stored in the Invoice table in the CollectorState column. At the same time, one character of this status string represents the current processing state of an event. The string's index is defined through the sort order of the associated event. The characters have the following meaning:

Table 19: Permitted status and meaning

Character	Name	Description
Blank space	New/unknown	Processing has not started. Initial state.
S	Started	This state is set by the form in order to immediately return a result to the user.
R	Running	This state is set by the process to signal that the import/collector is running.
F	Complete	The process was ended successfully.
E	Errors	The process ended in failure.

To set a status in the processes, you can use the SQL procedure VI_Accounting_SetCollectorState. This procedure expects the following parameters:

Table 20: VI_accounting_SetCollectorState procedure parameters

Parameters	Meaning
uid_invoice	Unique name of the voucher
eventname	Event name
state	Status

Calling example:

exec VI_Accounting_SetCollectorState '"&$UID_Invoice$&"','COLHARDWARE','R'

The database views used in the data collection processes can be used as templates for customizing database view.

Table 21: Database views for determining data

Name of the view	Usage
vi_view_accColADSAccount	Collects accounting relevant information for all Active Directory user accounts that are connected with an employee and managed with account definitions.
vi_view_accColADSHomeSize	Collects accounting relevant information about the size of Active Directory user account homes. The price must be given in MB in the service item. The view must be customized!
vi_view_accColEx2kMailbox	Collects accounting relevant information for all Microsoft Exchange mailboxes that are connected with an employee and managed with account definitions.
vi_view_accColEx2kMailSize	Collects accounting relevant information about the size of Microsoft Exchange mailboxes. The price must be given in MB in the service item. The view must be customized!
vi_view_accColHardware	Collects accounting relevant information of each device with workdesk and a device model with a service item.
vi_view_accColPersonHasApp	Collects accounting relevant information for all software applications assigned to employees and which have a service item.
vi_view_accColWorkdeskHasApp	Collects accounting relevant information for all software applications assigned to workdesks and which have an activity supplied.