INTERNAL

2020-11-09

Configuration Guide for SAP SRM Connectivity

with SAP S/4HANA
© 2020 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

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

1.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 List of SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Creating system type ERP_8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Creating system type ERP_8.0H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
2.3 Creating table entry BBP_FUNCTION_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Compatibility mode and Target mode (in SAP S/4HANA system). . . . . . . . . . . . . . . . . . . . . . . . 8

3.1 Conversion from Compatibility mode to Target mode in S/4HANA (Customizing change). . . . . . . . . . 8
3.2 Changing to Target mode in SRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Material Replication in SAP SRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1 System landscape definition for S/4HANA connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2 Assigning basic IDOC type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 SRM Component Planner Integration with SAP S/4HANA system. . . . . . . . . . . . . . . . . . . . . . 12

6 SAP S/4HANA system with DIMP LAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

2 INTERNAL Content
1 Overview of SAP SRM Integration with
SAP S/4 HANA

Introduction

SAP SRM Integration with SAP S/4HANA requires configuration and customizing changes in SAP SRM. With
SAP S/4HANA on premise edition 1511 or above, 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/4HANA 1511 or above. This Material Field Length
Extension (MFLE) change in SAP S/4HANA requires configuration and customizing changes in SAP SRM
system, to be able to integrate seamlessly.

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

The configuration changes must 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 2229738 .

Integration of SRM Core with SAP 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) and via TRFC
● Extended Classic PO creation via RFC

Integration of SAP SRM PPS with SAP S/4HANA supports:

● PR replication via RFC

● Extended Classic PO creation via RFC
● Classic PO creation via SOA services (PI/WSRM)

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

Overview of SAP SRM Integration with SAP S/4 HANA INTERNAL 3
1.1 Prerequisites

Configuration and customizing changes of SAP SRM Integration with S/4HANA 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 must
be implemented manually in development client using workbench request.

1.2 List of SAP Notes

Implement the below notes to integrate SAP SRM system with S/4HANA system.

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

● 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, interpret 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

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

4 INTERNAL Overview of SAP SRM Integration with SAP S/4 HANA
 ● 2244550 - Unable to create backend purchase order for material which has length more than 18chars
● 2838679 - Note for Report NOTE_2836354
● 2836354 - SRM Component Planner integration with S/4 HANA system

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

Overview of SAP SRM Integration with SAP S/4 HANA INTERNAL 5
2 Configuration Settings

This section describes the settings you must make in your SAP SRM system for integration with S/4HANA. It
also describes the Customizing details required for SAP SRM Integration with SAP S/4HANA.

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

2.1 Creating system type ERP_8.0

Do the following to define the system type ERP_8.0:

1. Go to SE11 transaction.
2. Open data element BBP_SYSTEM_TYPE.
3. Navigate to domain BBP_SYSTEM_TYPE.
4. Go to Value Range tab.
5. Add 2 new values as shown 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

Do the following to create system type ERP_8.0H.

1. Go to SE11 transaction.
2. Open database table BBP_BACKEND_DEST.

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

6 INTERNAL Configuration Settings
 3. Maintain backend destination (SAP S/4HANA) as 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 the 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 must convert
the data into the corresponding structure of the backend release.

The table BBP_FUNCTION_MAP contains the drivers for the normal function modules, and adaptors for the
object-oriented programs of the different backend releases. When the SAP SRM system communicates with
the backend system, SAP SRM system calls the function META_BAPI_DISPATCH, and this reads the table
BBP_FUNCTION_MAP.

Give each system a type by executing the Customizing Define Backend Systems, part of SRM Server
Technical Settings . You can also do the same by accessing the table BBP_FUNCTION_MAP using the
transaction SM30.

For ERP 8.0 and 8.0H system types

For ERP 8.0 and 8.0H system types, implement the SAP Note 2633649 and execute the report
BBP_MIG_S4HANA to add entries in the table BBP_FUNCTION_MAP.

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

Configuration Settings INTERNAL 7
3 Compatibility mode and Target mode (in
SAP S/4HANA system)

You can set the compatibility mode and target mode in Customizing, based on your business requirements.

All external interfaces in SAP S/4HANA are compatible with legacy systems that know only 18-character
material fields. The existing fields remain with their old length, and a second long field is added at the end of
the structure.

When the legacy system calls SAP S/4HANA system, or is called from there, only the short field is filled - this is
the compatibility mode. Once all surrounding systems are able to work with long material numbers, the S/
4HANA system can be switched to the target mode.

Now, longer material numbers can be created and used. This way, only the long fields in the external interfaces
will be used.

3.1 Conversion from Compatibility mode to Target mode in

S/4HANA (Customizing change)

To use the S/4HANA system in Compatibility mode, set the MFLE_SWITCH parameter value to C.

To use the system in Target mode, set the MFLE_SWITCH parameter value to T.

To add the parameter value to your user profile, navigate to System User Profile Own Data .

For example, see the below figure:

If no values are specified for the user, by default, the mode will be compatible mode. To convert the mode to
Target mode, set this parameter for the RFC user which is used for the communication between SRM and S/
4HANA system SM59 userid (For example, ALEREMOTE).

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

8 INTERNAL Compatibility mode and Target mode (in SAP S/4HANA system)
3.2 Changing to Target mode in SRM

After the Target mode is set in S/4HANA system for SRM communication, you must do the below setting in
SAP SRM system.

Using SM30 transaction, go to the view COMV_PR_LOGSYS, and add entry for QE4CLNT534.

The above entry in SAP SRM indicates that the connected S/4HANA system can use materials with database
length greater than 18 characters.

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

Compatibility mode and Target mode (in SAP S/4HANA system) INTERNAL 9
4 Material Replication in SAP SRM

The basic replication set up using CRM middleware continues to be applicable both in SAP SRM and SAP S/
4HANA systems. When replicating material from SAP S/4HANA system (material with length up to 18 chars),
set the customizing as specified in the SAP Note 2234467 where you can execute the report
BBPCU_MATNO_SET40.

The report BBPCU_MATNO_SET40 will set the material field length more than 18 characters in SAP SRM side, in
the customizing table TMCNV. Without executing this report, you cannot set the material length more than 18
characters.

Material field length can be set (more than 18) from this report only if the SAP S/4HANA system is set to target
mode. That is, the report will check whether the customizing in COMV_PR_LOGSYS has the entry for target
mode.

Also, as described in SAP Note 2472424 , there are few changes done for the exchange of materials from
SAP S/4HANA system to SAP SRM system, compared to the way it worked when ERP system is involved.

In ERP system, the material (product) GUID is stored in the table NDBSMATG16, and this is used during data
replication. In S/4HANA system this has been changed and material GUID is stored in the MARA table itself
(field SCM_MATID_GUID16) and the table NDBSMATG16 is not used anymore.

For successful replication of material from S/4HANA system to SRM system, the field SCM_MATID_GUID16
should have the required value. The program PRD_SCM_GUID_CONVERSION available in S/4HANA system will
update these values in MARA table from the table NDBSMATG16.

4.1 System landscape definition for S/4HANA connection

To connect SRM system with S/4HANA, implement all the notes specified in SAP Note 2229738 . The notes
must be implemented in the same order as specified.

First implement the interface notes as mentioned in sequence, and then implement the implementation notes
as per sequence. After all the notes are successfully implemented, set the system landscape assignment as
described below.

1. Go to SPRO.
2. Navigate to SRM Server Technical Basic Settings ALE Settings Define System Landscape .
3. Define the system type for ERP_8.0H as an entry.

With this assignment, SAP SRM system will call the driver routines relevant for S/4HANA system.

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

10 INTERNAL Material Replication in SAP SRM
4.2 Assigning basic IDOC type

Material document creation from the SAP SRM to S/4HANA system must use the new message type
MBGMCR02. This type must be mapped with the S/4HANA logical system. Follow the below steps to do the
mapping:

1. Go to transaction WE20.
2. Expand Partner Type LS from the Partner Profiles.
3. Select the logical system of S/4HANA system.
4. Select the Message Type MBGMCR and open the entry.
5. In IDoc Type section, specify the value of Basic type as MBGMCR02.

With the material document, IDOC process will take the the basic type MBGMCR02 which has the field
MATERIAL_LONG.

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

Material Replication in SAP SRM INTERNAL 11
5 SRM Component Planner Integration with
SAP S/4HANA system

Component planners process the maintenance and service orders in SAP SRM and in the SAP S/4HANA or
ERP back-end systems. They are responsible for planning materials that are required for executing orders or
projects. If your ECC system is transformed to S/4HANA system, to continue using SRM Component Planner
with the S/4HANA system, implement the below notes in the SRM systems:

● 2838679 - Note for Report NOTE_2836354

● 2836354 - SRM Component Planner integration with S/4HANA system

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

12 INTERNAL SRM Component Planner Integration with SAP S/4HANA system
6 SAP S/4HANA system with DIMP LAMA

SAP ECC system with an activated DIMP Manufacturer Part Number solution allows you to manage Long
Material Codes (up to 40 characters) by using the MATERIALID table. This table contains the relationship
between Material Code (internal material) and Long Material Code (external material) in SAP ECC.

During the conversion of SAP ECC with a DIMP LAMA solution, to SAP S/4HANA where the Long Material
Number is stored into all SAP S/4HANA application tables (MARA, MARC, NDBSMATG16, and so on), the internal
material number in table MARA is replaced by the external material number.

If the SAP S/4HANA system was upgraded from a DIMP LAMA system, a special handling is required in SAP
SRM for the existing DIMP LAMA material numbers, using the short material number maintained in table
MATERIALID in SAP S/4HANA.

● Inbound scenarios
In the SRM system the short material number (internal material maintained in the table MATERIALID in
SAP S/4HANA) must be used for the product ID.
● Outbound scenarios
In addition to the long material number (external material in the table MARA in SAP S/4HANA), the short
material number must be transferred to the S/4 HANA system.

In addition to the SAP Notes specified in previous sections, the below SAP Notes are also required for using
SAP S/4HANA system with DIMP LAMA.

● 2858467 - Material description was not replicated to SRM system from S/4 HANA System
● 2849897 - S/4 Conversion - Material Replication from S/4 HANA to SRM system not possible
● 2849142 - Issues With Long Material Number after Move To S/4 HANA: Prerequisite Note
● 2849618 - Issues With Long Material Number after Move To S/4 HANA: Read of S/4 HANA Backend
Data
● 2849648 - Issues With Long Material Number after Move To S/4 HANA: Transfer to S/4 HANA Backend

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

SAP S/4HANA system with DIMP LAMA INTERNAL 13
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Configuration Guide for SAP SRM Connectivity with SAP S/4HANA

14 INTERNAL Important Disclaimers and Legal Information
Configuration Guide for SAP SRM Connectivity with SAP S/4HANA
Important Disclaimers and Legal Information INTERNAL 15
www.sap.com/contactsap

© 2020 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 https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN