Steps to define required analysis

The following steps are required to implement a new analysis requirement:

1. Create an analysis dimension for the new analysis requirement using Analysis Dimensions (AND). For example, define a location dimension.

   As part of this definition, you can attach the analysis dimension to an existing analysis table to use the codes defined on that table, and choose to link to the table to automatically reflect any code changes.

   Depending on your serialization, you can setup extension fields for extended analysis to store and use extra attributes on analysis codes for this analysis definition.

2. Assign the analysis dimension to the data entities it can be used to analyze using Analysis Structure (ANS). For example, assign location to the ledger account, asset and warehouse entities. If you assigned the analysis dimension to a static data entity e.g. a ledger account, when you create a new data entity, you are prompted to enter an analysis code for this analysis dimension. For transaction analysis, when you enter the appropriate type of transaction you are prompted to enter the required analysis dimension codes (according to the journal type and account rules).
3. Define the analysis dimension codes using Analysis Codes (ANC), if they need to be entered manually. For example, to create location codes for the Northern, Southern and Western areas.
4. For ledger transaction analysis dimensions, you can use Journal Type (JNT) to control the analysis dimension input rules for particular transaction types. This is required because some of the transaction analysis dimensions may only apply to selected types of ledger transaction. For example, a product code may be required on sales related transactions only. Similarly, you can use Chart of Accounts (COA) to control the analysis dimension input rules for particular accounts. For example, some transaction analysis dimensions may not be required for some accounts but are mandatory for other accounts.
5. If analysis hierarchies are required to analyze the codes in different ways for reporting purposes, you must create the analysis hierarchy labels and hierarchy codes, and then assign the analysis codes to the hierarchy codes.

Once you have carried out all of these steps SunSystems automatically prompts you to enter the required analysis codes on accounts and transactions, as they are entered.

If in Step 2 you assigned the analysis dimension to a static data entry e.g. a ledger account, when you create a new data entity, you are prompted to enter an analysis code for this analysis dimension. For transaction analysis, when you enter the appropriate type of transaction you are prompted to enter the required analysis dimension codes (according to the journal type and account rules).