Hestia WMS FAQs

• No response" appears in the scanner
• A pick list with several orders
• Picklist cannot be packed
• Possible error messages in the SAP Business One Interface Monitor

No response" appears in the scanner

The scanner tries to retrieve information from the database, but does not receive any response. This can have several causes:

1. The network is overloaded and information can only be passed on slowly via it.
   • If the network is only overloaded for a short time (e.g. because someone is copying a very large file), it should recover soon and you can continue working normally.
   • If the network overload is a permanent condition, the network should be expanded.
     
2. An evaluation is carried out, SAP data is retrieved/uploaded or something else is read in/out. Before you do something like this, you must be aware that during this time you will block the database and your colleagues will not be able to work on the scanners. Therefore, if you know that the action you want to carry out is not completed within 2-5 minutes, you should clarify with the warehouse management when there would be a period of time during which you could carry out this activity without hindering your colleagues at the scanners. Such transactions are called long-running transactions.
   
   • Should it happen that a user with a long distance user interrupts work on the scanner, it is possible for an administrator to find the user and disconnect him from the server.
     To do this, open the command prompt on the server and execute the following code:

     ossvrstat localhost -clients

     
     All connected clients are now listed there with the information whether they currently have a transaction open or not.
     For those with transactions, note the PID (outlined in red),
     
     
     With the following command, a user can be disconnected from the database (XXXXX stands for the respective PID):

     ossvrclntkill localhost -p XXXXX

     
     
   • If the user cannot be determined, the server can be restarted. This will then disconnect all connections to the database. Please note that in the first few minutes after a server restart Hestia reacts rather sluggishly and has to warm up first.
     
3. A query, information or error message is not answered/confirmed. This also blocks the database. This usually occurs in the Hestia application and not in the scanners. Again, the administrator can identify the user and disconnect the user from the database as described in 2.

A pick list with multiple orders

If a picklist with multiple orders occurs in Hestia, this picklist comes from SAP.

Procedure to solve this:

Hestia:
Delete the warehouse receipt and move the moved goods back to their original places.

SAP:
Close pick list. It should then be possible to create a separate pick list for each order.

Picklist cannot be packed

The following error message appears because the associated invoice cannot be created

Reason:

• Invoices already exist in HESTIA for all affected order items.
  • However, an invoice was manually forwarded in the interface monitor because it could not be transferred to SAP.
    • for example, because the pick list was incorrectly cancelled in SAP after it was picked in Hestia.
  • the current forwarding of the invoice only serves to manually assign the existing SAP invoice number and therefore the invoice remains assigned to the order in HESTIA.
    
    (if you do not use the Determine button, you can assign any number to the invoice)
  • SAP then transfers a new pick list for the order, which results in an error message during packing, as the entire order has already been calculated and no new invoice can be created.

Solution:

Open the document history of the affected pick list and search for unusual invoice successors to the order. In our example, it is invoice 9999999999. Open it, deregister and remove the items.

Accordingly, there should also be a terminated successor picklist with the UK invoice 9999999999, which disappears from it after the invoice correction.

Background:

There is no function in Hestia to continue an invoice that cannot be reconciled with SAP.

Possible error messages in the SAP Business One Interface Monitor