CGI Advantage uses transactions to record financial information and administrative events into the system. Transactions collect information into a single input form, designed to ease data entry as well as to consolidate pertinent information for approval and query purposes. Transactions are created manually, interfaced, uploaded, system-generated, and even created behind-the-scenes through data entry paradigms meant to ease data entry (i.e. wizards).
The following level hierarchy of attributes identify the nature of transactions in CGI Advantage:
Transaction Category - highest level, broadly classifies a transaction into a functional area. Accounts Payable is a typical example of a functional area. This level is for reporting only. The universe of transaction categories is pre-defined and not something updated locally.
Transaction Type - the second level in the hierarchy identifies the functional purpose of the transaction. For example, the transaction type of Cash Receipt has the purpose of recording the receipt of money. This level goes beyond reporting in that there is processing logic in terms of edits and updates tied to a transaction type.
Transaction Sub Type – an optional level in the hierarchy that is used to extend special logic within a Transaction Type to one or more transaction codes, as no logic is ever designed to a specific transaction code.
Transaction Code - identifies a unique instance within a Transaction Type whereby online configurations are made to control many types of edits, security, workflow, and other types of processing rules. Please refer to the CGI Advantage - Financial Administration User Guide for information on setting up Transactions Codes, controls, and options for transactions.
A transaction is uniquely identified by the combination of its Transaction Code, Transaction Department Code, and its Transaction ID. The Transaction Department Code identifies the organization responsible for the transaction. The Transaction ID is a unique identification with a Transaction Department. When using automatic numbering, that Transaction ID may be unique across all Transaction Departments with a single numbering string used for a Transaction Code.
This topic includes the following areas: