How to Aggregate Data

Every time an aggregation is run for a defined fiscal period, the transactions created in the previous aggregation are deleted and new transactions are created to reflect the data being imported. For example, if you generate a Accounting Component invoice after an aggregation and then re-aggregate the data for the same fiscal period, the previously generated invoice has zero charges. This result is due to the transactions being rolled back on re-aggregation. New transactions are created as part of the re-aggregation. Therefore, invoices need to be regenerated to capture these new transactions and show the associated charges.

You can use Invoice groups and then generate your invoices in batch mode. You can also bill for two different data sets that are imported at two different times. You can do an aggregation after the first one is imported and then aggregate again after the second data imported. Only generate invoices after you verify that all the data for that fiscal period is valid.

To aggregate data, follow these steps:

Generate usm_mr_itemp_XXXXXX data from the external files and databases.
Generate usm_mr_ievent_XXXXXX data from the usm_mr_itemp_XXXXXX data based on the SQL aggregation specified in the Data Mediation profile. The XXXXXX values are sequential numbers generated by the system.
Generate usm_mr_iresult_YYYY data from the usm_mr_ievent_XXXXXX table based on the built-in aggregation logic. The YYYY is the internal metric ID for the event specified by the aggregation.
Generate transactions for the accounts based on the usm_mr_iresult_YYYY data created in Step 3.

You can run the aggregation process any number of times for a fiscal period to reflect the latest data that is imported into the system.