Missing SO number in Esker converted order

if there is no sales order number created on a converted Esker order, it is possible that the Esker interface process was aborted. Follow the steps below to check: 

1) First, using TOAD verify that there is no SO number created for the customer, customer PO information in
Esker tables.(SO, C_ESKERF, and C_ESKRER)

• select * from c_eskerf where c_eskerf_id = 'EskerID'
• select * from c_eskrer where c_eskrer_id = 'EskerID'
  

2) Once verified, inform Steve Welch and the user who validated the order. In the example below, Freddie was the user for this Esker SO. (Screenshot below was taken from the ticket in Freshdesk)

3) Next, using TOAD, remove the Esker order from C_ESKERF and C_ESKERR so the Esker CSV file can be reprocessed. 

• --delete from c_eskerf where c_eskerf_id = 'EskerID'
• --delete from c_eskrer where c_eskrer_id = 'EskerID'
  

4) Using PuTTY, log in to G2 (erpprod2.hagerco.com). Navigate to /g2/prod/userdata/scripts/esker/eskerdone and look for the CSV file for the Esker order.

• Use the command: ls -Al OrderCSV'EskerNumber.csv (Ex.  ls -Al OrderCSV1000678741175949460.csv)

5) Move the CSV file to the Esker Temp directory. (UNIX command 'mv' is used to move files)

• mv  OrderCSV1000678741175949460.csv ../eskertemp

6) There is a cron job that looks for Esker orders in the eskertemp directory every 2 minuties. Once the file is moved, the cron job will grab the CSV file and reprocess the file.  You can run the select statements from step 1 to verify that the Esker order now has a SO number created. 

7) If the SO number is there, the ticket is complete and can be closed. Also reach back out to Steve Welch and the verifying user and give them the update that the SO number has been created. 

8) If the Esker order get reprocessed and still does not populate the SO number. It is possible the CSV file we received from Esker is invalid or does not include all needed information. To investigate this scenario further, use WinSCP to connect to erpprod2.hagerco.com. navigate to /g2/prod/userdata/scripts/esker/eskerdone folder and download the CSV file. 

9) Open the file in Excel and compare the file to verify information is formatted correctly. 

10) Reach back out to the validating user. There are two options. The user can manually enter the order, or they can try to redownload the CSV file from Esker. 

11) Before the new CSV file can be processed, or before they enter the order in manually, the Esker order having issues need to be removed from the EskerF and EskerR tables. 

using TOAD, remove the Esker order from C_ESKERF and C_ESKERR so the Esker CSV file can be reprocessed. 

• --delete from c_eskerf where c_eskerf_id = 'EskerID'
• --delete from c_eskrer where c_eskrer_id = 'EskerID'
  

12) If the user manually enters the order into G2, once the old Esker order is removed from EskerR and EskerF tables, there is nothing else to be done by us. 

13) If the user gets a new CSV file from Esker, once the old Esker order is removed from EskerR and EskerF tables, have them upload the CSV file and check back in about 10 min to see if the SO number is populated.