Document Integration

ScanSPOT automatically creates warehouse tasks for Business Central documents and writes the data recorded on the device back after completion. This applies to every handling area that is enabled in the handling setup, and only to locations that are unlocked for this handling area.

What applies to all documents

ScanSPOT fields on the document. On all supported documents, a ScanSPOT group appears on the General FastTab:

Field	Description
Priority	High or Normal (default). Is passed on to the task.
Task Status	Open or Processed. Is set by ScanSPOT and cannot be changed. Is also shown on the lines.

Task and document stay synchronized.

• Changes to Priority or Assigned User ID on the document are applied to the task.
• If the document or a line is deleted, ScanSPOT deletes the task or the position.
• After a partial posting or partial registration, ScanSPOT creates the task again for the remaining quantities.

Transferred data. For each position, ScanSPOT transfers item, variant, description, location, zone and bin, unit of measure, the open quantity as Target Quantity, and the item tracking requirements. The actual quantity is prefilled with the open quantity, depending on the handling area.

Writing back. After completion, ScanSPOT writes the recorded quantities, bins, and item tracking (lots, serial numbers, expiration dates) to the document. Whether and when the document is posted afterward is controlled by the fields Update On Finish Activity and Post On Finish Activity (see Data Transfer).

Enabling a handling area later. For documents that already exist when a handling area is enabled or a location is unlocked, ScanSPOT does not create tasks. Tasks are created only at the event that is described for the respective document. To do so, reopen released purchase orders, sales orders, and return orders and release them again.

Purchase order and purchase return order

These handling areas are intended for locations where you work without warehouse receipt or warehouse shipment.

When a task is created: on manual Release of the document. For each location, a task with the document number is created. On Reopen, the task is deleted.

Which lines are transferred: Lines with inventoriable items, a positive open quantity, and a location, without drop shipment or special order. For the purchase order, the location must have neither Require Receive nor Require Put-away; for the return order, neither Require Shipment nor Require Pick. In these cases, you work via the respective warehouse documents.

Writing back: bin code, Qty. to Receive or Return Qty. to Ship, and the item tracking.

Posting: Only receipt or shipment is posted, not invoicing. With Print On Post Activity, the document is posted and printed.

Sales order and sales return order

The flow corresponds to purchasing, in the opposite direction: For the sales order, items are taken; for the return order, they are put away. The location rules apply accordingly.

• Before completion, the location and, if bins are mandatory, the bin must be filled in on the device.
• The bin code, Qty. to Ship or Return Qty. to Receive, and the item tracking are written back.
• Only the shipment or return receipt is posted, no invoice. With Print On Post Activity, ScanSPOT prints for the sales order via Post and Send with the document sending profile "Printer"; for the return order, via Post and Print.

Sales orders that were created from an Ad-hoc Sales Order carry the Ad-hoc flag. For them, ScanSPOT does not create a new task on release.

Warehouse receipt

When a task is created: as soon as warehouse receipt lines are created from purchase lines or sales return order lines, for example with Get Source Documents. For each warehouse receipt, one task is created. Lines from transfer orders are not transferred.

Writing back: zone, bin, Qty. to Receive, and the item tracking on the source line.

Posting: The warehouse receipt is posted without confirmation, if you want with a printout of the posted warehouse receipt. For remaining quantities, ScanSPOT creates the task again.

Warehouse shipment

When a task is created: as soon as warehouse shipment lines are created from sales lines or purchase return order lines. For each warehouse shipment, one task is created.

Writing back: zone, bin, Qty. to Ship, and the item tracking.

Posting: The warehouse shipment is posted without confirmation, if you want with a printout. Whether it is also invoiced depends on the posting policy in the user setup.

For checking a warehouse shipment at the workstation, see Checking a warehouse shipment.

Warehouse activities

Supported are put-away, pick, and movement (with directed put-away and pick) as well as inventory put-away, inventory pick, and inventory movement.

When a task is created: automatically when the warehouse activity is created, for example via Create Put-away, Create Pick, or when a movement is created. For each activity, one task is created.

Which lines are transferred: For locations where bins are mandatory, the take lines are transferred for picks and the place lines for put-aways; for movements, both. ScanSPOT automatically adjusts the respective counterpart line when writing back.

Writing back: Lines that were split on the device are also split by ScanSPOT in the activity. Then zone, bin, Qty. to Handle, lot, serial number, and expiration date are set for each line.

Registering and posting: Put-away, pick, and movement are registered without confirmation. Inventory put-away and inventory pick are posted. Invoicing takes place only if the posting policy in the user setup provides for it; for movements, production, and projects, never. For remaining quantities, ScanSPOT creates the task again.

Additional fields for picks

In the handling setup of the pick, on the Additional Process Values tab, you can choose up to two custom fields of the warehouse activity header as Additional Field 1 and Additional Field 2 (see Handling setup card). This applies only to picks in two-step logistics, not to inventory picks.

Item tracking

Whether a position needs a lot, serial number, or expiration date is determined by the item tracking code of the item. On the device, the tracking is scanned or chosen from the selection of available lots or serial numbers.