Analysis Tab

Use the Analysis tab to define how entries to the account must be analyzed. You can specify:

• Whether a cost center, a project, or both are required, and the default cost center or project to use

If cost center analysis and project analysis are enabled, you can apply rules (limitations) in relation to the recording of cost centers and projects.

If you have enabled COA masks, the sub-accounts, cost centers, and projects you use in the account analysis must be valid according to the COA masks. See COA Masks.

Important: After you have saved account setup data and used the account in postings, you can change the account setup to add additional analysis (project or cost center), but you cannot remove analysis. You can change the analysis limitation setting at any time.

Select to indicate that this account uses sub-account analysis. Specify the default sub-account profile in the next field.

This field is enabled when you select the Sub-Account field. Specify a default sub-account profile. When you enable sub-account analysis for bank accounts, tax accounts, and accounts with automatic posting, you must specify a default sub-account profile.

Select to indicate that this account uses cost center analysis. This option enables the Default Cost Center and Default SAF Structure fields. When you enable cost center analysis only, you must specify a default cost center.

If you enable both cost center analysis and project analysis for the same account, you must specify an analysis limitation.

Select to indicate that this account uses project analysis. This option enables the Default Project and Default SAF Structure fields. When you enable project analysis only, you must specify a default project.

If you enable both cost center analysis and project analysis for the same account, you must specify an analysis limitation.

GL accounts to be used in operational functions such as Purchase Orders cannot be set up with project analysis only. You must enable project and cost center analysis. When you enable cost and project analysis for a GL account, the analysis limitation must be set to none, one required, or cost center required.

When you enable both cost center and project analysis, you can specify any analysis limitation.

• None: There is no limitation on how you use cost centers and projects on the transaction. In this case, the Default Cost Center and Default Project fields must be empty.

• One Required: You must specify either one project or one cost center on the transaction.

• Both Required: You must specify both a project and a cost center on the transaction.

• Cost Center Required: You must specify a cost center. The Default Project field must be empty.

• Excluding each Other: You must specify either a project or a cost center on the transaction. You cannot specify both types of analysis and you cannot leave both blank.

• Project Required: You must specify a project. The Default Cost Center field must be empty.

Note: The analysis limitations are validated by the system when you save them. GL account analysis limitation settings are also validated in the program GL Account Excel Integration (25.3.13.5). Any validation problems return errors for automatic GL accounts and return warnings for manual GL accounts.

You can change the analysis limitation setting at any stage, even after Financials transactions have been posted using the account.

• Both Cost Center Analysis and Project Analysis are enabled, and the analysis limitation is Both Required or Cost Center Required.

• Both Cost Center Analysis and Project Analysis are enabled, and the analysis limitation is Both Required or Project Required.

When you enable cost center or project analysis, select a default SAF structure code for transactions on this account. This field is optional.

When the analysis type is cost center or project, you must specify a default SAF structure if the Retrieve Structure from GL Account setting is selected for the cost center or project.

Select to indicate that this account uses SAF analysis. This option enables the SAF Structure Code field.

This field displays the date on which analysis was activated for the account. This field is unavailable if analysis is not activated for the account.

This field displays the user who activated analysis for the account. This field is unavailable if analysis is not activated for the account.

This field displays the date on which sub-account analysis was activated for the account. This field is unavailable if sub-account analysis is not activated for the account.

This field displays the user who activated sub-account analysis for the account. This field is unavailable if sub-account analysis is not activated for the account.

New analysis limitation values (Cost Center Required and Project Required) were introduced in QAD 2012 EE and retrofitted to earlier releases. For accounts used in Financials transactions, you can change the analysis limitation setting to use the new values without restriction. However, you may encounter issues if you have changed the analysis limitation settings for GL accounts used in unposted operational transactions.

Important: It is recommended that you post all operational GL transactions prior to changing the GL account analysis limitation.

For unposted operational GL transactions that met the analysis limitation when the transaction was created and where the analysis limitation has since been changed to a more restrictive limitation (for example, from None to Cost Center Required), the system displays an error when you run Operational Transaction Post.

When posting operational transactions for accounts with updated analysis limitation settings, if a small number of errors are raised, use Unposted GL Transaction Correction to update the analysis limitation value for the accounts and then rerun Operational Transaction Post. If a large number of posting errors are raised, undo the analysis limitation change, post the transactions, and then restore the analysis limitation change.

Similarly, the Pending Invoice Register does not display unposted sales invoices if the analysis limitation settings for the sales accounts were updated after the invoice was created, and where the invoice is likely to cause errors during Invoice Post and Print.