SAP Business One Bin Locations: Configure and Control Stock by Location - tutorial featured image

Publications

SAP Business One Bin Locations: Configure and Control Stock by Location

Hector Pincheira

Hector Pincheira

CIO | CTO
Digital Strategy & Technology Innovation

items

SAP Business One Bin Locations It is the answer when your warehouse no longer fits in your head. Imagine the scene: a customer calls asking for an urgent shipment, the system confirms there are 40 units in stock, but the warehouse worker walks down three aisles before finding them, because no one knows for sure which rack they ended up in after the last rearrangement. The ERP was right about the quantity. It was wrong, however, about the only thing that mattered at that moment: where.

That gap between «how much I have» and «where it is» is one of the most expensive and least discussed bottlenecks in the logistics operation of an industrial or commercial SMB. It does not appear on any income statement as a separate line, but it leaks out in lost man-hours, slow picking, shipping errors, and consequently, in customers who stop trusting your delivery times. This article takes you step-by-step through the activation of Bin Locations in SAP Business One and provides the SQL queries—in SQL Server and SAP HANA—to control stock by location from day one.

Why Bin Locations Change the Conversation in Your Warehouse

SAP Business One, in its standard configuration, manages inventory at the warehouse level. That means the system tells you that there are 500 units of SKU X in the Central Warehouse, but it does not tell you if those 500 units are in rack A-12, distributed across three different locations, or mixed with a batch close to expiration at the back of the aisle. For small operations, with few SKUs and single-environment warehouses, that granularity is not critical. However, as soon as your catalog grows, your warehouse multiplies in levels, or your operation begins to handle batches and serial numbers, the absence of bin location control becomes a structural problem, not an anecdotal one.

Bin Locations solve that exact gap: they break down each warehouse into specific physical locations—aisle, rack, level, position—and allow every inventory movement to be recorded not just by warehouse, but by the exact coordinate where it occurred. The result is not only visual order. It is real traceability, faster picking, and above all, the ability to make layout decisions based on data rather than intuition.

SAP Business One Bin Locations - Warehouse Racks Organized by Location
Every rack, every level, every position: that is how Bin Locations turn a warehouse into a navigable system.

Prerequisites before activating Bin Locations

Enabling this feature is not a simple checkbox. Therefore, before touching the settings, validate these points with your operations team:

  • Inventory at zero or squared. SAP Business One requires that the warehouse has no open balances of pending documents (unclosed sales or purchase orders that affect stock) at the time of activating bin location management in that warehouse.
  • Physical map of the cellar. First define your coding structure (for example, AISLE-RACK-LEVEL-POSITION) on paper or in Excel, before creating it in the system. Changing it after operations have started is costly.
  • License and version. Bin Locations is available starting from SAP Business One 9.0 onwards, in both SQL Server and HANA versions, at no additional license cost.
  • Role of the warehouse worker. Consider that, upon activation, each movement (entry, exit, transfer) will require indicating the origin and destination location, which adds a step to the daily operational workflow.

Step-by-Step Tutorial: Activation and Configuration

The process runs in four stages. Below is the detail of each one.

1. Enable company-level location management

Go Administration → System Initialization → General Information, tab Inventory, and check the box Manage storage locations by warehouse. This action is at the company level and, once confirmed with open inventory in any warehouse, it can no longer be deactivated without SAP support, so thoroughly validate the previous prerequisite.

2. Define the location code structure

On the same screen, configure the format of the bin code: how many segments you'll use (for example, Aisle-Shelf-Level) and the separator between them. This structure is then automatically replicated when generating new locations, so defining it correctly from the start saves manual work later on.

3. Enable the warehouse and create the locations

In Administration → Definitions → Inventory → Warehouses, open the warehouse you want to manage by locations and activate the tab Enable storage locations in this warehouse. Below, you can create the locations one by one from Inventory → Storage location data → Storage locations, or generate them in bulk by defining ranges (for example, Aisle 1 to 5, Rack A to D, Level 1 to 3), which saves hours of data entry in a medium-sized warehouse.

4. Assign the default location and migrate the existing stock

Define, for each item or for the warehouse in general, a default location (default bin), so that future transactions have a suggested automatic destination. Then, run a Inventory Adjustment or a Warehouse Transfer initial for moving the already existing stock from the «unlocated» warehouse to the actual bins. This step is, in practice, the most time-consuming, because it requires someone to physically walk through the warehouse and confirm what is in each rack.

SAP Business One Bin Locations - worker verifying locations with barcode scanner
The initial migration of inventory to actual locations is the step that requires the most field discipline, but also the one that unlocks the most value afterward.

How to check stock by bin with SQL

Once the functionality is active, SAP Business One saves the bin location information in a specific set of tables. The table OBIN contains the location master; OIBQ accumulate stock in bin for items without batch or serial number management; OBBQ do the same for batch-managed items; and OBTL record each bin transaction, line by line. These four tables, combined, give you complete visibility. Below are two essential queries for your day-to-day.

Current stock by location (items without batch/serial number)

SQL Server

SELECT
    T0.[WhsCode]                AS 'Warehouse',
    T2.[BinCode]                AS 'Bin Code',
    T1.[ItemCode]                AS 'Item Code',
    T3.[ItemName]                AS 'Description',
    T1.[OnHandQty]                AS 'In-Bin Stock'
FROM OIBQ T1
INNER JOIN OBIN T2 ON T1.[BinAbsEntry] = T2.[AbsEntry]
INNER JOIN OWHS T0 ON T2.[WhsCode] = T0.[WhsCode]
INNER JOIN OITM T3 ON T1.[ItemCode] = T3.[ItemCode]
WHERE T1.[OnHandQty]  0
    AND T0.[WhsCode] = 'BOD-01'
ORDER BY T2.[BinCode], T1.[ItemCode]

SAP HANA

SELECT
    "T0"."WhsCode"                AS "Warehouse",
    "T2"."BinCode"                AS "Bin Code",
    "T1"."ItemCode"                AS "Item Code",
    "T3"."ItemName"                AS "Description",
    "T1"."OnHandQty"                AS "Stock in Bin"
FROM "OIBQ" "T1"
INNER JOIN "OBIN" "T2" ON "T1"."BinAbsEntry" = "T2"."AbsEntry"
INNER JOIN "OWHS" "T0" ON "T2"."WhsCode" = "T0"."WhsCode"
INNER JOIN "OITM" "T3" ON "T1"."ItemCode" = "T3"."ItemCode"
WHERE "T1"."OnHandQty"  0
    AND "T0"."WhsCode" = 'BOD-01'
ORDER BY "T2"."BinCode", "T1"."ItemCode"

Batch stock by location, with expiration date

For operations with lot traceability—food, pharmaceuticals, chemicals—you need to cross-reference the bin with the lot number and its expiration date. This turns the report into a FEFO (First Expired, First Out) management tool, not just a location tool.

SQL Server

SELECT
    T2.[BinCode]                AS 'Location',
    T0.[ItemCode]                AS 'Item',
    T3.[DistNumber]                AS 'Batch Number',
    T3.[ExpDate]                AS 'Expiration Date',
    T0.[OnHandQty]                AS 'Batch Quantity'
FROM OBBQ T0
INNER JOIN OBIN T2 ON T0.[BinAbsEntry] = T2.[AbsEntry]
INNER JOIN OBTN T3 ON T0.[ItemCode] = T3.[ItemCode] AND T0.[BatchNum] = T3.[DistNumber]
WHERE T0.[OnHandQty] > 0
ORDER BY T3.[ExpDate] ASC

SAP HANA

SELECT
    "T2"."BinCode"                AS "Location",
    "T0"."ItemCode"                AS "Item",
    "T3"."DistNumber"                AS "Batch Number",
    "T3"."ExpDate"                AS "Expiration Date",
    "T0"."OnHandQty"                AS "Batch Quantity"
FROM "OBBQ" "T0"
INNER JOIN "OBIN" "T2" ON "T0"."BinAbsEntry" = "T2"."AbsEntry"
INNER JOIN "OBTN" "T3" ON "T0"."ItemCode" = "T3"."ItemCode" AND "T0"."BatchNum" = "T3"."DistNumber"
WHERE "T0"."OnHandQty" > 0
ORDER BY "T3"."ExpDate" ASC

Variations and use cases

The same table base allows you to build additional reports depending on the maturity of your operation. For example, you can generate an «empty bins» alert (locations with a defined capacity but no assigned stock) by joining OBIN with OIBQ using a LEFT JOIN, to identify idle space in your layout. Similarly, if your warehouse handles cross-docking, you can filter by locations marked as «transit» to monitor how long merchandise stays there before leaving, a silent yet decisive indicator for your OTIF.

Another high-value variation is the «last location by item» report: a query that, using MAX(CreateDate) on OBTL, tells you where each SKU was last moved, which is useful when the warehouse worker loses track of a slow-moving item. Consequently, it is not just about knowing how much you have, but rather building, with these same tables, a signal system that anticipates problems before they reach the customer.

SAP Business One Bin Locations - warehouse aisle with coded shelving
A well-coded aisle is, at its core, a physical database that your ERP can read in real time.

Best practices and common mistakes

From the experience of supporting implementations, these are the most repeated errors and, therefore, the ones most worth preventing:

  • Encode locations without hierarchical logic. Using codes like «UBI-001», «UBI-002» without any relation to the physical position forces the warehouse worker to memorize instead of deduce. The Aisle-Rack-Level structure is always superior.
  • Activate the functionality without training the warehouse team. The system doesn't fail; the discipline of recording the location with each movement fails. Without that habit, the OIBQ and OBBQ data become outdated and the report loses all its usefulness.
  • Do not define «special» locations. Every warehouse needs bins for returns, quarantine, or damaged goods. Omitting this forces improvisation later, when it is already more costly to fix.
  • Ignore the maximum capacity per bin. SAP Business One allows you to define maximum volume or weight per bin location; failing to set this up removes a valuable alert that prevents physical over-stocking in a rack.

Official SAP Resources

To delve deeper into the technical configuration, SAP Business One has official documentation on the SAP Help Portal, under the «Bin Locations» section of the Inventory module, in addition to the SAP Notes available on the SAP Support Portal for your specific version (9.0 onwards). If your implementation partner has access to the SAP Business One Customer Portal, you will also find the official e-learning courses on advanced inventory management there.

Conclusion: from intuition to data

Bin Locations are not a decorative feature within SAP Business One. They are, in practice, the bridge between a warehouse managed by memory and one managed by data. The difference is measured not only in picked minutes saved, but in your operation's capacity to scale without chaos growing at the same speed as your catalog. Like any real transformation, it does not lie in checking a box: it lies in sustaining the data discipline that the feature demands, day after day, until it becomes invisible.

Do you want the complete details on how to integrate these queries into a real-time picking dashboard, with automatic alerts for empty and nearly expiring bins? That level of depth—with complete SQL and advanced configuration steps—is available to Strategic Circle members at hectorpincheira.com.

Most Read

QlikSense Hierarchy: parent-child chart of accounts expanded by levels
QlikSense Hierarchy: the Chart of Accounts That Doesn't Add Up
QlikSense Sum TOTAL: share of each family over the total
QlikSense Sum TOTAL: the Percentage That Changes When You Filter
SAP Business One Inventory Revaluation - featured image of the tutorial
SAP Business One Inventory Revaluation: Fix Wrongly Loaded Costs
Empty chamber with wooden benches: the counterweight that required being present to be used
The Veto You Had to Say in Person: Your Decisions With No Counterweight
SAP Business One customizations - featured image of the pre-upgrade audit tutorial
SAP Business One Customizations: Pre-Upgrade Audit
SAP Business One Customer Concentration - featured image of the tutorial
SAP Business One Customer Concentration: Measure Your Risk with SQL

RELATED ARTICLES