Configuration Guide PUBLIC

05-04-18

Configuration Guide for SAP SRM Connectivity

with S/4 HANA
SAP SRM Integration with SAP S/4 HANA
1 Overview of SAP SRM Integration with
SAP S/4 HANA

1.1 Introduction
SAP SRM Integration with S/4 HANA requires configuration and customizing changes on SAP SRM. With SAP
S/4HANA, on premise edition 1511, the maximum field length of the material number is extended from 18 to 40
characters. The appropriate related SAP development entities (domains, structures, table types, and transparent
tables, external and internal interfaces, user interfaces, and so on) have been adapted accordingly. Where required,
automated logic is in place and executed automatically in case a customer converts his current SAP Business Suite
system into SAP S/4 HANA 1511. This MFLE change in S/4 HANA requires configuration and customizing changes
on SAP SRM system, to be able to integrate seamlessly.

The following figure gives an overview of the Material Number Field Length Extension in S/4 HANA system
compared to SAP Business Suite:

Figure 1: Material Number Field Length extension in S/4HANA

The configuration changes have to be implemented manually in Development client using workbench request.
Once these configurations are made, a list of notes must be implemented in SAP SRM. For detailed information
on follow-on notes, refer SAP Note 2229738 or Notes List [ page 3 ].

Integration of SRM Core with S/4HANA supports:

- PR replication via SOA services ( PI/WSRM )
- Classic PO creation via SOA services ( PI/WSRM )
- Contract Replication via SOA services (PI/WSRM)
- Extended Classic PO creation via RFC
Integration of SAP SRM PPS with S/4HANA supports:
- PR replication via RFC
- Extended Classic PO creation via RFC
- Classic PO creation via SOA services ( PI/WSRM )
1.2 Prerequisites

Supported SAP SRM Releases

Configuration and customizing changes of SAP SRM Integration with S/4 HANA is available automatically from the
following releases and support package stacks of SAP SRM Systems:
● SAP SRM 7.0 (SRM_SERVER 700 SPS20)
● EHP1 for SAP SRM 7.0 (SRM_SERVER 701 SPS16)
● EHP2 for SAP SRM 7.0 (SRM_SERVER 702 SPS18)
● EHP3 for SAP SRM 7.0 (SRM_SERVER 7.13 SPS11)
● EHP4 for SAP SRM 7.0 (SRM_SERVER 7.14 SPS02)

Note
For support package stacks below what is mentioned above, configurations and customizing changes have to be
implemented manually in Development client using workbench request.

1.3 Notes List

Please implement the below notes to integrate SAP SRM system with S/4 HANA system

● 2229738 - Interface note1: S4H Adaption in SRM - Configuration Changes

● 2633649 - Interface note1(cont.): S4H Adaption in SRM - Table entries BBP_FUNCTION_MAP
● 2229740 - Interface note2: S4H Adaption in SRM - New Domain, data elements, structures; Changes in existing
structures
● 2229744 - Interface note3: S4H Adaption in SRM - IDOC Change
● 2234467 - Interface Note 4: LOMA - Report to set the material length 40 in customizing V_TMCNV (SRM)
● 2234062 - Imp Note 1: LOMA PO getlist changes for Invoice and GR creation in SRM(SRM with S4H integration)
● 2234164 - Imp Note 2: LOMA Requisition and reservation create changes
● 2234273 - Imp Note 3: LOMA acc,material read, inteprete SRM > S4H
● 2234274 - Imp Note 4: LOMA Tax relevant changes (SRM integration with S4H)
● 2234279 - Imp Note 5: LOMA Invoice read from backend (SRM > S4H)
● 2234317 - Imp Note 6: LOMA Inv items assignment for a PO (SRM --> S4H)
● 2234437 - Imp Note 7: LOMA Invoice processing, idoc invoice posting, invoice simulation
● 2234439 - Imp Note 8: LOMA Goods Movement idoc mapping changes
● 2234440 - Imp Note 9: LOMA - ECS PO transfer changes
● 2234462 - Imp Note 10: LOMA FI document read, product relevance check changes
● 2219958 - Imp Note 11: Plugin changes in S4H for SRM communication
● 2236410 - Imp. Note 12: LOMA - Material Replication changes
● 2254011 - Imp. Note 13: LOMA Idoc mapping issues - SRM_SERVER dependency on SRM_PLUS changes
● 2255708 - Idoc mapping issues - SRM_SERVER dependency on SRM_PLUS
● 2244550 - Unable to create backend purchase order for material which has length more than 18chars
2 Configuration and Customizing Settings
This chapter describes the settings you must make in your SAP SRM system for integration with S/4 HANA. It
also describes the Customizing details for SAP SRM Integration with SAP S/4HANA.

2.1 Creating system type ERP_8.0

System type for SAP_APPL EHP 8.0 and S/4HANA core must be defined in SRM system manually.

● Go to SE11 transaction.
● Open data element BBP_SYSTEM_TYPE.
● Navigate to domain BBP_SYSTEM_TYPE.
● Go to “Value Range” tab.
● Add 2 new values as below

Fix Val Short Description

ERP_8.0 SAP ERP 6.0 Enhancement Pack 8

ERP_8.0H Suite for HANA 1.0

2.2 Creating system type ERP_8.0H

● Go to SE11 transaction.
● Open database table BBP_BACKEND_DEST.
● Maintain backend destination(S/4HANA) aka logical system entry with system type as ERP_8.0H.

Following figure is an example:

2.3 Creating table entry BBP_FUNCTION_MAP
SAP SRM System uses table BBP_FUNCTION_MAP for communicating with the backend system. There might
be different releases (having different data structures) connected to SRM system and we have to convert the
data into the corresponding structure of the backend release.
● Table BBP_FUNCTION_MAP consists the drivers (for the normal function modules) /adaptors (for the object-
oriented programs) of the different backend releases.
● When the SRM communicates to the backend system, we call the function META_BAPI_DISPATCH, and this
reads the table BBP_FUNCTION_MAP.
● In the IMG in SRM under SRM Server > Technical Settings > Define Backend Systems you set up the backend
systems here, and give each one a type. (or access from BBP_FUNCTION_MAP from SM30)

2.3.1 For ERP 8.0 and 8.0H system type

For ERP 8.0 and 8.0Hsystem type, implement SAP Note 2633649 and execute report “BBP_MIG_S4HANA”
to add table entries in BBP_FUNCTION_MAP.

2.4 Compatibility mode and Target mode (in S/4HANA system)

Customizing, based on need this mode must be set by customer. All external interfaces in S/4HANA have been
adopted to be compatible to legacy systems that only know 18 character material fields: The existing fields stay
with their old length; a second long field is added at the end of the structure.
● When the legacy system calls S/4 HANA or is called from there, only the short field is filled - this is the so-called
compatibility mode. Once all surrounding systems are able to work with long material numbers, the S/4 HANA
system can be switched to the target mode.
● Now, longer material numbers can be created and used, therefore only the long fields in the external interfaces
are used, the old / shorter fields stay empty.

2.5 Conversion from compatibility mode to target mode in

S/4HANA(Customizing change)
To force Compatibility mode, set the parameter to C. To force target mode, set the parameter to T. All other
values are ignored. The parameter can be added to your user profile via menu ‘Sytem->User->Profile->Own
Data’.
Example:

If no values are specified for the user, the mode will be compatible mode. To convert the mode to Target mode
set this parameter for RFC user which is used for the communication between SRM and S4HANA system
SM59 userid (Ex: ALEREMOTE)

2.6 Changing to Target mode in SRM

Once the target mode is set in S/4HANA system for SRM communication, we have to set the below in SAP
SRM system.
Go to View COMV_PR_LOGSYS (SM30 Transaction) and add entry as below:

The above entry in SAP SRM indicates, the connected S/4HANA system can use material with Database length
greater than 18 characters.

2.7 Material Replication in SRM

The basic replication set up using CRM middle ware still applicable here both in SRM and S/4HANA system,
while replicating material from S4H system (material with length upto 18 chars) , set the below customizing as
18 (both in SRM and S4H system)

Go to View V_TMCNV (SM30 Transaction)

If the target mode is set to ‘X’ in S4H system for SRM communication, set the material number format as 40
both in SRM and S4H system.

With this material with 40 characters can be maintained in S4H system and the same can be replicated to SRM
system.

2.8 System landscape definition for S/4HANA connection

If customer decided to connect SRM system with S/4HANA, all the notes mentioned in SAP Note 2229738 have
to be implemented in same order mentioned in note. Otherwise only the interface notes are sufficient. First
implement the interface notes as mentioned in sequence then implement the implementation notes as per
sequence. After all notes are successfully implemented, set the system landscape assignment as shown in
figure below. With this assignment, SAP SRM system will call the driver routines relevant for S/4HANA system.

Go to SPRO:
Define the system type for ERP_8.0H as an entry.

2.9 Assigning Basic Idoc type

Material document creation from SRM to S/4HANA system has to use new message type MBGMCR02. This
type has to be mapped with S/4HANA logical system.

Goto WE20
Select “Partner Type LS”
Select the logical system of S/4HANA system

Go to message type MBGMCR

Open the entry and maintain basic type MBGMCR02

With the material document Idoc process will take the basic type MBGMCR02 which has the field
MATERIAL_LONG.
go.sap.com/registration/
contact.html

© 2016 SAP SE or an SAP affiliate company. All rights reserved. No

part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an
SAP affiliate company. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty of
any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only warranties
for SAP or SAP affiliate company products and services are those that
are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.