Contact
- Let’s connect!
- +49 931 784957-25
- hello@ososoft.de
- Kontaktformular
Choosing an embedded or decentralized EWM solution is undoubtedly not trivial. Is 24/7 operation necessary? How should the master data be transferred? Below we will show you the advantages and disadvantages.
In addition, we will briefly examine the two application scenarios.
SAP EWM is traditionally operated with its own system ID. If the productive ERP system is "P01", for example, the SAP EWM system has an example system ID of "EWP". Since these are two different systems, it is necessary to connect the systems to each other using SAP standard interfaces. For EWM versions that are based on the R/3 stack, the master data is transferred via CIF (Core Interface). The CIF interface is part of SAP APO. For newer EWM versions that are based on S/4 HANA, master data is transferred via ALE.
Master data is distributed to EWM initially or using a change pointer via the distribution model (transaction BD64). Transaction data is transferred from the SAP ERP system to the SAP EWM system and vice versa using qRFC (queued remote function call).
SAP EWM embedded is part of the S/4 stack. Basically, SAP EWM - like SAP WEM before it - is operated as an independent module within the ERP system. In the first versions of SAP EWM embedded, the interfaces were used exactly as in a decentralized connection - with the difference that the sender and receiver are the same logical system.
In more recent versions, these hard system boundaries are increasingly softened and, for example, redundant customizing is removed.
When designing the system, great care should be taken not to create any direct dependencies on the ERP system (e.g. a synchronous RFC from the EWM to the S/4 HANA system or similar). Logistics must be able to be productive for a certain period of time without the S/4 HANA system. Realistically, it must be acknowledged that this can only be a few hours at most. At the very least, the IM postings (WE, WE, etc.) generated by the SAP EWM in the ERP system cannot be permanently postponed.
When programming in SAP embedded, make sure that you still use SAP EWM's own framework. SAP EWM provides the necessary ABAP objects to meet logistics requirements. Even if there is a temptation to "skim" a table that is not part of the module, this usually leads to subsequent problems.
