SAP EWM CLIENT BASIS IMPLEMENTATION
The first step is client basis implementation for the EWM. Therefore, i am explaining shortly step by step at the below for the EWM Client Basis Implementation.
1.Define Own Business System
The system includes data in the many document flow tables as system key. Therefore, the system key is defined at the SCM system. In addition, the SCM system must be same located with EWM (central EWM structure).
Steps in the implementation,
SPRO→SCM EWM→EWM→INTERFACES→ERP INTEGRATION→GENERAL SETTING→DEFINE OWN BUSINESS SYSTEM.
For instance, SAP system number + CLNT + Client number so, Q4HCLNT100
2. Define Logic System to The Business system
The step is important for the communication of ERP and EWM. The reason is that the logic system provides mapping for the system. It needs mapping for the following reasons. The firstly, when deliveries are created, you send information from the ERP system to the EWM. Moreover, EWM contains only the information for the logical system. When the deliveries are triggered by the system, EWM stores information about the business system. Therefore, it provides connection between logical system and business system.
The secondly reason,
If you send any upgrade for the deliveries from the EWM to the ERP side. The system sends mentioned information to the ERP with using logical system.
SPRO→SCM EWM→EWM→INTERFACES→ERP INTEGRATION→GENERAL SETTING→DEFINE BUSINESS SYSTEM.
For example, Business system: Q4HCLNT100 Logic system : Q4HCLNT100
Manual Maint. : Flag is set. Event has occurred.
3. Add and Check of qRFC Destinations
The communication is performed between ERP and EWM side thanks to queues. Therefore, destinations of business system must be added at the client level. You can do at the SMQS transaction code. Also, the runtime should be 60 seconds.
Usually, it has Q4HCLNT100 business system destination. In addition, Q4HEWM100 business system destination will be added at the SMQS transaction code. Totally, altogether should be existed at the screen like Q4HCLNT100, Q4HEWM100.
4. Check qRFC Queues
The queue provides to monitor process status during triggered of two systems (ERP and EWM). The system creates queue named differently for each document type at the SMQ1 and SMQ2. Therefore, queue of qRFC should be fully at the implementation. I share to start with differently named of queue at the SMQ1 and SMQ2 transaction code. You can check at the SMQR transaction code
5. Check qRFC queue Administration
• DLV*• DLW*• EWM*• MMPUR* • WM*• X*• ZQMSKIP
Queues name should depend display programs as below.
6. Create Distribution Model View
Firstly, The BD64 transaction code is used for the distribution mode view. For EWM, the name of distribution starts with the EWM*. For example, EWMQ4H100. When you enter the BD64 screen, you can use ‘Create Model View’ at the above of the screen.
After, the popup will be opened at the screen. You can enter the same name of the short text and technical name field.
7. Create Distribution Model
The Distribution model provides to transfer objects from the SAP ERP system to the SAP EWM system. The objects consist of inbound delivery, outbound delivery etc.
Step in the implementation,SPRO→INTEGRATİON WİTH OTHER SAP COMPONENTS→EWM→BASIC SETTINGS FOR
EWMLINKAGE→GENERATE DISTRIBUTOUN MODEL FROM S4 HANA TO SAP HANA In addition, this implementation is performed for each warehouse number.For instance,Warehouse Number : CHM1
Logic system of SAP EWM: Q4HEWM100
Distribution model view : EWMQ4H100
8. Create Bapi Destination for The Logic System
Standard bapi destination and standard dialog bapi should be added to the EWM logic system at the screen. For this transaction, you can use BD97 screen.
Firstly, The EWM logical system is selected at the screen.
Secondly, the standard bapi destination is created with button where in above in the screen.
EWM logical system should be same for fields of Receiver/server and RFC destination.
P.S: The screenshot is belonging to the development system. Therefore, Receiver/server and RFC destination should be like D4HEWM100 .
9. Check RFC Destination of Logical System
The TBLSYSDEST table where in SE16N transaction code, is used for the checking. The fields of Receiver and RFC destination must be filled as Q4HEWM100 in the table.
10. Maintain Business System Group at The EWM Side
Business system group is the same with ERP client. Step in the information,
SPRO→SCM EWM→SCM BASIS→BASIC SETTING FOR CREATING THE SYSTEM LANDSCAPE→MAINTAIN BUSINESS SYSTEM GROUP
11. Assign Logical System and Queue Type
It needs to assign logical system and queue type for the communication between two system because this implementation provides to determine queue type for the document.
SPRO→SCM EWM→SCM BASIS→INTEGRATION→BASIC SETTING FOR CREATING THE SYSTEM LANDSCAPE→ASSIGN LOGICAL SYSTEM AND QUEUE TYPE
SAP EWM Consultant
Fiori applications have gained great momentum lately, thanks to their responsive design and customizable nature. Large companies, in particular, are...
Hello All,Wishing you a Happy New Year. Sometimes we need to look at more than one message log. As this number increases, the workload starts to...
SAP EWM CLIENT BASIS IMPLEMENTATION The first step is client basis implementation for the EWM. Therefore, i am explaining shortly step by step at the...
IMPLEMENTATION OF SORT RULES FOR WAREHOUSE TASK IN THE RF SCREEN. First, this implementation is valid for the RF screens which include confirmation...
What is SAP Fiori? SAP Fiori is a new user interface for standard SAP applications. It encompasses hundreds of standard applications...
“Reduce the complexity of connecting to Azure.” Adoption of cloud-based IT solutions such as Microsoft’s...
“To migrate or not to migrate, that is the question.” Migration to SAP PO 7.5 should be a key activity on every IT infrastructure roadmap. One of...
Mailiniz başarıyla gönderilmiştir en kısa sürede sizinle iletişime geçilecektir.
Mesajınız ulaştırılamadı! Lütfen daha sonra tekrar deneyin.