Troubleshooting NEOSYS Finance System - Revision history

Arvind: /* Running CHK.VOUCHERS */

2024-03-26T07:01:10Z

Running CHK.VOUCHERS

← Older revision		Revision as of 07:01, 26 March 2024
Line 270:		Line 270:
	1. /root/neosys/test <DBCODE>		1. /root/neosys/test <DBCODE>
	2. After startup press "x" key.		2. After startup press "x" key.
	3. Type: "~~chkvindex~~"		3. Type: "chkvouchers"
	</pre>		</pre>
	*Exodus LIVE Database		*Exodus LIVE Database
Line 277:		Line 277:
	2. Run /root/neosys/run <DBCODE>		2. Run /root/neosys/run <DBCODE>
	3. After startup press "x" key.		3. After startup press "x" key.
	4. Type: "~~chkvindex~~"		4. Type: "chkvouchers"
	</pre>		</pre>
	*AREV Both LIVE and TEST databases		*AREV Both LIVE and TEST databases

Arvind: /* Reopen New Year or Redo Open New Year procedure */

2024-02-09T10:13:54Z

Reopen New Year or Redo Open New Year procedure

← Older revision		Revision as of 10:13, 9 February 2024
Line 734:		Line 734:
	===Reopen New Year or Redo Open New Year procedure===		===Reopen New Year or Redo Open New Year procedure===

	~~In latest versions of NEOSYS, you~~ can reopen a year using the below command.		You can reopen a year using the below command.

			*Exodus TEST Database
			<pre>
			1. /root/neosys/test <DBCODE>
			2. Press x and then type reopenyear <Companycodes> YYYY
			3. Press x and then run chkob. Include a few prior years as well to ensure all balances are fine.
			</pre>

			*Exodus LIVE Database
			<pre>
			1. Stop all LIVE processes. (pressing x won't return prompt to enter check command if other LIVE processes running)
			2. Run /root/neosys/run <DBCODE>
			3. Press x and then type reopenyear <Companycodes> YYYY
			4. Press x and then run chkob. Include a few prior years as well to ensure all balances are fine.
			</pre>

			*AREV

	REOPENYEAR <Companycodes> YYYY		REOPENYEAR <Companycodes> YYYY
Line 748:		Line 765:
	</pre>		</pre>

	In Maintenance mode, run CHK.OB and include a few prior years as well, to ~~see if~~ all balances are fine.		In Maintenance mode, run CHK.OB and include a few prior years as well to ensure all balances are fine.
	<pre>		<pre>
	Media Production Finance Management Timesheets Files General Exit		Media Production Finance Management Timesheets Files General Exit

Arvind: /* Redo Open New Year procedure */ Make the article more searchable

2023-05-12T07:29:45Z

Redo Open New Year procedure: Make the article more searchable

← Older revision		Revision as of 07:29, 12 May 2023
Line 732:		Line 732:
	In order to fix this problem, redo the open new year procedure for the problematic year, where recreating opening balances (which is part of the opennewyear.subs program) should fix the issue.		In order to fix this problem, redo the open new year procedure for the problematic year, where recreating opening balances (which is part of the opennewyear.subs program) should fix the issue.

	===Redo Open New Year procedure===		===Reopen New Year or Redo Open New Year procedure===

	In latest versions of NEOSYS, you can reopen a year using the below command.		In latest versions of NEOSYS, you can reopen a year using the below command.

Joel: /* 3. Run CHK.ALLOC */

2023-02-01T06:54:34Z

3. Run CHK.ALLOC

← Older revision		Revision as of 06:54, 1 February 2023
Line 499:		Line 499:

	This process can be run while users are working since there is a only a very slight chance that they will be posting the same account at the time that the program is updating its open item voucher index.		This process can be run while users are working since there is a only a very slight chance that they will be posting the same account at the time that the program is updating its open item voucher index.

			====Exodus====

			*Exodus TEST Database
			<pre>
			1. /root/neosys/test <DBCODE>
			2. After startup press "x" key.
			3. Type: "chkalloc"
			</pre>
			*Exodus LIVE Database
			<pre>
			1. Stop all LIVE processes. (pressing x won't return prompt to enter check command if other LIVE processes running)
			2. Run /root/neosys/run <DBCODE>
			3. After startup press "x" key.
			4. Type: "chkalloc"
			</pre>

			Enter minimum period to start check from.
			<pre>
			/root/hosts/test/work Command? chkalloc
			Begin transaction
			Making a new document/report 52360178.htm:
			----------------------------------------
			Minimum voucher year.period to check?
			(0 for all)
			201601
			</pre>

			Enter 1 for all accounts. Enter 2 if you want to look at a specific a/c.
			<pre>
			========================================
			CHK.ALLOC
			*1. All Vouchers/Accounts
			2. One Account`s Indexed Vouchers Only
			Please enter 1 - 2 or Enter to default or 0 to cancel.
			? 1
			</pre>

			Enter specific a/c no. or press Enter for all.
			<pre>
			----------------------------------------
			Which account do you want ?
			Give the account number or name,
			or press [Enter] if not known.
			(separate multiple entries with spaces)
			?
			</pre>

			Choose option 3 (Yes to all).
			<pre>
			REC1:21 12/03/19 OPTI,A 2/ (Unposted) Voucher "REC1:21" ln:2 missing from index "OPTIA"
			========================================
			Missing from O/I index
			Add it? (5.4KB)
			1. Yes
			*2. No
			3. Yes to all
			4. No to all
			5. Yes to all "OPTIA"
			6. No to all "OPTI"
			7. Skip all unposted vouchers
			Please enter 1 - 7 or Enter to default or 0 to cancel.
			? 2
			</pre>

			====AREV====

	In maintenance mode press F5		In maintenance mode press F5

Joel: /* Running CHK.VOUCHERS */

2023-02-01T06:39:35Z

Running CHK.VOUCHERS

← Older revision		Revision as of 06:39, 1 February 2023
Line 270:		Line 270:
	1. /root/neosys/test <DBCODE>		1. /root/neosys/test <DBCODE>
	2. After startup press "x" key.		2. After startup press "x" key.
	3. Type: "~~chkalloc~~"		3. Type: "chkvindex"
	</pre>		</pre>
	*Exodus LIVE Database		*Exodus LIVE Database
Line 277:		Line 277:
	2. Run /root/neosys/run <DBCODE>		2. Run /root/neosys/run <DBCODE>
	3. After startup press "x" key.		3. After startup press "x" key.
	4. Type: "~~chkalloc~~"		4. Type: "chkvindex"
	</pre>		</pre>
	*AREV Both LIVE and TEST databases		*AREV Both LIVE and TEST databases

Joel: /* Running CHK.VOUCHERS */

2023-02-01T06:26:37Z

Running CHK.VOUCHERS

← Older revision		Revision as of 06:26, 1 February 2023
Line 263:		Line 263:

	====Running CHK.VOUCHERS====		====Running CHK.VOUCHERS====
	Run ~~the following command in maintenance mode~~ and ~~check for errors.~~
			This exact procedure restores vouchers missing from open item accounts:

			*Exodus TEST Database
			<pre>
			1. /root/neosys/test <DBCODE>
			2. After startup press "x" key.
			3. Type: "chkalloc"
			</pre>
			*Exodus LIVE Database
			<pre>
			1. Stop all LIVE processes. (pressing x won't return prompt to enter check command if other LIVE processes running)
			2. Run /root/neosys/run <DBCODE>
			3. After startup press "x" key.
			4. Type: "chkalloc"
			</pre>
			*AREV Both LIVE and TEST databases
			<pre>
	F5		F5
	UTIL		UTIL (nothing happens at this stage as its a background process and gives you access to the next command)
	CHK.~~VOUCHERS~~		CHK.ALLOC
			</pre>

	When running CHK.VOUCHERS, respond to prompts as shown below. Generally respond negatively to prompts which are not specified below, but in TEST datasets you can experiment by responding positively.		When running CHK.VOUCHERS, respond to prompts as shown below. Generally respond negatively to prompts which are not specified below, but in TEST datasets you can experiment by responding positively.

Joel: /* Fixing "Cross Check Balance" warning using CHK.VINDEX */

2023-02-01T06:17:35Z

Fixing "Cross Check Balance" warning using CHK.VINDEX

← Older revision		Revision as of 06:17, 1 February 2023
Line 201:		Line 201:

	===Commit or Revert current changes===		===Commit or Revert current changes===
			<pre>
	Finished in 2 mins, 45 secs		Finished in 2 mins, 45 secs
	What next boss ?		What next boss ?
Line 209:		Line 210:
	Please enter 1 - 2		Please enter 1 - 2
	? 0		? 0
			</pre>

			Select 1 to commit changes.

	==Checking if a voucher is fully posted==		==Checking if a voucher is fully posted==

Joel: /* Fixing "Cross Check Balance" warning using CHK.VINDEX */

2023-02-01T06:14:43Z

Fixing "Cross Check Balance" warning using CHK.VINDEX

← Older revision		Revision as of 06:14, 1 February 2023
Line 199:		Line 199:

	Select Yes.		Select Yes.

			===Commit or Revert current changes===
			Finished in 2 mins, 45 secs
			What next boss ?
			========================================
			Commit any database updates ?
			1. Commit
			2. Rollback
			Please enter 1 - 2
			? 0

	==Checking if a voucher is fully posted==		==Checking if a voucher is fully posted==

Joel: /* Fixing "Cross Check Balance" warning using CHK.VINDEX */

2023-01-23T07:45:20Z

Fixing "Cross Check Balance" warning using CHK.VINDEX

← Older revision		Revision as of 07:45, 23 January 2023
Line 152:		Line 152:
	===Different account - Delete the index entry?===		===Different account - Delete the index entry?===
	<pre>		<pre>
	"~~MEVEJ~~FZ" L=~~232~~ V=~~REC~~~~461~~~~FZ 05~~/07/09 B=~~447~~ "~~MEVEJ~~"		51841 voucher_index recs
	different account "~~ADVOPME~~"		"P8311" L=8 V=PUR1801231 30/06/18 B=13653 "P831" different account "P823"
	Delete the index entry?		========================================
	~~───┬─────────────────────────────────────────────────────────────~~		"P8311" L=8 V=PUR1801231 30/06/18 B=13653 "P831" different account "P823"
	1>No		Delete the index entry?
	~~2│None~~		*1. No
	~~3│Yes~~		2. Yes
	~~4│All~~		3. Delete None
			4. Delete All
			Please enter 1 - 4 or Enter to default or 0 to cancel.
			? 1
	</pre>		</pre>

Line 166:		Line 169:
	===Missing Voucher - Delete the index entry?===		===Missing Voucher - Delete the index entry?===
	<pre>		<pre>
	╔═════════════════════════════════════════════════════════════════╗		2500. JOB47141"14018151ü815" "1ü815" bad company
	║ "~~VIV~~N" L=~~458~~ V=IN~~2012/1170~~~~N 29~~/05/12 missing voucher ║		"14018151ü815" L=1 V=PUR11516:71ü815 15/01/14 missing voucher
	║ Delete the index entry? ║		========================================
	║───┬─────────────────────────────────────────────────────────────║		"14018151ü815" L=1 V=PUR11516:71ü815 15/01/14 missing voucher
	║ 1>No ║		Delete the index entry?
	║ ~~2│Yes ║~~		*1. No
	║ ~~3│None ║~~		2. Yes
	║ ~~4│All ║~~		3. Delete None
	╚═════════════════════════════════════════════════════════════════╝		4. Delete All
			Please enter 1 - 4 or Enter to default or 0 to cancel.
			? 1
	</pre>		</pre>

Line 181:		Line 186:
	===Different Date - Correct index entry?===		===Different Date - Correct index entry?===
	<pre>		<pre>
	"~~OMD~~AP" L=~~115~~ V=IN~~2013~~/~~350~~~~AP 31~~/03/13 B=~~1159~~		"P8311" L=8 V=PUR1801231 30/06/18 B=13653 different date "12/02/18"
	different date "14/03/13"		========================================
	Correct index entry?		"P8311" L=8 V=PUR1801231 30/06/18 B=13653 different date "12/02/18"
	~~───┬─────────────────────────────────────────────────────────────~~		Correct index entry?
	1>No		*1. No
	~~2│Yes~~		2. Yes
	~~3│Correct~~ None		3. Correct None
	~~4│Correct~~ All		4. Correct All
			Please enter 1 - 4 or Enter to default or 0 to cancel.
			? 1
	</pre>		</pre>

	Select Yes.		Select Yes.






	==Checking if a voucher is fully posted==		==Checking if a voucher is fully posted==

Arvind: /* Reposting a Batch in Journal Entry */

2022-09-09T12:23:12Z

Reposting a Batch in Journal Entry

← Older revision		Revision as of 12:23, 9 September 2022
Line 347:		Line 347:

	==Reposting a Batch in Journal Entry==		==Reposting a Batch in Journal Entry==
	The authorisation to repost a batch is restricted to NEOSYS and a few client users at the moment. Reposting a batch will repost all the vouchers in the batch.		The authorisation to repost a batch is restricted to NEOSYS and a few client users at the moment. Reposting a batch will repost all the vouchers in the batch. See [[Procedures#Amending.2FReposting_Journal_Entries\|Amending/Reposting Journal Entries]]

	See [http://userwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Finance_System#Correcting_mistakes_in_postings Correcting mistakes in postings] for NEOSYS policy for correcting mistakes in journal postings.		See [http://userwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Finance_System#Correcting_mistakes_in_postings Correcting mistakes in postings] for NEOSYS policy for correcting mistakes in journal postings.

	<b>Warning</b>: Reposting journals ~~which~~ are already allocated will create cross check balance errors, so before reposting, any allocations should be de-allocated to avoid these errors.		<b>Warning</b>: Reposting journals that are already allocated will create cross check balance errors, so before reposting, any allocations should be de-allocated to avoid these errors.

	Reposting a batch should be done in TEST dataset first. After reposting, all accounts should be tested for cross check balance errors. Do this by taking ledger printout for the whole year for all accounts.		Reposting a batch should be done in TEST dataset first. After reposting, all accounts should be tested for cross check balance errors. Do this by taking ledger printout for the whole year for all accounts.

	~~See [[Procedures~~#~~Amending~~.~~2FReposting_Journal_Entries\|Procedure~~ for ~~Reposting Journal Entries]]~~		#Client must de-allocate vouchers which need to be amended
			#NEOSYS support staff must wait for a day so that de-allocated vouchers are copied into Test database
			#Authorise required users to amend and repost (without record) '''in Test database only''' <br>(While reposting, we have 2 options i.e. with record and without record. The 'with record' option causes the system to maintain a history of edits made. Hence, we want to repost without record so that there is no trace of the edit in the system)
			#Amend a substantial number of vouchers in Test and verify them.<br>To verify if the edits made are reflected:
			#<nowiki>*Print all ledgers for the whole year</nowiki>
			#<nowiki>*Cross-check all balances</nowiki>
			#Once you verify the balances are correct in Test database, grant users permission to amend and repost in the Live database.
			#Ask users to amend and repost vouchers in the Live database.
			#Cross-check all balances for the current year.
			#If you successfully verify the balances, revoke permissions immediately. Else, wait for 24 hours and revoke permissions irrespectively.

	~~To repost a batch, edit the journal on the Journal Entry/Query page and save. Click OK for the prompt “OK to repost now?”.~~
	==Editing and Reposting Vouchers==		==Editing and Reposting Vouchers==