SAP WB03 — Display Site (SAP Retail)
A site is a physical retail location: a store that sells to consumers, or a distribution centre that supplies stores. WB01 creates one, WB02 changes, WB03 displays.
The idea worth understanding is that a site is not just a plant. When you create one, SAP creates plant data and a customer master and a vendor master for it, all linked. That is because a site plays all three roles: it holds stock like a plant, it receives goods like a customer when another site supplies it, and it supplies goods like a vendor when it ships to another site.
That is why an internal transfer between two stores can look like a normal sales-and-purchasing process. The sites genuinely are a customer and a vendor to each other.
When you would actually use WB03
- Checking how a store is set up before investigating why goods will not flow to it.
- Finding the customer or vendor number that belongs to a site.
- Confirming which distribution centre supplies a store.
- Checking the assortment a site is assigned to when an article will not list.
What the screen looks like
Site data
The fields, in plain English
T001W-WERKSThe site identifier, stored in the same field as a plant. Anywhere in logistics that asks for a plant, a retail site is what you supply.
Whether the site is a store or a distribution centre. It determines which data the system expects and how the site behaves in replenishment — a DC supplies, a store receives and sells.
Watch out: Set at creation and awkward to change afterwards, because so much configuration keys off it.
Which distribution centre normally replenishes this store. Drives automatic replenishment and stock transport orders.
Watch out: If goods are not flowing to a store, this is one of the first fields to check.
The master records generated alongside the site. The customer number is used when the site receives goods internally; the vendor number when it supplies them.
Watch out: Useful to know when tracing an internal document that appears to involve an unfamiliar customer or vendor — it is very often a site.
The sales-side organisational assignment, needed for the site to sell and for pricing to resolve.
Step by step
- 1Enter the site ID.
- 2Read General data for site category and supplying site.
- 3Note the generated customer and vendor numbers if you are tracing internal documents.
- 4Check the Address tab for the physical location used in deliveries.
- 5Check the assortment assignment when investigating why an article is not listed there.
Errors you will hit, and what they mean
Site ST01 does not exist
Why: Wrong ID, or you are looking at a plant that was created as a plain plant rather than as a retail site.
Fix: A plant created outside the retail site process will not open in WB03. Check whether it exists as a plant instead.
Goods are not replenishing to a store
Why: Missing or wrong supplying site, or the article is not listed there.
Fix: Check the supplying site here, then the article Listing view in MM43. Those two cover most cases.
Common questions
What is the difference between a site and a plant?
A site IS a plant, plus a customer master and a vendor master created together and linked. The extra records let the site trade internally with other sites.
Why does a site have a customer number?
So it can receive goods from another site through the normal sales and delivery process. Internal transfers use the same machinery as external ones.
What is the difference between WB03 and WB02?
WB03 displays, WB02 changes. Display first is the safer habit on master data this widely referenced.
Transactions that go with WB03
Reading about it only gets you so far
Practise SAP transactions in a safe simulated environment and keep what you learn.
Practise SAP transactions hands-on
Interactive modules, games, and an AI tutor — free to start.
Get started free →