<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://techwiki.neosys.com/index.php?action=history&amp;feed=atom&amp;title=Troubleshooting_NEOSYS_Jobs_System</id>
	<title>Troubleshooting NEOSYS Jobs System - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://techwiki.neosys.com/index.php?action=history&amp;feed=atom&amp;title=Troubleshooting_NEOSYS_Jobs_System"/>
	<link rel="alternate" type="text/html" href="https://techwiki.neosys.com/index.php?title=Troubleshooting_NEOSYS_Jobs_System&amp;action=history"/>
	<updated>2026-05-29T18:24:12Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.3</generator>
	<entry>
		<id>https://techwiki.neosys.com/index.php?title=Troubleshooting_NEOSYS_Jobs_System&amp;diff=1388&amp;oldid=prev</id>
		<title>Arya: Created page with &#039;== Solving Error: &quot;Estimate &#039;xxxxxxx&#039; system failure during previous invoicing attempt&quot; ==  System errors during production invoicing can result in various degrees of partial upd…&#039;</title>
		<link rel="alternate" type="text/html" href="https://techwiki.neosys.com/index.php?title=Troubleshooting_NEOSYS_Jobs_System&amp;diff=1388&amp;oldid=prev"/>
		<updated>2013-12-17T11:02:52Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;#039;== Solving Error: &amp;quot;Estimate &amp;#039;xxxxxxx&amp;#039; system failure during previous invoicing attempt&amp;quot; ==  System errors during production invoicing can result in various degrees of partial upd…&amp;#039;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Solving Error: &amp;quot;Estimate &amp;#039;xxxxxxx&amp;#039; system failure during previous invoicing attempt&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
System errors during production invoicing can result in various degrees of partial updating of invoice files, finance journals and billing analysis reports.&lt;br /&gt;
&lt;br /&gt;
It is important to stop further attempts to invoice an estimate until steps have been taken to reverse any partial updates done. Therefore, if there is a system error during an attempt to create an production invoice, the system locks the estimate from further invoicing.&lt;br /&gt;
&lt;br /&gt;
You can unlock the estimate for another attempt at invoicing but the following preventative and defensive procedure must be followed meticulously to avoid making things WORSE not better.&lt;br /&gt;
&lt;br /&gt;
Step 1. THIS PROCEDURE MUST BE RUN IN TEST DATA FIRST.&lt;br /&gt;
&lt;br /&gt;
Step 2. A REPORT MUST BE MADE STATING THE IDENTIFIED CAUSE OF THE FAILURE AND WHAT STEPS HAVE BEEN TAKEN TO AVOID IT REPEATING. THIS STEP IS *NOT* OPTIONAL&lt;br /&gt;
&lt;br /&gt;
Step 3. REPEAT THE PROCEDURE IN LIVE DATABASE ONLY IF A) THERE IS NO ISSUE IN STEP 1 AND B) STEP 2 HAS BEEN COMPLETED.&lt;br /&gt;
&lt;br /&gt;
=== Identify the half created invoice (invoice number and estimate number) ===&lt;br /&gt;
&lt;br /&gt;
 LIST PRODUCTION.INVOICES INVOICE_NO_FAILSAFE WITH INVOICE_NO_FAILSAFE NE &amp;quot;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Determine if any postings have been made ===&lt;br /&gt;
&lt;br /&gt;
Locate invoice voucher in finance Voucher File and/or Journals and note the posted or unposted batch number. &lt;br /&gt;
&lt;br /&gt;
=== If already posted: Reverse any posted finance journals ===&lt;br /&gt;
&lt;br /&gt;
If the invoice journal has already been posted then get finance to create a corresponding journal to reverse it&lt;br /&gt;
&lt;br /&gt;
=== If not yet posted: Delete any unposted financial entries ===&lt;br /&gt;
&lt;br /&gt;
Delete the unposted invoice journal voucher from unposted journals&lt;br /&gt;
&lt;br /&gt;
Notify finance department of the lost invoice/journal number&lt;br /&gt;
&lt;br /&gt;
=== Delete the invoice from the database ===&lt;br /&gt;
&lt;br /&gt;
Locate the invoice in the List of Invoices report. Your diligence is required to avoid missing it due to wrong selection of period etc.&lt;br /&gt;
99999 is the invoice number and X is the company code&lt;br /&gt;
&lt;br /&gt;
   DELETE INVOICES &amp;quot;999999**X&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It should say briefly &amp;quot;1 Record(s) Deleted&amp;quot;. If it says &amp;quot;Record does not exist&amp;quot; then also do&lt;br /&gt;
&lt;br /&gt;
  DELETE INVOICES &amp;quot;999999&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It MUST say briefly &amp;quot;1 Record(s) Deleted&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Run List of Invoices again to confirm it no longer exists.&lt;br /&gt;
&lt;br /&gt;
=== Unlock the estimate  ===&lt;br /&gt;
&lt;br /&gt;
XXXXXX is the production ESTIMATE number (NOT invoice number).&lt;br /&gt;
&lt;br /&gt;
 SELECT PRODUCTION.INVOICES &amp;quot;XXXXXXXXX&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It should say briefly &amp;quot;1 record(s) have been selected&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Be meticulously careful entering the number. If you enter the wrong number or mistype it etc there will be no error message, but the estimate will not be unlocked and you will still be unable to invoice it.&lt;br /&gt;
&lt;br /&gt;
 CLEARFIELD PRODUCTION.INVOICES INVOICE_NO_FAILSAFE&lt;br /&gt;
&lt;br /&gt;
It should just come back to the command line immediately&lt;br /&gt;
&lt;br /&gt;
=== Invoice the estimate ===&lt;br /&gt;
&lt;br /&gt;
Create the invoice and check everything is OK&lt;/div&gt;</summary>
		<author><name>Arya</name></author>
	</entry>
</feed>