Hanna Siefert, SAP

Documentation of TM-EWM Integration – Both systems

Embedded

1|Page
 Date Name Reason Version

04.06.2020 Hanna Siefert, SAP Initial Document Creation 1.0

12.06.2020 Hanna Siefert, SAP Include Input from Markus Becker 1.1

Content
1 EWM/TM embedded system 3
1.1 Check if point to point connection is enabled. 3
1.2 Perform SLD check 3
1.3 Perform Transaction Soamanager 3
1.4 Run srt_admin 4
1.5 Central Configuration Soamanager 4
1.6 Enter values for SLD Buffer Table 5
1.7 Enter own Business System 5
1.8 Define EWM Integration Profile 5
1.9 Define FO Type Customizing 5
2 Settings in EWM/TM System Client 000 6
2.1 Execute setup in client 000 6
3 Soamanager Setup in central system 6
3.1 Enter System name in Domain system 6
3.2 Create Domain 7
3.3 Add User Data 8
3.4 Setup integration scenario (central) 9
3.5 Add Logical Determination of Receiver using service groups 11
4 Appendix 13
4.1 Additional customizing needed 13
4.2 After a client copy 15
4.3 Execute report srt_wsp_setup_icf 15
4.4 Setup service user if failing in SRT_ADMIN 18
4.5 Optional: Check in client 000 if BGRFC settings successful 19
4.6 In case you want to get rid of warning IDEMPOTENCY in srt_admin (not mandatory) 21
4.7 SOAMANAGER Delete caches 22
4.8 Retest data of already triggered action 22
4.9 Check Delivery document in case LDAP is not triggered 24

2|Page
1 EWM/TM embedded system
1.1 Check if point to point connection is enabled.
In order that the transfer of documents will be working via Soamanager/WSRM Setup the
following customizing needs to be enabled.
Tx SPRO, Cross-Application Components > Processes and Tools for Enterprise
Applications > Enterprise Services > Point-to-Point Enablement for Asynchronous
Enterprise Services->Activate Support for Point2Point Communication.
Create new and check the box

1.2 Perform SLD check

It is very important that the result of the sldcheck (not in the popup but on the screen in the
backend) will revert a system under the call of function
“LCR_GET_OWN_BUSINESS_SYSTEM”.
Perform sldcheck (transaction SLDCHECK). Is own business function found? If not ask the
basis/security team to add system in SLD System.

1.3 Perform Transaction Soamanager

When the SLDCHECK was successful open transaction Soamanager and check the Business System
here. If nothing is maintained, please select checkbox “Get Business System from SLD”

a. Tx SOAMANAGER ->Technical Administration > SAP Client Settings: Get Business

System from SLD

3|Page
1.4 Run srt_admin
There is a transaction that is doing most of the settings on its own. like creating ICF notes,
create a Delay Logon user etc.

Run transaction “Srt_Admin” in “Run technical setup” mode

Remark: For TM-EWM Integration the “Idempotency” message can be ignored. If you want to
change something here please go to the appendix 4.6 .
In case there is an issue with the ICF nodes check Appendix 4.3.

1.5 Central Configuration Soamanager

For the Soamanager Setup it is recommended that there is one central system.

Access the transaction “soamanager” from Easy Access Menu

a. In Tab Technical Administration select the SAP Client Settings
b. In Sub Tab Central Configuration press Edit, select the checkmark for Central System
and press Save.
c. In the pop-up enter system user, e.g. ALE_REMOTE username and password.

4|Page
 d. Close soamanager

1.6 Enter values for SLD Buffer Table

During the TM-EWM Integration also a buffer table for the SLD entry is called. In case
that is not entered automatically by the system please also enter your system data there.
In customizing (transaction SPRO), navigate to SAP Transportation Management >
Transportation Management > Integration > Define SLD Data of Business Systems (table
/SCMB/TBUSSYS) and validate the entry for the SAP EWM system. Unset
the ManualMaint. flag to ensure the entry is updated from the SLD.
Flag set. Event has occurred.

1.7 Enter own Business System

In customizing (transaction SPRO), navigate to Extended Warehouse Management-
>Interfaces->ERP Integration->General Settings ->Define Own Business System

Make sure your Business System is maintained here.

1.8 Define EWM Integration Profile

The integration TM-EWM is based also on the settings of the integration profile. Please create an
entry here in case there is none.
Tx: Spro->Transportation Management > Integration-> Integration with SAP
Extended Warehouse Management->Define EWM Integration Profile

1.9 Define FO Type Customizing

The TM-EWM Integration will only be working if the FO Type is setup correctly:

Check if in customizing all important TM-EWM relevant flags are set

Tx: Spro->Transportation Management > Freight Order Management-> Freight Order
-> Define Freight Order Types

a. „Document Creation Relevance” must be „E”, otherwise no communication to EWM

b. „Immediate Processing” has to be set, otherwise Update Propagation Indicator is not set on FU
what can cause various errors later on
c. „Output Profile”. If it is not set, no PPF Action is triggered (meaning no communication to EWM), a
standard which can be used: /SCMTMS/TOR

5|Page
2 Settings in EWM/TM System Client 000
2.1 Execute setup in client 000
In tcode srt_admin execute the automatic setup in case the Srt_Admin call of your client hasn’t
created the BGRFC settings completely.

If you want to check if the BGRFC is setup correctly you can also perform checks as per Appendix 4.5.

3 Soamanager Setup in central system

All below actions will happen in transaction soamanager from Easy Access Menu.
A ‘central’ shall now appear in title line. If you have the old session from soamanager still open,
please close it first until you see the “Central” in the title line.

3.1 Enter System name in Domain system

In Soamanager tab Technical Administration select Domains.
Go in edit mode of the system and enter the logical system if empty and save.

6|Page
3.2 Create Domain
In Soamanager tab Technical Administration select Domains.
a) Press create and enter the following values
Field Value
Domain Name DO_TM_EWM
Weight 1
Description Domain TM-EWM

b) Press Add Systems and select TM/EWM system from the pop-up list.
c) Under Tab profile in the security tab select “User ID/Password” checkbox. This is done in the
sample setup if you want to have another option to do the setup, you can also do your settings.
d) Select checkbox “Secured communication”
e) In general Tab, select State as Active
f) Save the Domain

7|Page
3.3 Add User Data
As in above settings the Authentication Method “User ID/PW” was selected we need to enter the
Logon Data Name: e.g. service user ALE_REMOTE or TM_EWM_USER or as per your user setup.
In soamanager tab Service Administration select Logon Data Management
a) Press the create button
b) In 1: General enter the following values
Field Value
Type Template
Logon Data Name e.g. ALE_REMOTE
Description
c) Press Next
d) In 2 Credentials enter the following values

Field Value
Authentication Method User/Password or X.509
User Name ALE_REMOTE
Password *PW of the user of selected system

e) Press Finish
f) Activate the user with the activation Symbol

8|Page
 g) Go to tab: Assignment. If username and password is the same for TM and EWM System add
the user as following:
h) Press create
i) Press next
j) Press Finish

3.4 Setup integration scenario (central)

In tcode soamanager tab Service Administration select Integration Scenario Configuration
Create integration scenario (e.g. TM_EWM_LDAP) with service group connections for system with by
following below steps
- TM service group and EWM inbound interface
- EWM service group and TM inbound interface

a) Select create and enter the name “TM_EWM_LDAP” and the description “TM EWM Peer
to Peer Communication” and press button create
b) In sub-tab Service Group connection press the create button. 1st Step is Assign IBC
References
1) As Actor 1 get the value of the one embedded System via drag and drop from below
client list (in both embedded both systems are the same)
2) As Actor 2 get the value as well of the embedded System via drag and drop from below
client list
3) Press next

9|Page
c) In 2 Assign Service Groups choose connection type: Service Group Based, Request Response
1. Add in Actor 1 Service Group /SCMTMS/TOR_LDG_APPT_RQ for sending the Request
message from TM to EWM
1. Remark: IF following messages is coming execute 4.7. SOAMANAGER Delete caches

2. Add in Actor 2 Service Group /SCWM/SRVG_TM_SR for the response message from
EWM to TM
3. Press next

d) In 3 Define Matching Interfaces

10 | P a g e
 1. Check, that the automatically determined provider interfaces are as follows for Actor 1
TransportationOrderLoadingAppointmentRequest_in {http://sap.com/xi/EWM/Global}
Check, that the automatically determined provider interfaces are as follows for Actor 2
TransportationOrderLoadingAppointmentNotification_In {http://sap.com/xi/TMS/Global}
2. Press Finish
3. Save

e) Activate.
Release the Integration Scenario Configuration, press release button and in pop-up release
all the actions

Release.

3.5 Add Logical Determination of Receiver using service groups

The following step needs to just be executed for the interface TM->EWM. As a system could have
multiple EWM Systems that determine which system to use. In the embedded scenario with 1 TM
and 1 EWM that is just an easy receiver determination -> All messages are going to one client.
Remark: If multiple EWM systems are used those need to be maintain here as well

The reason why this is not needed backwards is because EWM always sends the information back to
the TM System where the message is coming from.
a) In soamanager tab Service Administration select Add Logical Determination of Receiver
using service groups
b) Press the create button

11 | P a g e
 c) In step 1: Enter the following values:
Field Value to input Input method
Service Group /scmtms/tor_ldg_appt_rq Manual typing
Provider IBC Reference EWM system Drag and Drop from below list

d) Press Next
e) In step 2 press Create new Routing and enter following values
Field Value
Priority 100
First Drop Down Logical Syst. (Rec.)
Second Drop Down Inclusive
3rd Drop Down Contains Pattern
4th Drop Down *

f) Press create new routing

g) Press the finish button.

3.6 Check completeness of the settings

Once the setup is completed and you want to do a check on the completeness you can do the
following:
a) In soamanager tab Tools select in area Health Check “Execute Health Check and explore
results”
b) Select “Run” in order to run the health check (remark: It might take some time for the results to
come)
c) In the popup select your system
d) In the result screen you see couple of checks that were performed, all should be green except
a. Technical settings of SOAP runtime (The idempotency can still be in red- error-state)
and in none used clients the flag can be red
b. Self Ping – can still be red

END

12 | P a g e
4 Appendix

4.1 Additional customizing needed

Additional customizing might be needed if message runs on an error on EWM side

1) Means of Transports must be in sync, most likely more valid for a non-
embedded scenario

2. On EWM side customizing needs to be done how to form a TU and a vehicle:

13 | P a g e
3. Package types must be customized

4. Manual task in EWM System (EWM)

Map Packaging material to MTR

Tcode /n/SCWM/PM_MTR
Field Value

MTr 0001

Pack.Material EWMS4-TRUCK00

Optional checked

Seq. PMs blank

No PMs in MTr blank

Cont. PM checked

5. In case on EWM side you want to use the shipping cockpit following sicf needs to be
activated.
SICF for shipping cockpit

14 | P a g e
 • Sap/public/bc/icons
• Sap/public/bc/icons_rtl
• Sap/public/bc/pictograms
• Sap/public/bc/webdynpro/*
• Sap/public/bc/webicons
• Sap/bc/nwbc/*
• Sap/bc/webdynpro/scwm/sco & sco_EXEC & shp_assign_door_lp & shp_assign_tu_door

4.2 After a client copy

After a client/system copy the soamanager setup is no longer correct as it referred to the original
systems. In order to delete the central configuration and all the soamanager setup execute the
report SRT_WSP_INITIALIZE_CEN_LOC_CFG in transaction se38 in S/4 System and in EWM System.

a) First in test mode afterwards

b) Without test mode:

In case the report is not available in your system, please notice: The report comes with
note 0002748671 and note 2830754 might be helpful as well.

4.3 Execute report srt_wsp_setup_icf

In case Icf nodes are were not created by tcode srt_admin you can also run the program
SRT_WSP_SETUP_ICF in transaction se38.

15 | P a g e
Execute the setup.

Execute

16 | P a g e
17 | P a g e
4.4 Setup service user if failing in SRT_ADMIN

18 | P a g e
4.5 Optional: Check in client 000 if BGRFC settings successful
In tcode as per screenshot below check all the settings:
SBGRFCCONF

19 | P a g e
20 | P a g e
4.6 In case you want to get rid of warning IDEMPOTENCY in
srt_admin (not mandatory)
Execute report srt_ws_idp_customize in se38

Afterwards check in tcode srt_admin again if Idempotency warning shall be gone

21 | P a g e
4.7 SOAMANAGER Delete caches
In tcode soamanager tab Service Administration select Design time Cache
Select second tab Administration, check the checkbox “Force Build of cache” and press
on build it will take some time.

This step will take some while.

4.8 Retest data of already triggered action

1) Go to transaction tcode: SPPFP
2) Enter following data:
Action definition TOR_LDAP_REQ,
Processed at: 4: When saving
Created from (Date): 01.03.2020
And execute

22 | P a g e
Select a message and “Process the message”.

6. Check in SRT_Moni with the “Message ID” mentioned in above screenshot in column “Sort
field”

7. Check in EDI for the Freight Order Number

23 | P a g e
 3) Scheck in Tcode /SCWM/TU with the correct Warehouse ID for the FO Number

In case message is not sending put the debugger in following classes:

a. Set debugger in /SCMTMS/CL_PPF_SERV_TOR_B2B->EXEC_TOR_LDAP_REQ or
in /SCMTMS/CL_TOR_LDAP_REQ->PROXY_CALL place in line of Call function
"LCR_GET_BS_DETAILS" and trigger the message again.

4.9 Check Delivery document in case LDAP is not triggered

Check if the Delivery of the Freight Order is pointing to the correct EWM System. In order to do
so check in tcode /BOBF/TEST_UI with object /SCMTMS/TOR
a. Go on search-> By alternative Key
b. Go on plus symbol
c. Select Root – Tor_ID
d. Enter your Freight Order you would like to send.
e. Go in sub-node ITEM_TR
f. Select the main Cargo Item
g. Check in WM_LOGSYS the logical System of the EWM System if this is a correct
entered. Please check the EWM setup

4.10 Components for incident creation

In case you can’t process with the setup or you have an issue with the sending of the Loading
Notification message please create a ticket under the following component:

a) BC-ESI-WS-ABA-CFG in case of issues with Soamanager

b) TM-INT-EWM in case on issues on SAP TM side
24 | P a g e
c) SCM-EWM-IFT in case of issues on SAP EWM side

25 | P a g e