Static and transaction data analysis
Global analysis codes can be assigned to static data types, for example ledger accounts, assets and warehouse. They can also be assigned to transaction data types, for example ledger transactions, purchase invoices, sales orders, inventory movements and so on.
Static Data Analysis
You can analyze several different types of static data including ledger accounts, assets, customers, suppliers, warehouses, items and employees. The information held for these entities rarely changes.
The analysis dimensions you assign to any of these entities typically contain relatively static information. For example:
- you might assign an analysis dimension for location against an asset or warehouse because the location doesn't (or very rarely) changes.
- you might assign an analysis dimension for product group against each product item if an item only ever belongs to one group.
These analysis codes are entered for the data item when it is defined and can be amended at any time. For example, when you define a new ledger account using Chart of Accounts (COA), you are prompted to enter the required analysis codes.
Transactional Analysis
The analyzable transaction entities comprise ledger transactions, sales and purchase order transactions, sales and purchase invoice transactions, and inventory movements.
Up to ten analysis dimensions can be assigned to each different analyzable entity. You are free to allocate any dimensions you require, regardless of where else in the system they may be used. On ledger transactions the analysis dimensions can be mandatory or optional, depending on the type of transaction (and type of journal, or account). On all other transactions and movements all defined analysis dimensions are mandatory.
Transactions are constantly being entered into the system, and each transaction contains different data, including different analysis codes for the analysis dimensions required. For example, if you assign analysis dimensions of cost centre and department to ledger transactions, you can enter a different cost centre and department code on each transaction you enter.
If you use SunSystems Order Fulfilment, you can use Analysis Mapping to automatically include transaction analysis codes on the sales or purchase transactions posted from Order Fulfilment to Financials. This allows you to combine the use of static and transactional analysis to obtain the refinement of transaction analysis, without the input effort it implies. For example, you can assign a static analysis code to each customer identifying the sales area, and then map this analysis dimension onto a ledger transaction analysis dimension. The sales area code is then automatically transferred on the transactions posted to the ledger.