SAP EWM Availability Groups: ROD and AFS Storage Locations

Eight in the morning, the day after go-live. Receiving has been scanning pallets since dawn, the quantities show up fine in S/4HANA, and yet the phone rings: sales order processing cannot confirm a single customer order. The stock exists, but it is not sellable.

I have watched this play out at every warehouse start-up, and the answer comes down to the concept of ROD and AFS storage locations in SAP EWM: two ERP-side stock locations that separate what has just arrived at the dock from what is genuinely available for sale. Behind that pair works a precise piece of customizing, the availability groups, and that is what you need to understand to stop fielding that phone call.

ROD and AFS: two storage locations on the ERP side, not in EWM

Let us start by correcting a widespread mistake, including in the first version of this article: the official labels are Received on Dock (ROD) and Available for Sale (AFS). You often see “Receive On Dock” or “Available For Sales” in blogs and project documentation; those variants do not match the official SAP terminology.

Second clarification, and a more structural one: these two objects do not live in EWM. They are Inventory Management storage locations, on the SAP ERP or S/4HANA core side. In the standard setup proposed by SAP, they are often named RD00 and AF00. EWM itself never reasons in terms of plant and storage location: it works with its own notions, the availability group and the stock type, which bridge to the ERP. If you are still weighing the warehouse management options in S/4HANA, the comparison choosing between WM, Stock Room Management and EWM sets the scene before we get into the mechanics.

The split of roles between the two is simple:

ROD captures the stock that has been received but not yet put away: the pallet is at the dock, under inspection or in internal transit to its final location. AFS gathers what has reached its final bin and that availability (ATP) can commit to customer orders. A frequently overlooked detail, covered in EWM warehouse structures: this two-storage-location scenario is optional. A single storage location is enough if you do not need to distinguish, on the ERP side, stock still being put away from available stock. We will come back to that in the decision section.

The mechanics of availability groups: how EWM replaces plant and storage location

Here is the heart of the matter, and the part most explanations skim over. In EWM’s quant data you will find neither plant nor storage location: the system replaces them with the availability group + stock type pair. The whole ROD-to-AFS switch rests on two mapping chains configured in customizing.

First chain: the combination of plant, storage location, logical system and warehouse number is assigned to an availability group. Second chain: the combination of availability group and non-location-dependent stock type (the well-known FF, “unrestricted use”) determines the EWM stock type. The table below sums up the full mapping of the standard model:

In practice: a pallet in RD00 is seen by EWM as a quant in stock type F1; as soon as it is put away, its stock type becomes F2, which corresponds on the ERP side to AF00. The stock type alone therefore carries the information that the ERP expresses with two distinct storage locations.

One version detail is worth noting: with S/4HANA, the availability group field went from 4 to 10 characters. Where older systems used opaque codes such as 0001 and 0002, you can now adopt a meaningful “plant/storage location” naming, for example SPCW/AF00. On a project, that single naming choice makes the customizing self-documenting.

These mappings obviously assume that master data flows correctly between the two systems; that is the job of the data synchronization between SAP ERP and EWM, which deserves its own guide.

The full flow: from goods receipt to the automatic posting change

Let us now walk through the life cycle of a pallet, because that is where the concept takes on its full operational meaning.

At receiving, the goods receipt posting creates the stock in the ROD storage location, in stock type F1 on the EWM side. At that moment, the ERP sees unrestricted-use stock in RD00: it knows the goods have arrived, but it also knows they are not sellable yet. EWM then generates the putaway warehouse task, the operator confirms it, and the pallet reaches its final location.

This is where the mechanism becomes elegant: the moment the product reaches its final bin, EWM automatically triggers a posting change that switches the stock from ROD to AFS. No manual transaction, no action on the ERP side: EWM drives, the ERP follows. Readers coming from the classic WM world will note the kinship with final bin determination on the classic WM side; the difference is that EWM materializes the completion of putaway through a stock movement visible to the ERP.

In complex putaway scenarios, with process-oriented storage control chaining unloading, a pass through a work center and then final putaway, the timing becomes finer: the goods receipt is posted as soon as the first warehouse task is confirmed, the unloading one, while the posting change waits for the actual arrival at the final bin. Between the two, your ERP faithfully shows stock that has arrived but is not available: exactly what the sales order processing team in my introduction would have liked to understand.

Customizing: configuring the availability groups step by step

The full configuration takes five steps, all on the EWM customizing side except the first. Setting up availability groups for Inventory Management documents the detail of each screen.

1. 1
   Create the two storage locations on the ERP side

   In the Inventory Management organization, create the storage locations dedicated to the EWM warehouse, for example RD00 for Received on Dock and AF00 for Available for Sale, attached to the relevant plant.

2. 2
   Define the availability groups on the EWM side

   In the Define Availability Group activity, create one availability group per storage location. Take advantage of the 10-character field for a meaningful plant/storage location naming.

   SPRO path:

   SCM Extended Warehouse Management → Extended Warehouse Management → Goods Receipt Process → Configure Availability Group for Putaway

3. 3
   Configure the stock types

   In the Configure Stock Type activity of the same customizing node, check the link between your availability groups and stock types F1 and F2, with the non-location-dependent stock type FF assigned to both. Rename the descriptions for readability, and set the Stock Type Role if a particular scenario requires it (customs stock, scrapping).

4. 4
   Assign the availability group to the storage types

   In the Assign Availability Group to Storage Type activity, Goods Movement Control area, link the AFS availability group to the final putaway storage types: this is the setting that triggers the posting change on arrival at the final bin.

5. 5
   Map the ERP storage locations to EWM

   Add one entry per storage location in the mapping table: plant, storage location, logical system and warehouse number point to the matching availability group.

   SPRO path:

   SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP Integration → Goods Movements → Map Storage Locations from ERP System to EWM

Two additional settings are worth knowing. First the Stock Type Role column, which lets you describe additional stock scenarios: normal stock, customs blocked stock or stock intended for scrapping (Scrapping Stock). Then the Goods Receipt Mode, in the interface control parameters: it lets you defer sending the goods receipt to the ERP until the receipt or putaway is fully complete. Handy to cut down the noise, but to be used knowingly: during that delay, the stock posted in EWM does not yet exist on the ERP side, and the gap between the two systems is normal.

Do you really need 2 storage locations? Pitfalls and side effects

The ROD and AFS scenario is the standard SAP ships, and it answers a real business question: giving the ERP, and therefore ATP and the sales teams, a faithful view of what is committable. If that distinction adds nothing for your organization, for example a production warehouse where all received stock is immediately consumable, a single storage location simplifies the model and saves one posting change per pallet.

Because that is the first side effect to anticipate: each receipt potentially generates two movements on the ERP side, the goods receipt to ROD and then the posting change to AFS. And the volume climbs quickly with radio frequency: when operators confirm their warehouse tasks one by one on the scanner, each confirmation triggers a distinct stream of material documents in the ERP. Combined with the ROD and AFS scenario, the document volume can double compared with a grouped receipt. Nothing blocking, but your colleagues in material accounting and archiving will appreciate the heads-up.

Second point of vigilance: if you activate the deferred Goods Receipt Mode, factor the temporary ERP/EWM gap into your inventory reconciliation procedures. A controller comparing the two systems in the middle of a receiving wave will wrongly conclude there is an anomaly. Document the behavior and train the teams: the gap then becomes what it is, a simple timing offset, not an error.

One last practitioner’s tip: name your availability groups with the meaningful format the 10 characters of S/4HANA allow. A consultant discovering your system two years after go-live will understand SPCW/AF00 without opening the mapping table.

FAQ: ROD and AFS storage locations in SAP EWM

The ROD and AFS concept is a good illustration of the EWM philosophy: let the warehouse drive the physical reality, and automatically translate that reality into the ERP’s language. Once the availability groups are in place, the mechanism runs on its own and nobody thinks about it any more, until the day a stock gap puzzles an auditor. You now know what to tell them. To complete the picture on the master data side, carry on with the guide on data synchronization between SAP ERP and EWM: it is the other half of the contract between the two systems.

Keep reading

01

SAP Tutorials

SAP EWM Master Data Integration: ERP Sync with CIF, ALE, DRF

Since the move to S/4HANA, the question "how do you synchronize data between SAP ERP and EWM" no longer has the same answer, and many projects still get it wrong...

Michael A. 7 min read

02

SAP Tutorials

SAP EWM RF Framework: Navigation, Profiles and Mobile Setup

Everyone uses the RF framework in SAP EWM without seeing it: it is the terminal screen the warehouse operator scans. But the real value is not in the scan, it...

Michael A. 10 min read

03

SAP Tutorials

SAP SD Pricing Determination: The Condition Technique

Sooner or later, on a project, a user shows you a sales order and asks why the displayed price is not the one they expected. You open the line, you...

Michael A. 14 min read

04

SAP Careers

SAP ECC vs S/4HANA: the key differences for your SAP career

If you look into SAP for your career, two acronyms keep coming up: ECC and S/4HANA. One is the older generation of SAP's ERP, the other is the current version....

Michael A. 11 min read