Form OneByOneCheckingForm

• Unit name: Forms.OneByOneChecking
• Form name: OneByOneCheckingForm
• Old form name: unit204 (form204)

Synopsis

The form searches for an outgoing order, and allows to investigate the status of the order.

Functionalities

1. An edit allows to enter an order number (aOrderID).
2. A click on a button or pressing enter in the edit fetches the order.

   SELECT * from OUT where AVIZ=aOrderID
   

3. If no order was found, a message

   Order :aOrderID was not found.
   

   is shown. Focus is returned to the edit box.
4. If the order is found, the order data are displayed:
5. BlockNo The batch number for the order.
6. Country The destination country.
7. AVIZ The order number.
8. DClient Destination client.
9. DClientTown The destination town.
10. DClientCountry The destination country.
11. If the order is found, the order count summary details are displayed:
12. Total: QT1
13. Scanned: QT2
14. Not Scanned: QT3 (=QT1-QT2)
15. If the order is found, the order article count summary details are displayed in a grid. (result of OUTDetailsArticleCountSummary) Records where QT1 equals QTY2 are displayed green, others are displayed red.
16. A button 'Refresh list' executes the refresh action.
17. An edit box 'Check article' allows to enter an EAN code (aEAN). (bar code). Pressing enter executes the CheckArticle action.
18. A button allows to execute CheckArticle action.

Actions

Refresh

1. Active if summary counts are active.
2. Refreshes both summary counts.

CheckArticle

Checks an article and updates counts. 1. Active only if an article EAN code is entered. 2. When executed, the article corresponding to the aEAN code is located in the global article lookup. (check EANCODE,EANCODE1,EANCODE2,EANCODE3,EANCODE4).
3. If the article is not found, then a message is displayed:

EAN barcode :aEAN was not found in the article list.

Focus is returned to the edit box. 4. If the article for this is found, The record corresponding to the article is located in the OUTDetailsArticleCountSummary dataset, using the article code. details in the grid. 5. If the record corresponding to the article is not found, then a message is displayed:

There is no such article in the job: :Name

6. If the record corresponding to the article is found then the quantities asked (Qt1) and checked (Qt2) are compared. If they are equal, a message is displayed:

Article is already scanned: :Name

7. The service call DeliveryControl.UpdateOutgoingArticleCountt is executed with the article code and order ID. 8. After the call returns (also in case of EWarta exception) the data is refreshed and the EAN edit box is cleared and focused.

Tables/Views

• OUT (filter on order)
• Article (filter on EAN)
• OUTDetailsCountSummary

  SELECT
    sum(qty) as QTY1,  
    sum(isnull(checkedqty,0)) as QTY2
  FROM
     OUTDETAILS
  WHERE
     (AVIZ=AVIZNO=:aOrderID)
   ```
  * **OUTDetailsArticleCountSummary**
  

  SELECT outdetails.artcode, sum(outdetails.qty) as QTY1,
  sum(checkedqty) as QTY2 max(PickedBy) as PKB, Max(CheckedBy) as CKB, NAME2 FROM OUTDETAILS INNER JOIN ARTICLE ON (artcode=name ) WHERE (AVIZ=:AOrderID) GROUP BY outdetails.artcode, NAME2 ORDER BY outdetails.artcode

  * **ArticleStockCount**
  

  SELECT outdetails.ID, outdetails.qty, outdetails.QtyCF, outdetails.CheckedQty, outdetails.ID, PickedBy, outdetails.qty-isnull(outdetails.CheckedQty, 0) as RESTQTY from Out inner join Outdetails on aviz=avizno WHERE blockno=+'+label10.caption+' and AVIZ=+'+Label12.Caption+' AND ARTCODE=+'+Edit1.Text+' and outdetails.qty>isnull(outdetails.CheckedQty, 0) order by outdetails.ID asc

```

Needed Service Calls

Call 1

Call 2

Reports