Information Systems:ASW Analyzer - Revision history

Jeremym: /* Rebuild Custom Summary Level */

2023-01-16T22:56:15Z

Rebuild Custom Summary Level

Norwinu: /* Potential timing issue */

2017-11-01T19:34:39Z

Potential timing issue

Norwinu: /* Rebuild Custom Summary Level */

2017-11-01T19:32:50Z

Rebuild Custom Summary Level

Norwinu at 19:23, 1 November 2017

2017-11-01T19:23:22Z

Norwinu at 21:44, 10 April 2017

2017-04-10T21:44:43Z

Norwinu at 00:22, 26 January 2017

2017-01-26T00:22:53Z

Norwinu: /* Overview */

2017-01-26T00:22:17Z

Overview

Norwinu at 00:21, 26 January 2017

2017-01-26T00:21:09Z

Norwinu at 00:05, 26 January 2017

2017-01-26T00:05:21Z

Norwinu: Norwinu moved page Information Systems:Rebuilding ASW Analyzer Summary Levels to Information Systems:ASW Analyzer

2017-01-25T22:06:22Z

Norwinu moved page Information Systems:Rebuilding ASW Analyzer Summary Levels to Information Systems:ASW Analyzer

@@ Line 124: / Line 124: @@
 Sign on as FINADMIN using our favourite password (unity). Open ASW by typing 'ASW'.
-Go to Summary Level Definition Tasks (STCSLM).  Select option 3 - Reorganise summary level definitions, and select level.
+Go to Summary Level Definition Tasks (GO STCSLM).  Select option 3 - Reorganise summary level definitions, and select level.
 This will select a system base level, or existing summary level, that matches the keys you selected, and summarize it. If you are rebuilding several levels, redo the most complex level first, as the rebuild tries to use an existing summary level as a base.  It will only use the base level if it has to.

@@ Line 132: / Line 132: @@
 ====Potential timing issue====
-Currently, we are under the impression that '''custom''' summary levels can be rebuilt while there is user activity on the system (as opposed to base, which should only be done when no users are on the system). In fact, we have done so successfully. However, an issue was experienced whereby custom summary levels were rebuilt on a Sunday prior to any user activity, but led to Analyser files not being updated that entire day (i.e. the days transactions were not reflected in Analyser files). '''There is thus perhaps a theory that custom summary rebuilds should occur after users have already signed on.''' This has yet to be confirmed however; the issue may have been caused by other factors.
+Currently, we are under the impression that '''custom''' summary levels can be rebuilt while there is user activity on the system (as opposed to base, which should only be done when no users are on the system). In fact, we have done so successfully numerous times already. However, an issue was experienced whereby custom summary levels were rebuilt on a Sunday (and interestingly, prior to any user activity), but led to Analyser files not being updated that entire day (i.e. none of the day's transactions were reflected in Analyser files). '''There is thus perhaps a theory that custom summary rebuilds should occur after users have already signed on.''' This has yet to be confirmed however; the issue may have been caused by other factors.
 ==Add Custom Summary Level==

← Older revision		Revision as of 19:32, 1 November 2017
Line 129:		Line 129:

	* if an analyser rebuild fails, check here to see if summary levels have to be manually rebuilt.		* if an analyser rebuild fails, check here to see if summary levels have to be manually rebuilt.
		+
		+	====Potential timing issue====
		+
		+	Currently, we are under the impression that '''custom''' summary levels can be rebuilt while there is user activity on the system (as opposed to base, which should only be done when no users are on the system). In fact, we have done so successfully. However, an issue was experienced whereby custom summary levels were rebuilt on a Sunday prior to any user activity, but led to Analyser files not being updated that entire day (i.e. the days transactions were not reflected in Analyser files). '''There is thus perhaps a theory that custom summary rebuilds should occur after users have already signed on.''' This has yet to be confirmed however; the issue may have been caused by other factors.

	==Add Custom Summary Level==		==Add Custom Summary Level==

@@ Line 1: / Line 1: @@
 =Overview=
- Note: This info is quite wrong, but I'll update it later. Skip to [[#Troubleshooting_Analyzer_Problems |'''this section''']] if you just want to fix something. -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])
+ Note: The terminology regarding 'Analyzer' is likely inaccurate, but I'll update it later. Skip to [[#Troubleshooting_Analyzer_Problems |'''this section''']] if you just want to fix something. -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])
 Analyzer is an ASW module providing ‘data warehouse’ functionality to ASW. It can be described as a system of programs and files that maintain summary statistics of various natures (e.g. inventory and accounting stats). For example, consider the common task within ASW of querying the A/R transactions for a customer for a given period. It would be inefficient for the system to work directly with the A/R transaction file each time, first having to filter for only that customer's transactions and then having to perform a sum on the amounts. It would be more efficient to query a file that already had summarized A/R transactions by customer. Analyzer maintains such a file. As Analyzer is part of ASW, the updating of Analyzer files is internal and automatic (e.g. as a transaction is added to the G/L, the summary levels that pertain to G/L transactions are also updated).

← Older revision		Revision as of 21:44, 10 April 2017
Line 145:		Line 145:

	[[Category: Finance Problems (I.T.)]]		[[Category: Finance Problems (I.T.)]]
		+	[[Category: ASW Analyzer]]

← Older revision		Revision as of 00:21, 26 January 2017
Line 1:		Line 1:
	=Overview=		=Overview=
		+
		+	Note: This info is quite wrong, but I'll update it later. Skip to Rebuild if you just want to fix something. -[[User:Norwinu\|norwizzle]] ([[User talk:Norwinu\|talk]])

	Analyzer is an ASW module providing ‘data warehouse’ functionality to ASW. It can be described as a system of programs and files that maintain summary statistics of various natures (e.g. inventory and accounting stats). For example, consider the common task within ASW of querying the A/R transactions for a customer for a given period. It would be inefficient for the system to work directly with the A/R transaction file each time, first having to filter for only that customer's transactions and then having to perform a sum on the amounts. It would be more efficient to query a file that already had summarized A/R transactions by customer. Analyzer maintains such a file. As Analyzer is part of ASW, the updating of Analyzer files is internal and automatic (e.g. as a transaction is added to the G/L, the summary levels that pertain to G/L transactions are also updated).		Analyzer is an ASW module providing ‘data warehouse’ functionality to ASW. It can be described as a system of programs and files that maintain summary statistics of various natures (e.g. inventory and accounting stats). For example, consider the common task within ASW of querying the A/R transactions for a customer for a given period. It would be inefficient for the system to work directly with the A/R transaction file each time, first having to filter for only that customer's transactions and then having to perform a sum on the amounts. It would be more efficient to query a file that already had summarized A/R transactions by customer. Analyzer maintains such a file. As Analyzer is part of ASW, the updating of Analyzer files is internal and automatic (e.g. as a transaction is added to the G/L, the summary levels that pertain to G/L transactions are also updated).

@@ Line 1: / Line 1: @@
 The A/P Reconciliation List prints both the total of G/L account for A/P, and the total of all vendor balances.  Both these come from Analyser.  The A/P Analysis report shows the total of (and detail when requested) of accounts payable transactions.  All three of these totals should be the same.
-Report writer (which uses the Analyser files) is used to print trial balances and income statements.
+Report Writer (which uses the Analyser files) is used to print trial balances and income statements.
 If any of these are out of balance, it could be because there is something wrong with the Analyser files.  I think that the problem is usually that the various custom summary levels have gotten out of sync – which isn’t surprising; it does happen when Analyser has to look at every single transaction and decide which totals to add it to.  As long as we catch it soon enough, it is easy enough to fix.
@@ Line 42: / Line 46: @@
 ==Rebuild==
-All Summary Base Levels that have the same balance type as one of the System Base Levels being rebuilt are deleted from ANOBOB and ANOBAL.
+All Base summary levels that have the same balance type as one of the System Base Levels being rebuilt are deleted from ANOBOB and ANOBAL.
 ''Changed so that they are only deleted, or cleared, starting with the period being rebuilt.''