The invoice date and price information provide further information about an invoice voucher. Prices are determined from the item prices of the active voucher items using the Recalculate task.
To recalculate a voucher
-
In the Manager, select the Accounting > Vouchers category.
-
Select the voucher in the result list.
-
Select the Recalculation task.
- Save the changes.
Related topics
If a voucher has already been processed, set the Booked option. This voucher can no longer be processed.
To reactivate a voucher for processing
-
In the Manager, select the Accounting > Vouchers category.
-
Select the voucher in the result list.
-
Select the Recalculate task.
- Save the changes.
Related topics
To obtain an overview of a voucher
-
In the Manager, select the Accounting > Vouchers category.
-
Select the voucher in the result list.
-
Select the Voucher status overview task.
Table 13: Configuration parameter for automatically entering voucher items
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.
If you disable the configuration parameter at a later date, model components and scripts that are no longer required, are disabled. SQL procedures and triggers are still carried out. For more information about the behavior of preprocessor relevant configuration parameters and conditional compiling, see the One Identity Manager Configuration Guide. |
Accounting | SimpleCollector | ReportDir |
Specifies the path of the report repository. |
Enter separate voucher items into a voucher. One voucher item corresponds to a bookable IT service. For example, software assigned to an identity 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. For more information, see Starting accounting runs for vouchers.
You must customize the events to you want to run. 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.
The data collectors are defined as view definition extensions (ViewAddon) to the ACNVCollect table. You can use these data collectors as template for creating custom extensions.
Table 14: Data collector in the default system
COLPERSONHASAPP |
Collects accounting relevant information for all software applications assigned to identities and which have a service item. |
0 |
COLWORKDESKHASAPP |
Collects accounting relevant information for all software applications assigned to workdesks and which have a service item. |
1 |
COLHARDWARE |
Collects accounting relevant information of each device with workdesk and a device model with a service item. |
2 |
COLADSACCOUNT |
Collects accounting relevant information for all Active Directory user accounts that are connected with an identity and managed with account definitions. |
3 |
COLEX2KMAILBOX |
Collects accounting relevant information for all Microsoft Exchange mailboxes that are connected with an identity and managed with account definitions. |
4 |
COLADSHOMESIZE |
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. |
5 |
COLEX2KMAILSIZE |
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. |
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 15: Permitted status and meaning
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 ACN_PSetCollectorState SQL procedure. This procedure expects the following parameters:
Table 16: ACN_PSetCollectorState procedure parameters
uid_invoice |
Unique name of the voucher |
eventname |
Event name |
state |
Status |
Calling example:
exec ACN_PSetCollectorState '<UID_Invoice>', 'COLPERSONHASAPP', 'E'