Supply Chain Management Blogs by Members
Learn about SAP SCM software from firsthand experiences of community members. Share your own post and join the conversation about supply chain management.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Integrate It! SAP EWM and SAP ERP integration via CIF. Step-by-step guide

gorbenkoteh
Active Participant
‎2020 Aug 17 12:05 PM
19,128
You have Distributed System Landscape with EWM Installed on an Own Server and ERP (S/4HANA)  and want to integrate them via CIF-interface*. This blog-post contains a step-by-step guide and some tips based on hands-on experience.


*CIF (Core Interface) is technically part of the integration for master and transaction data between S/4HANA and SCM-system


Quote.



“The increased scale and complexity of SAP and non-SAP systems challenges require that we look for ways to simplify the system-integration requirements”


This quote about a series of blog-posts (“Integrate it…”) about integration between different SAP and non-SAP systems


Another posts from this series (The list is being updated.)


Integrate It! - LUW debug step by step guide



Integrate it! – SAP and MES integration. Step-by-step guide



Integrate it! – Qlick View/Sense and SAP integration. Step-by-step guide



Integrate it! – SAP BW. Extract data from remote MS SQL Server. Step by step guide



Integrate it! – Qlick View/Sense and SAP HANA integration. Step-by-step guide



Resolution.



Step 1. Create  RFC-users


Step 1.1. Create RFC user in ERP


Transaction - SU01 - User Maintenance

User: RFCREMOTE (for example)

User Type:  Communication

Profile: S_ENTW_SHOW


Step 1.2. Create RFC user in EWM


Transaction - PFCG - Role Maintenance

Copy role /SCWM/ERP_EWM_INTEGRATION in /ZSCWM/ERP_EWM_INTEGRATION

and Generate profile

Transaction - SU01 - User Maintenance

User: RFCREMOTE

User Type:  Communication

Role: /ZSCWM/ERP_EWM_INTEGRATION





Links:

Check For or Create an RFC User and ALEREMOTE User in SAP ERP


SAP Extended Warehouse Management 9.5 Security Guide




Step 2.Create RFC-settings


Step 2.1 Create RFC connection in ERP

Transaction - SM59 - RFC Destinations

Type: 3(ABAP Connection)

Name: <SID>CLNT<CLIENT No>

where SID, CLIENT No relevant for ERP

Target host: EWM host

User/Pass: User RFCREMOTE  and password from Step 1



Step 2.2. Create RFC connection in EWM

Transaction - SM59 - RFC Destinations

Type: 3(ABAP Connection)

Name: <SID>CLNT<CLIENT No>

where SID, CLIENT No relevant for ERP

Target host: ERP host

User/Pass: User RFCREMOTE  and password from Step 1



Step 3. Define Logical system


Step 3.1. Settings in ERP:

Transaction -BD54 - Define Logical System

Define Logical System for <SID>CLNT<CLIENT No>

where SID, CLIENT number relevant for EWM

Step 3.2.Settings in EWM:

Transaction - BD54 - Define Logical System

Define Logical System for <SID>CLNT<CLIENT No>

where SID, CLIENT number  relevant for ERP



Step 4. Activate business functions in the Switch Framework


Step 4.1. Settings in ERP:

Transaction - SFW5 - Switch Framework Customizing

Activate:


LOG_SCM_EWM_INT






Step 5. Multiple SPRO settings


Step 5.1. Settings in ERP. The defining queue for transfer to SAP EWM

Start transaction SPRO and in the IMG, choose Logistics Execution >Extended Warehouse Management Integration >Basic Setup of Connectivity  >Define Queue for Transfer to SAP EWM.

Links:

The defining queue for transfer to SAP EWM


Step 5.2. Settings in ERP. Basic Settings for Setting Up the System Landscape

Start transaction SPRO and in the IMG, choose

Integration with other SAP components > Extended Warehouse Management >

Basic Settings for Setting Up the System Landscape >Specify SAP APO Release






Step 6.  Setting up QOUT Scheduler


Step 6.1. Settings in ERP:


Transaction - SMQS -Setting up QOUT Schedule


Select Register without activation.


Destination  - RFC destination to EWM

Max. Conn.                    2

Max. Runtime                60 (Default)

W/o tRFC                        Empty (Default)

Scheduler Monitoring  1.800 seconds (Default)







Step 6.2. Settings in EWM:


Transaction - SMQS -Setting up QOUT Schedule


Select Register without activation.


Destination  - RFC destination to ERP

Max. Conn.                    2

Max. Runtime                60 (Default)

W/o tRFC                        Empty (Default)

Scheduler Monitoring  1.800 seconds (Default)





Step 7. Setting up QIN Scheduler


Transaction - SMQR - Registering a Queue Name


Step 7.1. Settings in ERP:


EWM*, QM*, DLW*,QI*, WM queues must be scheduled

Handler (program name) - /SPE/QUEUE_DISPLAY_TOOLS


Step 7.2. Setting in EWM:

CF*, DLW*,QI* queues must be scheduled










Step 8. Target System Independent Settings in CIF


Step 8.1. Settings in ERP:


Transaction - CFC9 - Target-System-Ind. Settings in CIF

My friendly advice:  Change Transfer for Master Data to 1 - ALE Change Transfer Periodic








Step 9.  Integration Jobs





Step 9.1. Settings in ERP:

Few words about standard ABAP integration reports

report RIMODDEL - Delete the old, inactive version of the integration model

report RIMODGEN - Create a new version of the corresponding integration model

report RIMODAC2 - Deactivate/Activate the new version

report RIMODINI -  Initial transfer of certain master data without Deactivating the associated integration model.


Job (my friendly job name purpose):

INTEGRATION_ERP_EWM_BATCH

INTEGRATION_ERP_EWM_MAT

INTEGRATION_ERP_EWM_CUS

INTEGRATION_ERP_EWM_VEN


Steps inside of each of this job:






Explanation of job steps:


No1 - Deactivate integration model. Only non-active models can be deleted.

No2 - Delete obsolete integration models. Clean-up phase.

No3 - Generate integrate model.

No4 - Activate the integration model and transfer it to the target system.





Step 10. Monitoring



Monitoring is one of the benefits of using integration jobs

A friendly advice use function - "Job monitoring" in Solution Manager 7.2

Look at more about monitoring in my separate blog-post SAP Monitoring and Situation Center. Step-by-step guide


See chapter "Step 6 / Tab #6. Job Monitoring"

You immediately receive an e-mail alert if the problem with integration occurred.








Troubleshooting.


Problem:


Transaction SMQ2

Queue in SYSFAIL status

Reason: Batch/Material/etc was blocked


Resolution:


Schedule Job

INTEGRATION_ERP_EWM_RSQOWKEX (my friendly job name purpose)

Job frequency: 5 minutes

ABAP-report:  RSQOWKEX

Variant: CIF








Schedule Job

INTEGRATION_ERP_EWM_RSQIWKEX (my friendly job name purpose)

Job frequency: 5 minutes

ABAP-report:  RSQIWKEX

Variant: EWM


Variant explanation:






Notes/Links:


552322 - RSQOWKEX and RSQIWKEX






Problem:


Integration Materials/Batch  is failed with the error:






Resolution:


Transaction - CUNI - Unit of Measures

Inconsistency between ERP/EWM at this point may lead to an error during ERP/EWM integration




Problem:


Integration Customers/Vendors is failed with the error:





No location ZZZ exists for mapping entry XXX of cat.YYY BSG S4HANA



Resolution:






Conclusion


Approach to SAP ERP - SAP EWM integration was provided.

Labels in this area
Popular Blog Posts