Barcode scanning in SAP Business One without a WMS: what the Service Layer can and can't do

What the Service Layer is.

The Service Layer is the web interface of SAP Business One. It is part of every B1 10 installation, runs on the SAP server, and talks HTTPS and OData, the same language a browser or a phone app speaks. SAP's own Web Client and mobile apps use it. So does every modern add-on that wants to read or post something in B1 without installing anything inside the B1 client.

The part that matters for a warehouse: the Service Layer applies the same business rules as the B1 client. A goods receipt posted from a scanner goes through the same checks as one typed on screen: stock, batches, serial numbers, bin locations, authorisations, approval procedures. If B1 would refuse it on screen, it refuses it from the scanner. Nothing is written into the database behind B1's back.

The Service Layer is installed with B1 but is not always switched on. Your B1 partner enables it in the System Landscape Directory; it usually listens on port 50000. A scanner app on the warehouse wifi only needs to reach that port, nothing else.

What a scanner can post without a WMS.

Everything below is a standard B1 document. A scanner app fills it in from barcodes and posts it through the Service Layer; from then on it is an ordinary document in B1, with the usual journal entries, reports and history.

• Receiving: a goods receipt PO on an open purchase order, line by line, with batch, serial number and bin. Also a receipt without a purchase order.
• Picking and delivery: the pick list from B1 (Pick and Pack Manager), updated per scanned line, then a delivery per customer.
• Transfers: a stock transfer from bin to bin, from warehouse to warehouse, a whole bin in one go, or an inventory transfer request from B1 processed on the scanner.
• Counting: an inventory counting document from B1, counted blind or with the book stock shown, and then the inventory posting that corrects the stock.
• Returns and corrections: a return from a customer, a return to a supplier, a goods receipt or goods issue with a reason and a G/L account.
• Production: issue components to a production order, return what was left over, report completion with rejects and by-products.

Batches, serial numbers and bin locations go on every one of those documents, exactly as B1 expects them. Units of measure work too: if a box barcode is set up in B1 as the barcode of the box unit, scanning the box posts the right quantity of pieces.

What B1 already has, and most warehouses never switch on.

A lot of what people buy a WMS for is already in B1, waiting to be configured by the partner:

• Bin locations per warehouse, with attributes, a receiving bin and a default bin per item.
• Pick lists through the Pick and Pack Manager, released per sales order or per batch of orders.
• Inventory counting documents with a counter per document and a separate posting step.
• Batch and serial number management with expiry dates and the choice of when they are required.
• Unit of measure groups with a barcode per unit, so a piece, a box and a pallet can each have their own label.
• Several barcodes per item in the Bar Codes table, for suppliers that each use their own code.

A scanner app does not replace any of that. It uses it. That is also why a good scanner app changes nothing in your B1 database: it needs no extra fields or tables, because the fields are already there.

Where B1 stops and a WMS begins.

A warehouse management system keeps its own stock administration next to B1 and synchronises the two. That is what makes it expensive, and it is also what makes it powerful. You need one when your warehouse needs things B1 does not do:

• wave planning: picking many orders in one walk and splitting them afterwards;
• voice picking, pick-to-light, conveyor or sorter control;
• slotting and labour management: deciding where every item belongs and measuring every picker;
• multi-step put-away, cross-docking, 3PL billing for stock you hold for others;
• thousands of order lines a day, with several shifts and dozens of scanners.

If that is your warehouse, buy a WMS and plan an implementation. If your warehouse has a few scanners, receives with a pen and counts from a printed list, you don't have a WMS problem. You have a keyboard problem, and a scanner app that posts B1's own documents solves it for a fraction of the price. B1 stays the only truth about your stock.

What the Service Layer can't do, honestly.

• Offline posting. A document is posted the moment it is sent. Without wifi a scanner can keep scanning, but nothing lands in B1 until the connection is back.
• Several counters on one counting document are a B1 client feature that the Service Layer handles differently; most scanner apps work with one counter per document.
• Speed. Every posting is a full B1 transaction. A receipt with two hundred lines takes seconds, not milliseconds. For a small warehouse that is fine; for a sorter it is not.
• A licence. The Service Layer logs in as a SAP user, and that user needs a licence. How that works for warehouse staff is in the guide on licences.

What you need before you start.

• SAP Business One 10 with the Service Layer enabled and reachable over HTTPS on the warehouse wifi.
• One technical SAP user for the scanner app, with the right authorisations; see the licence guide.
• Bin locations, batch management and barcodes set up in B1 the way your warehouse really works. A scanner only makes a messy master data problem faster.
• Android scanners or phones; which ones is in the guide on scanners.

How KScan does it.

KScan is our scanner app for exactly this situation. It runs on one Windows server next to SAP, keeps its own small database only for sessions and settings, and reads and posts everything through the Service Layer, in the standard documents above. Nothing is added to your B1 database. Every document KScan posts carries a remark with the name of the employee who scanned it. No WMS, no implementation project; the product page has the full list of what is and isn't in.