EWM Value-Added Services: Labelling and Shrink-Wrapping (and Kitting) at a VAS Work Center
Some customers want work done on goods before shipping. A VAS order, created from the delivery and the customer's VAS requirements, routes the goods through a VAS work center where the activities are performed and confirmed — then they continue to the goods-issue zone.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01Delivery with VAS requirements
The delivery is VAS-relevant: EWM creates VAS order VAS-0000501 with two activities.
Business scenario
Demo Retail requires its own price labels on each unit and shrink-wrapped cartons. 30 EA of FG-2000 are picked for its delivery.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
Delivery with VAS requirements open in twin
The delivery is VAS-relevant: EWM creates VAS order VAS-0000501 with two activities.
The VAS order tells the warehouse exactly what extra work to do.
- 02
Pick to the VAS work center open in twin
30 EA go to VAS-01 instead of straight to the goods-issue zone.
The step is part of the process, not an afterthought at the dock.
- 03
Labels applied, film wrapped open in twin
The operator has finished both activities. What next?
Confirmation captures effort and consumption of auxiliary packaging, and can be required before goods issue.
- 04
Unconfirmed VAS open in twin
With the VAS order still open, the warehouse cannot prove the work was done or charge for it, and goods issue may be blocked.
Whether it blocks goods issue is configuration dependent; the missing record is a problem either way.
- 05
Confirm VAS and stage open in twin
VAS order confirmed. The labelled, wrapped goods move to GI-ZONE.
Effort data can be used for internal costing or billing the customer for the service.
- 06
- 07
Shipped with the customer's labels open in twin
Delivery → VAS order → pick to VAS → confirm → stage → ship.
VAS turns the warehouse into a light-assembly and customisation site.
SAP documents
Stock impact
| Step | Plant / SLoc | Stock type | MvT | Change |
|---|---|---|---|---|
| Pick to the VAS work center | 1000 / AFS · PICK-02-05 | Unrestricted use | — | −30 EA |
| Pick to the VAS work center | 1000 / AFS · VAS-01 | Unrestricted use | — | +30 EA |
| Confirm VAS and stage | 1000 / AFS · VAS-01 | Unrestricted use | — | −30 EA |
| Confirm VAS and stage | 1000 / AFS · GI-ZONE | Unrestricted use | — | +30 EA |
| Goods issue | 1000 / AFS · GI-ZONE | Unrestricted use | 601 | −30 EA |
Accounting impact
Goods issue
TypicalGoods issue
- Dr Cost of goods sold (GBB/VAX)₹36,000
- Cr Inventory — finished goods (BSX)₹36,000
Standard COGS posting.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
- 601GI for deliveryReversal: 602
Performs customer- or product-specific work on goods in the warehouse — labelling, packing, kitting — and records it per order.
Transactions & Fiori apps
- /SCWM/PACK — Work center (VAS activities are confirmed at the work center; the exact transaction depends on release — requires configuration validation)
- /SCWM/PRDO — Outbound Delivery Order
- /SCWM/MON — Warehouse Monitor
- Warehouse Monitor
Differences by SAP version
No VAS framework in classic WM.
VAS and kitting in embedded and decentralized EWM.
Availability depends on scope.
Configuration
VAS relevance and activities
Configuration dependentDefined in packaging specifications and condition records.
VAS confirmation as goods issue prerequisite
Configuration dependentWhether open VAS orders block goods issue.
Prerequisites
- VAS activities and packaging specifications with VAS levels
- VAS work center in the storage control
- Determination of VAS relevance per product/customer
Master data
- Packaging specification (VAS levels)
- Defines the activities and auxiliary materials.
Organizational structure
- Warehouse EW01
- Work center VAS-01
Tables
| Table | Description |
|---|---|
| /SCWM/ORDIM_C | Tasks to and from the VAS work center |
Integration
- SDVAS requirements per customer and delivery.
Common errors
“No VAS order created”
Likely causes: No packaging specification with VAS for this product/customer; Delivery not VAS-relevant
Where to look: Packaging specification determination
Troubleshooting
Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.
CHECK 1
VAS
- Packaging specification with VAS?
- Storage control includes the VAS step?
Interview questions
What are value-added services in EWM?
Activities performed on goods in the warehouse — labelling, packing, oiling, kitting. EWM creates VAS orders from packaging specifications, routes goods through VAS work centers via storage control, and records confirmation of each activity, which can be used for costing or billing.
Quiz
References
- SAP SE — SAP Help Portal: Value-Added Services in EWM (source)
- SAP SE — SAP Help Portal: Kitting (source)
Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.
Version history
| Version | Change |
|---|---|
| 1.0.0 | Initial version. |