In Public Cloud, the mapping between Plant → Storage Location → ERP Warehouse Number is part of the foundation organizational structure and is fixed once deployed. You cannot simply “edit” the mapping in CBC to merge two existing plants into one ERP warehouse number. This is because a plant is a legal/logistical entity in S/4HANA and is the top-level org unit for inventory valuation. An ERP warehouse number is always assigned to exactly one plant in standard Public Cloud WM/EWM integration. Cross‑plant ERP warehouses are not supported in Public Edition; each plant’s stock is managed separately in ERP.
On the implication side, to “merge” two plants into one ERP warehouse, you would need a re‑implementation or data migration to redesign the org structure — essentially closing one plant and moving its materials, stock, and processes into the other plant’s warehouse.
In Public Cloud, you cannot change the assignment in customizing (SPRO → Logistics Execution → Warehouse Management → Interfaces → Assign Warehouse Number to Plant/Storage Location) and it’s part of SAP’s restricted config. Any change would require an SAP Expert Configuration request and is only possible within the supported design rules (still one plant per ERP warehouse).
Below chart shows the difference between two scenarios
The recommended approach would be if the business goal is to operate one physical warehouse for two plants in Public Cloud, you must still model them as two separate ERP warehouses (one per plant) and manage them in EWM as two logical warehouses — even if physically they are in the same building. Cross‑plant consolidation can be handled at process level (e.g., shared resources, harmonized bin structures) but not by merging ERP warehouse numbers.
Bluesky| User | Count |
|---|---|
| 29 | |
| 14 | |
| 14 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.