Technical Trouble Shooting Guide - TransLution Statuses

Introduction
These notes are intended for people with a good knowledge of SQL and also a good understanding of the TransLution database. The information is not intended for general users of the software

TransLution Statuses

It is often useful to know what a status line means for a specific scanner job or sales order. This section describes each of these. Sometimes a line in a certain status will not be visible from the front end but it can of course still be seen in the database.

 

TransLution Scanner Jobs (Database Table - Job)

1: New Job
2: Job currently running on the scanner
3: Finish button on the scanner has been pressed. Non-standard or non-processed jobs (i.e. not picking, transfer, cycle count or stock take) remain in this status
4: Job Completed by the standard function area processing
5: Job cancelled by Job Manager

 

Buffered Posting (Database Table - BUFFER_POST_DATA)

Possible row statuses are:

5 - New row ready for processing

15 - Error row. Processing failed

20 - Processing was successful

50 - Cancelled Row. Will not be processed

 

Print Step (Database Table - PRINT_MASTER)

Possible Row statuses are:

1 - New report

5 - Started Processing

15 - Encountered an Error

20 - Successful Print. This cannot validate if the printer was the one required or if the print was successful but it confirms there were no SSRS errors

 

General Posting Service

5 - Line ready for processing but not yet processed. Either because the General Posting service is not running or the timer interval has not yet elapsed.

10 - Being processed by the service. As soon as the service timer ticks over, all lines in status 5 are picked up and put into status 10 (This is configurable using GENERAL POSTING SERVICE QUERY COUNT. It defaults to 100). If the ERP service or Syspro cannot be found, these lines are immediately put back into a status of 5 to await the next time tick.

15 - Line processed but an error was returned by Syspro. The error details are shown in the Response column of the general posting table and in the Business Object Event Table. The business object event id is saved to the general posting table.

20 - Line successfully processed in Syspro. 

25 - Line did not post because the associated line in the Referenced Table failed to post.

35 – Line has not been processed as a result of a communication failure. This is typically because the call to Syspro does not respond (something goes down between starting the post and finishing it). This means that there is nothing telling us to take the line out of status 10. This is because we don't know if the post succeeded or not so we can't roll it back (if we did we would risk posting duplicate transactions) or mark it as failed (because we don't know if it did fail). With every new cycle, any rows in status 10 are set to a status of 35.