Before SAP EWM can work its magic, it needs to talk to your ERP system. This means setting up the plumbing that lets these two SAP landscapes share data smoothly.
A. Defining Logical Identities
Logical Systems:
- In both ERP and EWM, you assign a unique name (e.g.
ZMECLNT800,T43CLNT800) that represents each client. - These logical system names show up in ALE (Application Link Enabling) and RFC (Remote Function Call) setups—think of them as “DNS entries” for your SAP servers.
RFC Destinations:
- Create an RFC user in each system, then configure an RFC connection in both ERP and EWM that points to the other’s logical system name.
- This link carries function calls and transactional messages back and forth.
B. Grouping Systems and Setting Controls
Business System & Group:
- EWM stores a “business system” key in its document flow. You map each logical system to a business system, then bundle them into a Business System Group (BSG).
- BSGs let you handle scenarios where multiple ERP plants or systems feed into one EWM, or vice versa, without mixing up materials.
Version-Control Parameters:
- In EWM’s Customizing, you’ll find a table (“Control Parameters for ERP Version”) where you specify exactly how data fields and versions behave between ERP and EWM.
- You can tweak entries here if you’re on a newer ERP release or need special field mappings.
Linking Inventory and Deliveries
Next up is telling ERP which of its warehouses are managed by EWM—and how deliveries should flow.
A. Assigning the Warehouse Number
- ERP Warehouse Definition:
- In ERP’s Warehouse Management (WM) IMG, create a warehouse number that corresponds to your EWM warehouse.
- Tie it to the correct plant (
1000) and storage location (0001) that hold the raw inventory data.
- Activation Flags:
- Comm. WM: Set to “Queued and Serialized Asynchronous RFC.” This ensures every delivery document is reliably queued to EWM.
- Unchecked Deliveries: Choose if CRM-created deliveries (with reduced checks) should flow into EWM.
- Distribution Mode: “Immediate” pushes every new delivery into EWM right away; “Stop” holds them until you manually release via VL06D.
- Serial/Batches in EWM: Flags like SN Dec. WM and BatchDetEW let you control whether EWM handles serial-number tracking or batch determination.
- GR from EWM Only: Locks goods-receipts (e.g., for production orders) so they only post in EWM, preventing ERP users from bypassing warehouse checks.
- Deliv.Chg: In S/4HANA, this allows ERP to still tweak a delivery after it’s hit EWM—useful for last-minute address changes.
B. Defining How Deliveries Travel
- Distribution Model (BD64):
- Under Outbound Model, pick Objects like Inbound Delivery, Outbound Delivery, Production Material Request—or simply select All to cover every scenario.
- Map the ERP warehouse number, the EWM logical system, and your chosen objects. This one table drives all delivery replication.
- Warehouse Number Mapping in EWM:
- In EWM’s Customizing, there’s a table to map ERP Warehouse → EWM Warehouse (and optionally Business System). Make sure every ERP warehouse has a matching EWM entry.
Fine-Tuning the Integration
With basic links in place, you’ll refine settings so ERP and EWM speak the exact same language.
A. Communication Profiles
- ERP Integration Profile (EWM):
- In decentralized EWM, you pick a set of control parameters that govern how deliveries, changes, and cancellations travel between systems.
- Embedded EWM uses an all-in-one Process Profile instead—no separate table, but identical options.
B. Master Data Flow
- Embedded EWM: Shares master data (materials, bins, customers) directly—no replication needed.
- Decentralized EWM on NetWeaver: Uses CIF/qRFC to push master data one-way from ERP to EWM.
- Decentralized EWM on S/4HANA: Prefers ALE with IDocs or the Data Replication Framework (DRF) for material and bin replication.
C. Transactional Data Flow
All delivery and posting-change messages use qRFC to guarantee ordered, once-only delivery. Whether it’s an inbound delivery arriving in EWM or a goods-issue confirmation going back to ERP, it’s queued, serialized, and safe against network blips.
Putting It All Together
By the end of these configurations, you’ll have:
- A stable RFC/ALE backbone linking ERP and EWM.
- Warehouse numbers in ERP that mirror EWM, complete with communication flags and distribution models.
- Business system mappings and groups** to keep multi-system landscapes in sync.
- Clear master/data replication paths—automatic in embedded, CIF/IDoc in decentral.
- Reliable transactional messaging via qRFC for deliveries and posting changes.
With these foundations solid, every inbound and outbound delivery will flow seamlessly between your ERP and your SAP EWM warehouse—ready for putaway, picking, and all the advanced processes you’ll configure next.