PUBLIC

How-To Guide
SAP Digital Supply Chain Management, Edition for SAP S/4HANA
Document Version: 3.0 - 2023-03-16

Integration of SAP ERP or SAP S/4HANA

with SAP Digital Supply Chain Management,
Edition for SAP S/4HANA in a Single Client
Document History
Document Version Description
Version 1.0 First published version for SAP Digital Supply Chain Management, edition for SAP
S/4HANA in a single client
Version 2.0 SAP Portfolio and Project Management added to the SAP Digital Supply Chain
Management, edition for SAP S/4HANA in a single client
Version 3.0 Hub Scenario enabled for the applications in the SAP Digital Supply Chain
Management, edition for SAP S/4HANA in a single client

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Document History © 2023 SAP AG or an SAP affiliate company. All rights reserved. 2
Table of Contents
1 Purpose of This Guide......................................................................................................................... 5

2 Background Information .................................................................................................................... 7

2.1 Terminology .................................................................................................................................... 7
2.2 Prerequisites ................................................................................................................................... 7
2.3 Limitations ....................................................................................................................................... 7
2.4 Overview of System Landscape Entities....................................................................................... 8
2.5 Overview on Integration Technologies by Domain ...................................................................... 9

3 Cross-Solution Customizing Settings .............................................................................................. 10

3.1 Activate Business Functions ........................................................................................................ 10
3.2 Check Basic Table Entries............................................................................................................ 10
3.3 Create Factory Calendars in the DSC System ............................................................................ 11
3.4 Define Material Number Length ................................................................................................... 11
3.5 Define Material Types .................................................................................................................... 11
3.6 Define Plants and Storage Locations in the DSC System ......................................................... 12
3.7 Create MRP Areas for Plants or Storage Locations (for MP&S and eSPP) ............................. 13
3.8 Create MRP Areas for Subcontracting ....................................................................................... 13
3.9 Create Production Supply Areas ................................................................................................. 13
3.10 Create Model and Planning Version in the DSC System ........................................................... 13
3.11 Maintain Business System Group ............................................................................................... 14
3.12 Configure Customer or Vendor Integration and Make Business Partner Settings in the
ERP and DSC System ................................................................................................................... 14

4 Configure System Connection and Global Settings .......................................................................... 15

4.1 Activate Change Pointers............................................................................................................. 15
4.1.1 Activate Change Pointers at the Client Level in the ERP System .............................. 15
4.1.2 Activate Change Pointers per Message Type in the ERP System ............................. 15
4.2 Configure Logical Systems in the ERP System .......................................................................... 16
4.3 Configure Logical Systems in the DSC System ......................................................................... 16
4.4 Create an RFC User (ERP and DSC System) ..............................................................................17
4.5 Create RFC Connections from the ERP to the DSC System and Vice-Versa .......................... 18
4.6 Assign DSC Logical Systems to RFC Destinations in the ERP System .................................... 19

5 Setup of Application Link Enabling (ALE)......................................................................................... 20

5.1 Create a Port for RFC Connections .............................................................................................20
5.2 Define a Data Distribution Model and Distributing Views .........................................................20
5.3 Define Partner Profiles ................................................................................................................. 22
5.3.1 Generate a Partner Profile in the ERP System ............................................................ 22
5.3.2 Replicate a Distribution Model (ERP to DSC System) ................................................ 23
5.3.3 Generate a Partner Profile in DSC for the Distribution Model (ERP to DSC
System) ........................................................................................................................... 23
5.4 ALE Integration from the DSC to the ERP System .................................................................... 24
5.5 IDoc Serialization .......................................................................................................................... 24

6 Setup of Data Replication Framework (DRF) ................................................................................... 25

6.1 Set up Point-to-Point Communication for Web Services.......................................................... 25
6.2 Define Technical Settings for Data Replication (ERP to DSC System) .................................... 25
6.3 Define Replication Models............................................................................................................ 27
6.4 Define DRF Filter Criteria ............................................................................................................. 28
6.4.1 Define Filter Criteria for the Selection of Business Partners...................................... 28
6.5 Configure Inbound Processing of Equipment ............................................................................30
6.6 Define Technical Settings for Data Replication (DSC to ERP System) .................................... 31
6.7 Create a BAdI Implementation to Clear Data When Replicating Materials (ERP System) .... 31

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Table of Contents © 2023 SAP AG or an SAP affiliate company. All rights reserved. 3
 6.8 Create a BAdI Implementation to Differentiate Materials Relevant for SAP Advanced
Planning and Optimization and Extended Service Parts Planning (eSPP) .............................. 36
6.9 Create a BAdI Implementation to Update Planning Flags When Replicating Materials
(DSC System) ............................................................................................................................... 36

7 Configure Required Settings ............................................................................................................ 37

8 Data Transfer .................................................................................................................................... 38

8.1 Transfer of Business Partners Using Data Replication Framework (DRF) .............................. 38
8.1.1 Activate the Function Module for Master Data Governance Change Handling ........ 38
8.1.2 Execute the Initial Business Partner Data Transfer with DRF .................................... 38
8.1.3 Execute the Delta Business Partner Data Transfer with DRF .................................... 39
8.1.4 Monitor Business Partner Transfer with DRF .............................................................. 39
8.1.5 Transfer Shipping Points ............................................................................................... 39
8.1.6 Transfer Locations .........................................................................................................40
8.2 Execute the Initial Transfer of Characteristics via ALE and IDoc .............................................40
8.3 Execute the Initial Transfer of Classes ........................................................................................40
8.4 Execute the Initial Transfer of Material Masters ........................................................................40
8.5 Execute the Initial Transfer of Batches ....................................................................................... 41
8.6 Execute the Delta Transfer of Master Data ................................................................................ 41

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Table of Contents © 2023 SAP AG or an SAP affiliate company. All rights reserved. 4
1 Purpose of This Guide
In today’s uncertain economic climate, companies cannot wait years or even months to realize the benefits of
supply chain digitalization. They require modular, interoperable solutions that can be implemented quickly to
deliver responsiveness and resilience. This modular interoperability is a main tenet of the SAP Digital Supply
Chain Management, edition for SAP S/4HANA® that helps you to accelerate innovation and time to value. As a
composable package of solutions for supply chain professionals, the edition can be deployed independently from
other solution implementations and ERP transformations on SAP S/4HANA. This means it can be a stepping
stone to broader enterprise transformation with SAP S/4HANA, while helping you to focus immediately on urgent
supply chain needs. The edition of SAP Digital Supply Chain Management for SAP S/4HANA includes several
modular solutions that – jointly with an underlying ERP system – tightly integrate and work with other SAP
products to support scenarios that span the Plan to Fulfill cycle.
Plan to Fulfill, a subprocess within Design to Operate, describes the journey of information through the stages of
supply and demand planning, manufacturing, and logistics. When engineering designs a new product or redesigns
an existing one, supply chain planners need to consider the impact on demand, supply, and production. They
must also collaborate with their suppliers to purchase newly defined components or materials. Manufacturing
receives information about the new or modified product from engineering and makes the appropriate
adjustments to the required production steps. The finished product is warehoused and then transported as
customer orders are received.
The following modular solutions support the Plan to Fulfill cycle and can be part of SAP Digital Supply Chain
Management, edition for SAP S/4HANA®, depending on your system and business process needs:
• SAP Extended Warehouse Management (SAP EWM) application
• SAP Transportation Management (SAP TM) application
• SAP Yard Logistics application
• SAP S/4HANA Manufacturing solution for planning and scheduling (MP&S)
• SAP S/4HANA Manufacturing solution for production engineering and operations (PEO)
• SAP S/4HANA Supply Chain solution for extended service parts planning (eSPP)
• SAP Portfolio and Project Management (SAP PPM) application

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Purpose of This Guide © 2023 SAP AG or an SAP affiliate company. All rights reserved. 5
Each of these modular solutions can run in the same system in its own client – or alternatively in the same client -
as a side car to the existing ERP system (either SAP ECC or SAP S/4HANA). When combining some or all of those
individual solutions into the SAP Digital Supply Chain Management, edition for SAP S/4HANA in a single, joint
client, some settings deviate from the individual guides whereas other settings remain unchanged.
This guide covers the topics where some of the settings deviate from the settings in the individual guides and
describes the overarching implementation steps required. Each modular solution has its individual
implementation guide with solution-specific setup details. You should use this guide in combination with the
individual guides that cover additional solution-specific setup tasks.
These are the detailed guides for the integration technologies:
• TM Integration Guide for DSC Edition
• Integration of SAP ERP or SAP S/4HANA with Decentralized EWM based on SAP S/4HANA
• How To Integrate Extended Warehouse Management (EWM) and Transportation Management (TM) in
One Client for SAP Digital Supply Chain Management, edition for SAP S/4HANA
• SAP S/4HANA Manufacturing for Planning & Scheduling - Implementation Guide
• PEO Implementation Guide for SAP Digital Supply Chain Management, Edition for SAP S/4HANA
• Extended Service Parts Planning within SAP S/4HANA - Implementation Guide
• Administration Guide for SAP Yard Logistics for SAP S/4HANA
• Master Data Governance: Set Up Data Replication
• Data Replication Framework
• SAP S/4HANA Cookbook Customer/Vendor Integration
• Configuration Guide for SAP Portfolio and Project Management in S/4HANA

You find the latest version of all of these guides on the SAP Digital Supply Chain Management, edition for SAP
S/4HANA product page on the SAP Help Portal.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Purpose of This Guide © 2023 SAP AG or an SAP affiliate company. All rights reserved. 6
2 Background Information
2.1 Terminology
In this guide, we refer to:
• SAP Digital Supply Chain Management, edition for SAP S/4HANA as DSC edition
• the system that the DSC edition and the selected modules are running on as DSC system
• the system that your ERP is running (SAP ECC or SAP S/4HANA) on as ERP system
• the modules within the DSC edition as DSC solutions
In this section, you get an overview of prerequisites and limitations as well as the system landscape entities used
in the integration of SAP ERP with the DSC edition.

2.2 Prerequisites
The following minimum system requirements allow you to combine all the DSC solutions, or a selection of the
solutions in a single client:
System Release
SAP Digital Supply Chain Management, edition for SAP S/4HANA 2021 FPS2 or higher
SAP S/4HANA
SAP Yard Logistics add-on SAP Yard Logistics 2021 for SAP S/4HANA
ERP system: ERP 6.0 EHP 7 SP23 or higher or EHP 8 SP17 or
SAP ECC higher
or SAP S/4HANA SAP S/4HANA 2021 FPS0 or higher

If you are implementing fewer than the 6 possible DSC solutions in a single client, it may be possible to implement
on lower releases. However, this should be considered carefully and analyzed with your SAP experts.
Individual standalone applications that you want to run in separate clients in the DSC edition may have lower
minimum system requirements. Please refer to the individual application-specific documentation to determine
the minimum system requirements.
Please check the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP S/4HANA
product page on the SAP Help Portal for system releases, support packages, and additional prerequisites.
Customer vendor integration (CVI) is a prerequisite within your ERP system when connecting to your DSC
system. Since SAP S/4HANA contains the business partner concept and CVI by default, this prerequisite is
especially important when you use ECC as an ERP system. Your customer and vendor master data and
corresponding settings need to be checked to define a business partner concept. This concept should be
established in a pre-project before starting the implementation of the DSC edition. Since customer or vendor
master data is used differently across SAP customers, this guide cannot give a detailed implementation
recommendation. Therefore, section 3.13 Configure Customer or Vendor Integration and Make Business Partner
Settings in the ERP and DSC System only provides a short overview on this topic.
For some master data objects (for example. work centers) you use different integration technologies (for
example, core interface (CIF) vs. data replication framework) based on the usage within DSC edition. Therefore,
you establish a concept on which data to integrate in which way depending on the usage and determine the
corresponding filter criteria to set up integration accordingly in the respective chapters.

2.3 Limitations
The usage of SAP Digital Supply Chain Management, edition for SAP S/4HANA with retail specific master data
(for example, material masters) is not supported.
Advanced Shipping and Receiving is not supported for use in SAP Digital Supply Chain Management, edition for
SAP S/4HANA.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Background Information © 2023 SAP AG or an SAP affiliate company. All rights reserved. 7
2.4 Overview of System Landscape Entities
The following table provides an overview of system landscape entities required for the integration:
Entity Setting Customizing Comments
Level Transport
RFC destination Cross-client No Technical setting for RFC and qRFC communication
Example: Naming convention: <SID>CLNT<CLIENT>
ERPCLNT001 See section 1.1 Create RFC Connections from ERP to DSC
DSCCLNT001 and Vice-versa.
Logical system Cross-client Yes Technical setting for RFC and qRFC communication
Example: Naming convention: <SID>CLNT<CLIENT>
ERPCLNT001 Can be created in the System Landscape Directory
DSCCLNT001
The logical system is assigned to the RFC destination
Own logical system assigned to client
See section 4.2 Configure Logical Systems in SAP ERP.
Business system Client No Used in the DSC system for master data
group 1:N relationship to logical system
Example: See section 3.11 Maintain Business System Group.
BSG1

Business system Client No Used in the DSC system for transactional data
Example: Naming convention: <SID>_<CLIENT>
ERP_001 The business system is assigned to a logical system
DSC_001
Can be created in the System Landscape Directory
Own business system assigned to client
See section 1 Setup of Data Replication Framework (DRF).

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Background Information © 2023 SAP AG or an SAP affiliate company. All rights reserved. 8
2.5 Overview on Integration Technologies by Domain
In contrast to standalone implementations of DSC solutions, we follow a consolidated approach for data
integration in context of SAP Digital Supply Chain Management, edition for SAP S/4HANA, which deviates for
certain objects.
Object / Domain Integration Technology
Business partner Data replication framework (DRF) via service
(CVI is required in the ERP system as a prerequisite)
Locations (for example, plants, shipping Points) DRF via service (for more information, see the TM
Integration Guide for DSC Edition)
Note: /SAPAPO/CREATE_LOCATION is not required
for location types 1001 and 1003 in this case
Classes and characteristics Application Link Enabling (ALE) via IDoc
Material masters DRF via IDoc
CIF for Manufacturing solution for planning and
scheduling (MP&S) and Extended Service Parts
Planning (eSPP) (for more information, see the
solution-specific guides on the SAP Digital Supply
Chain Management, edition for SAP S/4HANA SAP
Help Portal)
Batches ALE via BAPI
Serial numbers (piece of equipment) ALE via BAPI
Work centers CIF via RFC calls (see SAP S/4HANA Manufacturing
for Planning & Scheduling - Implementation Guide)
DRF via IDoc for non-MP&S work centers
BOM, routing, production versions See the PEO Implementation Guide for SAP Digital
Supply Chain Management, Edition for SAP
S/4HANA
Production data structure (PDS) can be generated
from ERP via CURTO_CREATE or directly within the
DSC edition via CURTOADV_CREATE in case
versioned master data is required for planning
Others (for example, transactional data) See the solution-specific guides on the SAP Digital
Supply Chain Management, edition for SAP
S/4HANA product page on the SAP Help Portal

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Background Information © 2023 SAP AG or an SAP affiliate company. All rights reserved. 9
3 Cross-Solution Customizing Settings
3.1 Activate Business Functions
You activate business functions that enable your ERP system to communicate with your DSC system in the
Switch Framework.
Each DSC solution requires the activation of specific business functions which even may depend on system
releases in some cases. For more information, see the solution-specific guides on the SAP Digital Supply Chain
Management, edition for SAP S/4HANA product page on the SAP Help Portal and activate required business
functions according to your needs.
This guide only covers the business function relevant for integration.
As of EHP8, you activate following business function to enable immediate data integration:
Business Function Description
DRF_FOUNDATION Data Replication

For more information, see the business function documentation in transaction SFW5.
Business function DRF_FOUNDATION is shipped in SAP ERP 6.0 with enhancement package 8 and is not available
in earlier enhancement packages. It enables material master changes to be replicated when the material is saved.
If the business function has not been activated or is not available. The system only writes a change pointer when a
material is saved. You can replicate all materials that have a change pointer by using transaction DRFOUT or report
RDRF_MESSAGE_OUT (replication mode Changes). It is recommended to schedule a job to run the report
RDRF_MESSAGE_OUT periodically to replicate all material changes since the previous replication.

3.2 Check Basic Table Entries

Context
Basic tables such as units of measures, currencies, countries, and languages are used both in the ERP and the
DSC system. You check that the required entries (especially the ISO codes) are identical in all systems that are
part of your system landscape.

Procedure
Carry out the following steps in your DSC system Customizing client:
On the SAP Easy Access screen, choose Tools > Administration > Administration > Client Administration >
Customizing Objects > Object Comparison.
Compare the information in the following table between the DSC system client and the ERP system
customizing client. Compare the entries you plan to use in your DSC system processes.
Adjust the tables in the ERP system or DSC system Customizing, if necessary as follows:
View/Table Description Usage in DSC Edition
T002 Language keys Material master and others
T005 Countries Material master and others
T006 Unit of measure Material master and others
TCURC Currency codes Material valuation data

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Cross-Solution Customizing Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 10
3.3 Create Factory Calendars in the DSC System
You create factory calendars in the Customizing of the DSC system.

Procedure
In Customizing, choose Advanced Planning > Master Data > Calendar > Maintain Factory Calendar.
On the next screen, select Factory Calendar and choose Change.
On the next screen, choose Create.
Define the factory calendar as needed.

Important
Factory calendars are not client-specific. Each change takes effect directly in all clients.

3.4 Define Material Number Length

The ERP and DSC system use the same material number length and formatting options.

Procedure
Carry out the following steps in the DSC system:
Launch Change View Material Number Format (transaction OMSL).
Adopt the ERP system settings.

Note
If you connect the DSC system to an SAP ERP system supporting 40 characters, you also have to
activate the field length extension for the communication to this system in Customizing for Cross-
Application Components under General Application Functions  Field Length Extension  Activate
Extended Fields (transaction FLETS).
If your ERP system is an SAP S/4HANA system, PEO supports a 40-character SAP S/4HANA
material ID.
If your ERP system is an SAP ERP 6.0 system with corresponding enhancement package, PEO only
supports the 18-character SAP ECC material ID, regardless of whether you've activated the 40-
character long material ID for discrete industries (DIMP LAMA) in the ERP system. No option is
currently available to map the 40-character SAP S/4HANA material ID to the DIMP-LAMA material
ID.

3.5 Define Material Types

You define material types in the ERP and DSC system while preventing accounting requirements in the DSC
system.

Procedure
Determine the material types you for your processes.
Create the required material types both in ERP and DSC systems in Customizing, under Logistics General >
Material Master > Basic Settings > Material Types > Define Attributes of Material Types. For more
information, see How to Create Material Types for Major Assembly Production on the SAP Help Portal.
Accounting and sales is done in the ERP system. For example, the DSC system only supports production
engineering and operations, warehouse tasks, etc. Accounting or sales related material attributes are not
needed in the DSC system. Make sure the material types in the DSC system do not require accounting data
and do not update inventory values (for more information, see Deselect quantity/value updating for
material types in your valuation area via IMG path Logistics > General  Product Lifecycle Management

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Cross-Solution Customizing Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 11
 (PLM)  Material Master  Basic Settings  Define Attributes of Material Types )
For further details refer to section 6.7 Create a BAdI Implementation to Clear Data When Replicating
Materials (ERP System).
Maintain additional settings as described by the individual guides (for example, PEO Implementation Guide
SAP Digital Supply Chain Management, Edition for SAP S/4HANA 3.6.2 “Non-valuated Materials” on the
SAP Help Portal).

3.6 Define Plants and Storage Locations in the DSC System

You create required plants and storage locations within the DSC system.

Context
A plant and an assignment to a company code must exist to receive material master with plant-specific data
(database table MARC) in the DSC system. The company code itself is not required in the DSC system for further
processing, therefore it is sufficient to create it with minimal or “dummy” data.

Procedure
Carry out the following steps in your DSC Customizing client:
Create required plants as a copy of for example plant 0001 (transaction EC02) in Customizing under
Enterprise structure  Definition  Logistics > General  Define, copy, delete, check plant.
Maintain storage locations in Customizing under Enterprise structure  Definition  Materials Management
 Maintain Storage Location.
Check if plants were assigned to company code (otherwise then maintain) in Customizing under Enterprise
structure  Assignment  Logistics > General  Assign Plant to Company Code.
Assign a company code to a fiscal year variant via IMG path Financial Accounting (New)  Financial
Accounting Global Settings (New)  Ledgers  Fiscal Year and Posting Periods  Assign Company Code to a
Fiscal Year Variant. Here you assign the new company code to a fiscal year variant for example, K4.
If the fiscal year variant does not exist yet, create it via IMG path Financial Accounting (New)  Financial
Accounting Global Settings (New)  Ledgers  Fiscal Year and Posting Periods  Maintain Fiscal Year
Variant.
Assign a company code to chart of accounts via IMG path Financial Accounting (New)  General Ledger
Accounting (New)  Master Data  G/L Accounts  Preparations  Assign Company Code to Chart of
Accounts. Here you assign the new company code to a chart of accounts for example, INT.
If the chart of accounts does not exist yet, create it via IMG path Financial Accounting (New)  General
Ledger Accounting (New)  Master Data  G/L Accounts  Preparations  Edit Chart of Accounts List.
Maintain company codes for Materials Management via IMG path: Logistics > General  Product Lifecycle
Management (PLM)  Material Master  Basic Settings  Maintain Company Codes for Materials
Management. Here you set up the new company code for material management, for example, fiscal year
and posting period.
Deselect quantity/value updating for material types in your valuation area via IMG path Logistics > General
 Product Lifecycle Management (PLM)  Material Master  Basic Settings  Define Attributes of Material
Types. Here you deselect the check boxes for quantity updating and value updating for used material types
in material master. The valuation area is created automatically in step 2 'Assign plant to company code'. It
has the same number as the plant.
Check if the sales organization was assigned to plants by copying (otherwise then maintain) in Customizing
under Enterprise structure  Assignment  Sales and Distribution  Assign Sales Organization > Distribution
Channel > Plant.
Check if the standard purchasing organization was assigned to plants (otherwise maintain) in Customizing
under Enterprise structure  Assignment  Materials Management  Assign Purchasing Organization to
Plant.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Cross-Solution Customizing Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 12
3.7 Create MRP Areas for Plants or Storage Locations (for
MP&S and eSPP)
MRP areas for storage locations have to be created in both systems with the same settings.

Procedure
In Customizing, choose Production > Material Requirements Planning > Master Data > MRP Areas > Define
MRP Areas for Plant/Storage Locations.
Create a new entry by specifying name, description, and plant.

3.8 Create MRP Areas for Subcontracting

MRP areas for subcontracting have to be created in both systems with the same settings.

Prerequisites
Business partners have been transferred and vendor numbers are available in the DSC system.

Procedure
In Customizing, choose Production > Material Requirements Planning > Master Data > MRP Areas > Define
MRP Areas for Subcontractors.
Create a new entry by specifying name, description, and vendor.

3.9 Create Production Supply Areas

Context
Production supply areas (PSA) serve as a place for interim storage on the shop floor and are used to make
material directly available for production purposes. PSAs are maintained in work centers for storage location
determination. Therefore, those are needed in DSC system as well, for example when transferring PDS from PEO
to MP&S.

Procedure
Carry out the following steps in the DSC system:
1. Launch Edit Table Views (transaction PK05).
2. Enter your plant.
3. Create relevant PSAs corresponding to your ERP system settings.

3.10 Create Model and Planning Version in the DSC System

Context
Before any master data can be transferred, model 000 and planning version 000 must be created manually in the
DSC system as transferred data is automatically assigned to this model and planning version.

Procedure
On the SAP Easy Access screen, choose Logistics > Advanced Planning > Master Data > Planning Version
Management > Model and Version Management or use transaction /SAPAPO/MVM.
Choose Create Model/Planning Version.
Create model 000 and select it.
Create planning version 000 for this model with the following values:

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Cross-Solution Customizing Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 13
 Field Value
Change Planning Active Selected

Standard Planning Horizon 999

(Days)
Copy In Foreground

Determine Priority According to your business needs

Take Safety Stock into Account According to your business needs

No Order Without Source of According to your business needs

Supply

Note
The model is also relevant for SAP TM and its creation is described in the respective guides.
However, when using MP&S and TM within the DSC system, creation needs to follow the MP&S
approach.

3.11 Maintain Business System Group

1. Launch Maintain Business System Group (transaction /SAPAPO/C1).
2. Define a business system group by specifying an ID and a description. For example, BSG1 – Business System
Group 1.

3.12 Configure Customer or Vendor Integration and Make

Business Partner Settings in the ERP and DSC System
For some solutions, the business partner transfer from the ERP system via DRF services is required. Therefore,
activities according to BP_Conversion_Guide.pdf attached to SAP Note 2265093 are mandatory in your ERP
system. For business partner, inbound corresponding settings are also required on the DSC system.
The business partner concept raises important conceptual topics such as groupings, number ranges, which
should be outlined in a pre-project.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Cross-Solution Customizing Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 14
4 Configure System Connection and Global
Settings
You configure the system landscape settings required for the queued remote function call (qRFC) communication
between the DSC and ERP system.
The DSC system communicates with the ERP system via queued remote function call (qRFC) for parallel
processing, using system resources in parallel to increase business throughput and reduce processing time.

4.1 Activate Change Pointers

4.1.1 Activate Change Pointers at the Client Level in the ERP

System
You activate change pointers at the client level.

Procedure
Activate change pointers at client level in Customizing for SAP NetWeaver under Application Server  IDoc
Interface/Application Link Enabling (ALE)  Modelling and Implementing Business Processes  Master Data
Distribution > Replication of Modified Data  Activate Change Pointers > Generally.
Launch Activate Change Pointers Generally (transaction BD61) in the system from which materials are to
be replicated.
Select the checkbox to activate change pointers in general.
Save your settings.

4.1.2 Activate Change Pointers per Message Type in the ERP

System
You activate change pointers for all message types assigned to your distribution model.

Context
The change pointers are needed to log changes to the master data and distribute them to the receiver system.
To ensure that changed master data can be identified, activate change pointers in the system from which the
master data is to be replicated.

Procedure
Launch Activate Change Pointer Generally (transaction BD50) and activate change pointers for the
following message types:
• MATMAS
• BATMAS
• CHRMAS
• CLSMAS
• CLFMAS
Save your settings.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Configure System Connection and Global Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 15
 Important
The activation of change pointers per message type creates entries for the fields of the message
type in another table. For batches (message type BATMAS) it might happen that an entry for the
batch status is missing as this depends on the setup of the system whether batch status
management is activated or not. To verify this, start transaction BD52 for message type BATMAS
and check that an entry exists for object CHARGE, table name MCHA, field name ZUSTD.

4.2 Configure Logical Systems in the ERP System

Configure logical systems in your ERP system to enable Application Link Enabling (ALE) communication between
your ERP and DSC system.

Procedure
Define a logical system for your ERP system and assign it to a client.
Define a logical system for your DSC system and client.

Note
Logical systems must adhere to the naming convention <SSS>CLNT<CCC>, where SSS is the 3-
character system ID and CCC is the client.
Log on to your ERP system.
Launch Display ALE Customizing (transaction SALE).
Define a logical system for your ERP system and client by choosing Basic Settings > Logical Systems >
Define Logical System.
Save your entries and exit the activity.
Assign the ERP logical system to a client by choosing Basic Settings > Logical Systems > Assign Logical
System to Client.
Select the client in which you're running ERP and assign the logical system that identifies the ERP system
and client.
Save your settings and exit the activity.
Define a logical system for your DSC system and client by choosing Basic Settings > Logical Systems >
Define Logical System.
Save your entries and exit the activity.

4.3 Configure Logical Systems in the DSC System

Configure logical systems in your DSC system to enable ALE communication between your DSC and ERP system.

Procedure
Define a logical system for your DSC system and assign it to a client.
Define a logical system for your ERP system and client.

Note
Logical systems must adhere to the naming convention <SSS>CLNT<CCC>, where SSS is the 3-
character system ID and CCC is the client.
Log on to your DSC system.
Launch Display ALE Customizing (transaction SALE).
Define a logical system for your DSC system and client by choosing Basic Settings > Logical Systems >
Define Logical System.
Save your entries and exit the activity.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Configure System Connection and Global Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 16
 Assign the DSC logical system to a client by choosing Basic Settings > Logical Systems > Assign Logical
System to Client.
Select the client in which you're running the DSC system and assign the logical system that identifies the
DSC system and client.
Save your settings and exit the activity.
Define a logical system for your ERP system and client by choosing Basic Settings > Logical Systems >
Define Logical System.
Save your entries and exit the activity.

4.4 Create an RFC User (ERP and DSC System)

Create an RFC user with the required authorizations in your DSC and ERP systems to enable message-based data
replication between the systems.

Procedure
Launch User Maintenance (transaction SU01) in your ERP system and identify the user.(Naming
conventions suggest calling the RFC user ALEREMOTE).
On the Logon Data tab, select user type Service and provide a password.
Launch Role Maintenance (transaction PFCG) to create a role with the necessary authorizations for this
user.
For example, in the ERP system, the RFC user must have authorizations for the following authorization
objects for PEO:
• S_RFC
• B_ALE_MODL
• C_PDC
• M_MSEG_BWA
• M_MSEG_WWA
• C_AFRU_AWK
Check the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP S/4HANA
product page on the SAP Help Portal to have a complete list of required authorizations.
Launch User Maintenance (transaction SU01) in your DSC system and identify the user (Naming
conventions suggest calling the RFC user ALEREMOTE).
On the Logon Data tab, select user type Service and provide a password.
Use Role Maintenance (transaction PFCG) to create a role with the necessary authorizations for this user.
In the DSC system, the RFC user must have authorizations that include the following authorization objects:
• S_RFC
• B_ALE_MODL
Check the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP S/4HANA
product page on the SAP Help Portal to have a complete list of required authorizations

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Configure System Connection and Global Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 17
4.5 Create RFC Connections from the ERP to the DSC System
and Vice-Versa
Prerequisites
System administrators must make specific settings for the remote function all (RFC) connection between the ERP
and DSC system before any Customizing activity is carried out.
Contact your system administrator to ensure the following prerequisites are met:
• An RFC user exists in each target system/client defined as RFC destination. For example, for the DSC
system client to use the RFC destination to the ERP test client, an RFC user exists in the ERP client.
• RFC destinations exist between the corresponding ERP system and DSC system clients.

Procedure
...

Launch Configuration of RFC Connections (transaction SM59).

Create the RFC connection to the DSC system if it doesn't exist yet.
Select ABAP Connection and choose Create to create the RFC connection.
Enter the following data and then choose Enter.
• Destination: Specify the logical system of the DSC system as the destination.
• Connection: Type 3
On the Technical Settings tab, make the following settings:
• For load balancing, select Yes.
• Enter the target system, message server, and group.
• If necessary, copy this information from the system entry properties in SAP Logon.
On the Log on & Security tab, define the following settings:
• Enter the language and client of the target system.
• Specify the logon data for the RFC user that you created.
• Set Trust Relationship to No.
On the Unicode tab, make sure the connection type is Unicode.
Save your RFC connection.
Verify your settings by choosing Remote Logon and Connection Test.

Repeat steps 1 to 8 in the DSC system to create the connection to the ERP system.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Configure System Connection and Global Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 18
4.6 Assign DSC Logical Systems to RFC Destinations in the
ERP System
You assign the logical systems defined in the ERP system to RFC destinations in SAP ERP.

Context
These settings cannot be transported from your ERP Customizing client to other SAP ERP systems and clients.
Therefore, you must repeat the steps in every ERP system client connected to the DSC system.

Procedure
Carry out the following steps in each ERP system client you want to connect to the DSC system:
In Customizing for SAP NetWeaver, choose Application Server > IDoc Interface/Application Link Enabling
(ALE) > Communication > Determine RFC Destinations for Method Calls.
Select the DSC logical system, for example, DSCCLNT001.
Choose Standard BAPI destination.
Enter the RFC destination created by your system administrator for the corresponding DSC system and
choose Enter.
Repeat the steps in the DSC system to assign ERP logical systems to RFC connections.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Configure System Connection and Global Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 19
5 Setup of Application Link Enabling (ALE)
Note
The following description contains only an example for the ALE IDoc setup. ALE offers much more
settings and possibilities. Therefore, you should get familiar with ALE in general. For more
information, see IDoc Interface/ALE on the SAP Help Portal.

5.1 Create a Port for RFC Connections

Create a port from your DSC and ERP system to the corresponding RFC destination to define the channel
through which data is to be exchanged.

Procedure
Launch Ports in IDoc Processing (transaction WE21).
Create a transactional RFC port:
• As the port name, specify the technical name of the RFC destination.
• Enter a description of the port.
As the version, select IDoc record types SAP Release 4.x.
As the RFC destination, enter the RFC destination of your ERP or DSC system respectively.
Save your entries.

5.2 Define a Data Distribution Model and Distributing Views

You define the messages in the distribution model in the sender system.

Procedure
Carry out the following steps in the ERP system:
...

Launch Maintenance of Distribution Model (transaction BD64).

Choose Distribution Model  Switch Processing Mode.
Choose Create Model View to create a new model view.
Enter the data as shown in the following table:
Field Value

Short Text For example, DSCCLNT001: DSC Edition

(replace DSCCLNT001 with the logical system name for DSC edition)
Technical Name For example, DSCCLNT001
(replace DSCCLNT001 with the logical system name for DSC edition)
Choose Continue.
Choose Add Message Type and select the new model to add message types.
For each message type, enter the data as shown in the following table:

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Application Link Enabling (ALE) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 20
 Business Object Message Sender Receiver
Type
Materials MATMAS Specify the logical Specify the logical
system of the ERP system of the DSC
Work centers LOIWCS system. system.
Production orders LOIPRO
Dummy message type SYNCH

This is a mandatory message type that is

used to determine RFC destinations.
Select the model view and define the following message flows by choosing Add BAPI:
The object name and method are case-sensitive entries.
Business Object/Interface Method Sender Receiver
Object
Equipment PieceOfEquipment Create Specify the logical system Specify the logical system
of the ERP system. of the DSC system.
Batch Batch SaveReplica Specify the logical system Specify the logical system
of the ERP system. of the DSC system.
If you use batches or characteristic-dependent planning, you also need the following message types:
Business Object Message Sender Receiver
Type
Characteristics CHRMAS Specify the logical system of the Specify the logical system of the
master ERP system. DSC system.
Classes master CLSMAS
Classification CLFMAS
master
To create a filter group for message type CLSMAS (classes), choose No filter set or Data Filter Active under
message type CLSMAS in the tree, then choose Create Filter Group on the dialog box.
Choose filter object type Class Type and enter the class types 022 and 023 for batch classes (depending
on your system settings the value help may not show both values. You still can enter both values).
If Characteristic Dependent Planning (CDP) as part of MP&S is relevant, you need to set your batch level to
material or client specific. As a result, class type 023 will become relevant for batches.
Choose Continue.
To create a filter group for message type CLFMAS (classifications), choose No filter set or Data Filter Active
under message type CLFMAS in the tree.
Choose Create Filter Group on the dialog box.
Choose filter object type Class Type and enter the class types 022 and 023 for batch classes (depending
on your system settings the value help may not show both values. You still can enter both values).
Choose Continue.
Save your distribution model.
For the message types LOIPRO (production orders), MATMAS (materials), and LOIWCS (work centers),
and for the BAPI PieceOfEquipment (equipment), you can use DRF filter objects to further refine the
data that is to be replicated.
DRF filter objects are not yet supported for filtering batches to be replicated.
To create a filter group for BAPI method Batch.SaveReplica (batches), choose Receiver determination
under BAPI Batch.SaveReplica in the tree.
Choose Create Filter Group on the dialog box.
Choose Continue.
Save the distribution model.
Choose Edit > Model view > Distribute to transport the distribution model to other systems.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Application Link Enabling (ALE) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 21
5.3 Define Partner Profiles
You can generate the partner profile within Display Distribution Model (transaction BD64) automatically or create
it using Partner Profile (transaction WE20) manually. You use this to create the partner profile manually.

5.3.1 Generate a Partner Profile in the ERP System

Generate a partner profile to define the parameters for exchanging data with your DSC system based on the
information in the distribution model.

Prerequisites
You configured the basic settings for the system landscape and created a distribution module from the ERP
system to the DSC system.

Procedure
Carry out the following steps in the ERP system:
Launch Display ALE Customizing (transaction SALE).
Choose Modeling and Implementing Business Processes > Partner Profiles > Generate Partner Profiles .
In the Model View field, select the distribution model that you created for distributing data from the ERP
system to the DSC system.
As the partner system, select the logical system of your DSC system.
Enter the ALE user (the default value is ALEREMOTE) along with the following values:
Field Value
Version 3

Pack. Size 100

Make the following settings:

a. Under Output Mode, select the Pass IDoc Immediately radio button.
b. For inbound processing, select the Trigger immediately radio button.
Execute the report.
Verify generation of the partner profile by performing the following substeps:
a. Launch Partner Profiles (transaction WE20).
b. Under Partner Profiles, expand the Partner Type LS folder and select the logical destination system.
c. Verify that the outbound and inbound parameters match the distribution model and you have the
required IDoc versions. You can drill down into an outbound message type to change the IDoc
version.
d. Check the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP
S/4HANA product page on the SAP Help Portal for details on required versions.
e. If you want inbound IDocs to be processed immediately rather than asynchronously by report
RBDAPP01, drill down into the inbound message type and make sure that Trigger Immediately is
selected.
f. If you want outbound IDocs to be processed immediately rather than asynchronously by report
RSEOUT00, drill down into the outbound message type and make sure that Pass IDoc Immediately
is selected.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Application Link Enabling (ALE) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 22
5.3.2 Replicate a Distribution Model (ERP to DSC System)
Replicate your distribution model from your ERP to your DSC system.

Prerequisites
Before distributing the model, ensure that:
• You've generated the partner profile and the SYNCH message type exists as an outbound parameter.
• The technical name of your distribution model is unique within your system landscape.

Procedure
Carry out the following steps in the SAP ERP system:
Launch Display ALE Customizing (transaction SALE).
Choose Modelling and Implementing Business Processes> Maintain Distribution Model and Distribute Views.
Select your distribution model and choose Edit Model > View Distribute.
Select the logical system of the receiving DSC system and choose Continue.

Results
The system displays a list of messages each with a status that indicates whether the action was successful.

5.3.3 Generate a Partner Profile in DSC for the Distribution

Model (ERP to DSC System)
Generate the partner profile for the distribution model that you replicated to your DSC system to define the
parameters for exchanging data based on the information in the distribution model.

Prerequisites
You've successfully replicated the distribution model from the ERP to the DSC system.

Procedure
Carry out the following steps in the DSC system:
Launch Display ALE Customizing (transaction SALE).
Choose Modeling and Implementing Business Processes > Partner Profiles > Generate Partner Profiles.
In the Model View field, select the distribution model that you replicated to your DSC system from your ERP
system.
As the partner system, select the logical system of your ERP system.
Enter the ALE user (the default value is ALEREMOTE) along with the following values:
Field Value
Version 3

Pack. Size 100

Make the following settings:

a. Under Output Mode, select the Pass IDoc Immediately radio button.
b. For inbound processing, select the Trigger immediately radio button.
Execute the report.
Verify generation of the partner profile by performing the following substeps:
a. Launch Partner Profiles (transaction WE20).
b. Under Partner Profiles, expand the Partner Type LS folder and select the logical destination system.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Application Link Enabling (ALE) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 23
 c. Verify that the outbound and inbound parameters match the distribution model and you have the
required IDoc versions. You can drill down into an outbound message type to change the IDoc
version.
d. Check the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP
S/4HANA product page on the SAP Help Portal for details on required versions. To determine the
latest IDoc version in your system, call transaction WE30 and enter the IDoc name with an asterisk
(*) instead of the two-digit version suffix (for example, enter LOIPRO*). Choose F4 to display the
input help, which lists the available IDoc versions. All IDoc versions are downwards compatible, but
it is recommended that you use the latest available IDoc version.
e. Drill down into the inbound message type and ensure that the correct process code is entered
under Inbound options. For example, use process code MATM for materials.

Note
The process code specified in the partner profile determines which function module is used to
process the inbound message. The process codes are configured in transaction WE42. Multiple
inbound function modules exist for some message types. For example, materials and articles (retail
solution) are replicated using the MATMAS IDoc but use different process codes. For details, see
corresponding chapter "Define Inbound Processing (ERP and PEO)” in the PEO Implementation
Guide for SAP Digital Supply Chain Management, Edition for SAP S/4HANA .
f. If you want inbound IDocs to be processed immediately rather than asynchronously by report
RBDAPP01, drill down into the inbound message type and make sure that Trigger Immediately is
selected.
g. If you want outbound IDocs to be processed immediately rather than asynchronously by report
RSEOUT00, drill down into the outbound message type and make sure that Pass IDoc Immediately
is selected.

5.4 ALE Integration from the DSC to the ERP System

For some processes data integration from the DSC system to the ERP system via ALE is required. For the
respective settings, see the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP
S/4HANA product page on the SAP Help Portal (for example, PEO Implementation Guide for SAP Digital Supply
Chain Management, Edition for SAP S/4HANA).

5.5 IDoc Serialization

Consider the settings described in Set Up Data Replication on the SAP Help Portal:
• Use the message type SERDAT to prevent errors during inbound processing such as posting MATQM
before MATMAS.
• With serialized message distribution, IDocs are created, sent, and posted in a specific order.
• Set up sending and receiving systems using transaction SALE in sender and target systems and choose
Modeling and Implementing Business Processes Master Data Distribution Serialization for Sending and
Receiving Data. See the Customizing documentation for the setup process.
SAP Note 752194 provides additional information.
Report RBDMANI2 is scheduled to re-process IDocs with errors in the Inbound processing.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Application Link Enabling (ALE) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 24
6 Setup of Data Replication Framework
(DRF)
6.1 Set up Point-to-Point Communication for Web Services
You set up the point-to-point communication between your ERP system and DSC system using the SAP standard
technology data replication framework (DRF) with web services.

Note
There are two options to establish a connection between two systems to communicate with each
other via web services. The communication messages can be sent and received via and
intermediate XI server or by a direct point-to-point communication between the systems. Here we
describe the usage of a point-to-point communication.
For the configuration guide, see Configuring the SOA Manager for MDG (NW 7.40 or higher).

6.2 Define Technical Settings for Data Replication (ERP to DSC

System)
You configure the technical business system settings for DRF transfer.

Context
You can specify whether the system is to replicate a business object change immediately or create a change
pointer when a business object is changed. In the latter case, you need to replicate the business object
manually using transaction DRFOUT.

Procedure
Carry out the following steps in the SAP ERP system:
Define a business system in Customizing for Data Replication (Transaction DRFIMG) under Data
Replication > Define Custom Settings for Data Replication > Define Technical Settings  Define Technical
Settings for Business Systems  Define Business Systems.
Enter the data as shown in the following table:
Field Value

Business System Enter the name of your DSC business system, for example DSC_001

Logical System Enter the name of the logical system of your DSC business system, for
example DSCCLNT001

RFC Destination Enter the name of the RFC Destination of your DSC business system, for
example DSCCLNT001

Disabled for Inactive

Replication
Save your entries.
Select your defined business system and navigate to Define Bus. Systems, BOs to define the assigned
business objects.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 25
 Enter the data as shown in the following table:
Business Object Type Description

986 Business partner including relationships

97 Production order

145 Batch

194 Material

493 Work center (in case you do not transfer all work centers via CIF)

DRF_0045 Shipping Point/receiving Point (see TM Integration Guide for DSC Edition)

464 Plant (see TM Integration Guide for DSC Edition)

Output mode (Only required if your ERP system is an SAP S/4HANA system or minimum ECC ERP EhP8),
select:
• Direct Output if you want the message (IDoc) to be sent immediately.
• Pooled Output if you want to create messages collectively later by running transaction BD21 or
report RBDMIDOC.
• Object-Dependent Default if you want to use the default setting, which is direct output for all
business objects except materials and pooled output for materials.
Select your defined business object type system and navigate to Define Bus. Systems, BOs, >
Communication Channel to define the communication channel.
For key harmonization select Not Defined.
Save your entries.

Note
The output mode configuration is available only from SAP ERP 6.0 with enhancement package 8 and only
if the business function DRF_FOUNDATION has been activated. If this business function has not been
activated or is not available, or if the output mode is set to Pooled Output, the system only writes a
change pointer when a material or work center is saved. You can use transaction BD21 or report
RBDMIDOC to create IDocs for all change pointers (see 8.6 Execute the Delta Transfer of Master Data.
It is recommended that you schedule the following jobs:
• a job to run report RBDMIDOC and message type MATMAS periodically to create IDocs for all material
changes since the previous IDoc generation.
or
a job to run the report RDRF_MESSAGE_OUT periodically to replicate all material changes since the
previous replication.
• a job to run report RBDMIDOC and message type BATMAS periodically to create IDocs for all batch
changes since the previous IDoc generation. Direct Output is not yet supported for batches.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 26
6.3 Define Replication Models
You configure the replication model for data transfer. The replication model defines what is transferred, how it is
transferred and the receiver system of the data transfer.

Procedure
Carry out the following steps in the SAP ERP system:
Define a replication model in Customizing for data replication (Transaction DRFIMG) under Data
Replication  Define Custom Settings for Data Replication  Define Replication Models.
Choose New Entries.
Create a replication model for every business object you want to replicate.
Enter the data as shown in the following table:
Business Ob- Outbound Communication Channel Outbound Pa- Outbound Pa-
ject of Repli- Implementation rameter and rameter Value
cation Model Value
Business 986_3 1 Replication via PACK_SIZE_B 1
partner Services ULK

Material 194_2 Replication via PACK_SIZE_B 1000

IDoc ULK

Work centers 493_1 Replication via n/a n/a

IDoc

Production 97_1 Replication via n/a n/a

orders IDoc

Equipment 183_1 Replication via n/a n/a

IDoc

Plant 464_L 1 Replication via n/a n/a

Services

Shipping DRF_0045_L 1 Replication via n/a n/a

point/receiving Services
point
For filter time select Filter After Change Analysis.
Select your defined outbound implementation and navigate to Assign Target System for Repl-Model/Outb.
Impl. Enter the data as shown in the following table:
Field Value

Business System Enter the business system that you created for your DSC system

Save your entries.

Navigate back to Define Replication Models to activate the replication model.
Select your defined replication model.
Select Activate.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 27
6.4 Define DRF Filter Criteria
You define filter criteria for a DRF replication model to define which business object instances want to replicate to
your DSC system.

Context
Although you can filter by IDs of individual materials, serial numbers, and production orders, it would require you
to continuously update the filter criteria, for example, every time you create a material or release a production
order. This could lead to data inconsistencies due to missing objects. A logical approach is to filter by common
attributes that every business object instance must have in your DSC system. For example, if you filter by plant,
you replicate all production orders manufactured in this plant or all materials with attributes specific to this plant.
If you're using the DSC edition only for final assembly and you manufacture components in the same plant, you
may need to use additional filter criteria such a material type or MRP controller. SAP recommends that you use
the Data Replication Framework (transaction DRFF) to define filter criteria because it's flexible. An alternative way
to define filter criteria is in the business configuration in Customizing.

Procedure
Launch Define Filter Criteria (transaction DRFF ).
Select a DRF replication model and choose Create.
Specify the filter criteria and then choose Save.

6.4.1 Define Filter Criteria for the Selection of Business

Partners
Procedure
Carry out the following steps in the SAP ERP system:
Define filter criteria for business partner distribution in the SAP Easy Access Menu for Data Cross
Application Components > Processes and Tools for Enterprise Applications  Master Data Governance >
Data Replication > Define Filter Criteria (transaction DRFF).
Select your replication model (for example Business Partner Transfer to DSC001) and choose Change.
Enter Filter Criteria to Include Business Objects, for example for the account group:
Field Value

Filter Criterion Customer or vendor account group

Relation For example, is

Filter Value Customer or vendor account group, for example, DEBI

Save your entries.

Select Show Segment Filters.
Select Company Code Seg. replicated – 98602 from the list of segment filters (select the name to navigate)
Select Edit in the new window.
Enter the following data in Filter Criteria to Exclude Business Objects:

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 28
 Field Value

Filter Criterion Company code

Relation Contains

Filter Value *

Save your entries.

Navigate back to the filter criteria and select Show Segment Filters.
Select Purchasing Org Seg. replicated – 98603 from the list of segment filters (select the name to
navigate).
Select Edit in the new window.
Enter the following data in Filter Criteria to Exclude Business Objects:
Field Value

Filter Criterion Purch. organization

Relation Contains

Filter Value *

Save your entries.

Navigate back to the filter criteria and choose Show Segment Filters.
Select Cust Company Code Seg. replicated – 98604 from the list of segment filters (select the name to
navigate).
Select Edit in the new window.
Enter the following data in Filter Criteria to Exclude Business Objects:
Field Value

Filter Criterion Company code

Relation Contains

Filter Value *

Save your entries.

Navigate back to the filter criteria and select Show Segment Filters.
Select Cust Sales Area Seg. replicated – 98605 from the list of segment filters (select the name to
navigate).
Select Edit in the new window.
Enter the following data in Filter Criteria to Exclude Business Objects:
Field Value

Filter Criterion Distribution channel

Relation Contains

Filter Value *

Field Value

Filter Criterion Division

Relation Contains

Filter Value *

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 29
 Field Value

Filter Criterion Sales organization

Relation Contains

Filter Value *

Save your entries.

Navigate back to the filter criteria and select Show Segment Filters.
Select BP Seg. Filter for TaxCategory – 98700 from the list of segment filters (select the name to navigate).
Select Edit in the new window.
Enter the following data in Filter Criteria to Exclude Business Objects.
Field Value

Filter Criterion Tax number category

Relation Contains

Filter Value *

Save your entries.

Note
In Execute Data Replication (transaction DRFOUT) (SAP Easy Access Menu for Data Cross
Application Components  Processes and Tools for Enterprise Applications  Master Data
Governance > Data Replication  Execute Data Replication) it is possible to maintain manual filter
criteria for the execution of the business partner data transfer. This does not affect the filters
defined for the data replication model in this section. The same logic can be used for defining filters
for execution.

6.5 Configure Inbound Processing of Equipment

Make the necessary settings to configure inbound processing of equipment replicated to your DSC system from
your ERP system.

Context
The distribution model in your ERP system replicates equipment to DSC via IDoc EQUIPMENT_CREATE, which is
triggered based on a business transaction event (BTE). For inbound processing in your DSC system, you want the
inbound parameter for this IDoc to be processed by a program that is scheduled to run in the background.

Procedure
Carry out the following steps in the DSC system:
Launch Partner Profiles (transaction WE20).
Choose the partner system (logical system) of your ERP system under Partner Type LS.
In the Inbound table, select the row containing the message type EQUIPMENT_CREATE and choose the
Inbound parameter details icon below the table.
Under Processing by Function Module, select Trigger by background program.
Save your changes.
Go back to the SAP Easy Access screen.
Execute report RBDAPP01 from the ABAP Editor (transaction SE38).
Create a variant (for example, EQUI) for message type EQUIPMENT_CREATE and IDoc status 64.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 30
 Launch Define Background Job (transaction SM36) and create a new background job (for example,
EQUIPMENT_CREATE) as follows:.
a. Specify the ABAP program name RBDAPP01 and the variant that you created in the previous step
(in this example, EQUI).
b. Choose Date/Time as the start condition and select the Periodic job checkbox.
c. Enter the start date and time.
d. Choose Period Values, then Other Period, and enter the number of minutes (for example, 5).
Save your background job.

6.6 Define Technical Settings for Data Replication (DSC to ERP

System)
For some processes, data integration from the DSC system to the ERP via DRF is required. For the respective
settings, see the solution-specific guides on the SAP Digital Supply Chain Management, edition for SAP S/4HANA
product page on the SAP Help Portal (for example, PEO Implementation Guide for SAP Digital Supply Chain
Management, Edition for SAP S/4HANA).

6.7 Create a BAdI Implementation to Clear Data When

Replicating Materials (ERP System)
Create a Business Add-In (BAdI) implementation to delete sales and accounting data from materials that you
replicate from your ERP system to your DSC system.

Context
The material master data in your ERP system normally contains accounting, purchasing, and sales data, which is
not relevant or needed by your DSC system. If you replicate this data, your receiving DSC system requires sales
organizations, valuation classes, and information about goods receipts of purchased materials or goods issues to
customers. To prevent referential integrity issues, you create a BAdI implementation in your ERP system to clear
this data before the material is replicated to the target system.

Procedure
Log on to your ERP system.
Create an implementation of the BAdI definition BADI_MATMAS_ALE_CR (Change data in MATMAS IDoc
when Generating an IDoc) in the customer namespace.
Adjust the BAdI implementation to your individual needs.
Save and activate your implementation.

Example
The following example BAdI implementation is based on material master data replication from an ERP system to a
DSC system. It implements enhancement spot BADI_MATMAS_ALE_CR.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 31
Sample Code:

method if_ex_badi_matmas_ale_cr~change_matmas.

* Purpose
* =======
* The material master has many attributes controlling business processes in d
ifferent
* applications like sales, purchasing, production, accounting, and inventory
management.
* Every application needs only a subset of the material's attributes. The MAT
MAS idoc
* replicates all attributes maintained in the source system, if they are not
deleted in
* this BADI. Unnecessary attributes can reference other business objects or c
ustomizing
* entities. If the unnecessary attribute is populated the referenced object m
ust exist,
* even if it is not necessary for the business process running in the client,
or else
* you run into a referential integrity issue.
* Accounting and costing data is for example not necessary in PEO. If the mat
erial's
* accounting and costing data is replicated into the PEO client, then you mus
t still
* create profit centers and valuation classes in the PEO system. To avoid the
need to
* create such referenced but unnecessary business objects in PEO, the unneces
sary
* attributes should be deleted during transfer. This is what the BADI impleme
ntation
* below is doing for PEO.

* The MATMAS idoc must populate all mandatory fields. Additional mandatory fi
elds can be
* defined in the material master configuration (transaction OMS9). Make sure
all
* mandatory fields are populated by the idoc. Make also sure only the attribu
tes
* required for PEO are mandatory in the PEO client.

* When to run this BADI implementation

* ====================================
* Several DSC edition modules could run in the same S/4HANA system in differe
nt clients.
* In this example S/4HANA for Manufacturing for Production Engineering and Op
erations PEO
* is running in client 914. Other modules like PPDS or EWM could run in diffe
rent clients.
* Every module needs different material master attributes, while other attrib
utes are
* unnecessary. Therefore, the BADI implementation for PEO may only run in the
client, in
* which will be sent to the PEO system. If PEO is running in a different clie
nt in your system landscape,
* then this code section must be adjusted.
if f_idoc_header-rcvprn <> 'QDRCLNT914'.
exit.
endif.

* Delete unnecessary material master views

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 32
* ========================================
* If you do not delete the sales org specific views here, then you must maint
ain the
* sales organizations in the destination/PEO system. If you do not delete the
* warehouse specific views here, then you must maintain the warehouse numbers
in the
* destination/PEO system. If in the destination system you only want to manag
e a
* subset of the warehouses, then you should delete here all warehouse views,
which
* are not managed by the destination system.
* Note that storage types and wharehouse numbers may only be deleted if EWM i
s not
* running in the same client (which could make sense to manage the floor stoc
k
* needed for production).
delete t_idoc_data where segnam = 'E1MBEWM'. "Delete accounting views (
B)
delete t_idoc_data where segnam = 'E1MLGTM'. "Delete storage type speci
fic data (L)
delete t_idoc_data where segnam = 'E1MLGNM'. "Delete warehouse number s
pecific data (S)
delete t_idoc_data where segnam = 'E1MVKEM'. "Delete sales org specific
data (V)
delete t_idoc_data where segnam = 'E1MLANM'. "Delete country specific t
ax data
delete t_idoc_data where segnam = 'E1MPGDM'. "Delete material master pr
oduct group
delete t_idoc_data where segnam = 'E1MPOPM'. "Delete forecast parameter
s (P)
delete t_idoc_data where segnam = 'E1MPRWM'. "Delete forecast values
delete t_idoc_data where segnam = 'E1MVEGM'. "Delete material total con
sumption
delete t_idoc_data where segnam = 'E1MVEUM'. "Delete material unplanned
consumption

* Set plant-specific material attributes for DSC side-by-side processing

* ======================================================================
* DSC side-by-side does not do proper inventory management. It only manages
* goods receipts and goods issues related to production orders. For component
* materials the PEO system will only record goods issues, but not goods recei
pts.
* Goods receipts for raw materials relate to purchase orders and purchase ord
ers
* are not managed in the PEO system. Therefore, component inventory in the PE
O
* system will become more and more negative. We must allow negative inventory
* in the DSC system. Proper inventory management with all goods issues and
* goods receipts will be done in the ERP system, to which the DSC side-by-
side
* system is connected.
*
* MRP is performed in the ERP system, not the PEO system. To avoid the need t
o
* maintain MRP customizing like MRP types, lotsizing procedure, etc. the BADI
* implementation deletes such references below.
*
* In this section you could also delete the special procurement key SOBSL.
* In that case you need not maintain special procurement keys in table T460A.
* PEO execution does not support phantom assemblies anyways. Phantom assembli
es

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 33
* could however be used in product engineering. a phantom e-BOM must then be
* flattened in e-BOM to m-
BOM handover. To allow this process special procurement
* key are not blanked out in the code below.
field-symbols: <idoc> like line of t_idoc_data.
data: ls_e1marcm type e1marcm,
ls_e1maram type e1maram.

loop at t_idoc_data assigning <idoc> where segnam = 'E1MARAM'.

ls_e1maram = <idoc>-sdata.
ls_e1maram-
mtpos_mara = space. "No default sales order item type. We don't do sales in P
EO system
replace all occurrences of 'B' in ls_e1maram-
vpsta with ' '. "Accounting
"replace all occurrences of 'L' in ls_e1maram-vpsta with ' '. "Storage
replace all occurrences of 'S' in ls_e1maram-
vpsta with ' '. "Warehouse management
replace all occurrences of 'V' in ls_e1maram-vpsta with ' '. "Sales
replace all occurrences of 'P' in ls_e1maram-
vpsta with ' '. "Forecasting
replace all occurrences of 'G' in ls_e1maram-vpsta with ' '. "Costing

replace all occurrences of 'B' in ls_e1maram-pstat with ' '.

"replace all occurrences of 'L' in ls_e1maram-pstat with ' '.
replace all occurrences of 'S' in ls_e1maram-pstat with ' '.
replace all occurrences of 'V' in ls_e1maram-pstat with ' '.
replace all occurrences of 'P' in ls_e1maram-pstat with ' '.
replace all occurrences of 'G' in ls_e1maram-pstat with ' '.

<idoc>-sdata = ls_e1maram.
endloop.

loop at t_idoc_data assigning <idoc> where segnam = 'E1MARCM'.

ls_e1marcm = <idoc>-sdata.

replace all occurrences of 'B' in ls_e1marcm-pstat with ' '.

"replace all occurrences of 'L' in ls_e1marcm-pstat with ' '.
replace all occurrences of 'S' in ls_e1marcm-pstat with ' '.
replace all occurrences of 'V' in ls_e1marcm-pstat with ' '.
replace all occurrences of 'P' in ls_e1marcm-pstat with ' '.
replace all occurrences of 'G' in ls_e1marcm-pstat with ' '.

* ls_e1marcm-xmcng = 'X'. "Always allow negative inventory

* ls_e1marcm-ekgrp = space. "Purchasing group not required in PEO side-
by-side
* ls_e1marcm-dispr = space. "MRP profile not required in PEO side-by-
side
if ls_e1marcm-dismm <> 'X0'.
ls_e1marcm-dismm = 'ND'. "No MRP performed in PEO side-by-
side, but field is mandatory
endif.
* ls_e1marcm-
disls = space. "Lotsizing procedure not required in PEO side-by-side
** ls_e1marcm-
sobsl = space. "Still replicate special procurement key to allow phantom e-
BOMs in PEO
* ls_e1marcm-lagpr = space. "Storage cost code
* ls_e1marcm-losfx = space. "Setup costs
* ls_e1marcm-fhori = space. "Scheduling margin key
* ls_e1marcm-mrppp = space. "MRP planning calendar

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 34
* ls_e1marcm-
stlal = space. "BOM alternative for costing (we don't do costing in PEO)
* ls_e1marcm-
stlan = space. "BOM usage for costing (we don't do costing in PEO)
* ls_e1marcm-plnty = space. "Task List Type for costing
* ls_e1marcm-plnnr = space. "Routing for costing
* ls_e1marcm-aplal = space. "Routing alternative for costing
* ls_e1marcm-sobsk = space. "Special procurement key for costing
* ls_e1marcm-disgr = space. "MRP group
* ls_e1marcm-awsls = space. "Variance key for cycle counting
* ls_e1marcm-sfepr = space. "Repetitive Manufacturing profile
* ls_e1marcm-lfrhy = space. "Planning cycle
* ls_e1marcm-rdprf = space. "Rounding Profile
* ls_e1marcm-strgr = space. "Planning strategy group
* ls_e1marcm-mdach = space. "Action Control: Planned Order Processing
ls_e1marcm-xmcng = abap_true. "neg. stock allowed
<idoc>-sdata = ls_e1marcm.
endloop.
endmethod.

Note
If PEO is the only module you're running in the DSC edition, the example implementation above is a
starting point. However, if you're running PEO
and EWM together in the same SAP S/4HANA system (where EWM could be used to manage PEO's
floor stock), you need not only the material's manufacturing attributes but also the warehousing
attributes. In this case, the material's warehousing attributes must not be cleared before the data is
sent.
Note
If PEO is the only modul e you're running in the edition of SAP Digital Supply Chain Man agement for
SAP S/4H AN A, the ex ampl e impl ementation abov e is a starting point. However, if you're running PEO and E WM together in the same SAP S /4HANA s ystem ( wher e EWM could be used to man age PEO's floor stock), you need not only the material's manufacturing attribu tes but also the w ar ehousing attributes . In this case, the mat erial' s warehousing attribut es must not be clear ed before th e dat a is sent.
The over all mat erial maint enan ce st atus is mad e up of the individual maint enance st atuses . The individual maint enan ce st atuses hav e the following meaning:

User department Maintenance Status

Work scheduling A
Accounting B
Classification C
MRP D
Purchasing E
Production resources/tools F
Costing G
Basic data K
Storage L
Forecasting P
Quality management Q
Warehouse management S
Sales V
Plant stocks X
Storage location stocks Z

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 35
6.8 Create a BAdI Implementation to Differentiate Materials
Relevant for SAP Advanced Planning and Optimization and
Extended Service Parts Planning (eSPP)
SAP Advanced Planning and Optimization and eSPP cannot be active for the same location product. In case both
solutions are relevant in your DSC edition, implement BAdI CIF_S4_BADI_PRODUCT_OUTBOUND
(enhancement spot CIF_S4_PRODUCT_EHSP) with your logic on ERP releases (for example, set PPSKZ or
ESPPFLG by plant).

Note
When integrating from SAP S/4HANA systems you set this flag in the integration model and the
implementation is not needed to distinguish eSPP and Advanced Planning relevancy.

6.9 Create a BAdI Implementation to Update Planning Flags

When Replicating Materials (DSC System)
In the current release, we have IDoc and CIF updates on material masters. IDocs sent from the ERP system do not
contain the Advanced Planning flag. Therefore, we need to ensure that the flag is not reset unintentionally.
Implement BAdI BADI_MATMAS_ALE_IN in your DSC system to re-read PPSKZ from table MARC and update
inbound values accordingly.

Note
The above coding serves as an example. Depending on your scenario the coding needs to be
adjusted (for example. by considering deletion flags, etc.).

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Setup of Data Replication Framework (DRF) © 2023 SAP AG or an SAP affiliate company. All rights reserved. 36
7 Configure Required Settings
Complete all required settings from the solution-specific guides on the SAP Digital Supply Chain Management,
edition for SAP S/4HANA product page on the SAP Help Portal in your implementation scope before transferring
data.

Important
There are additional BAdI Implementations and other prerequisites defined within the specific
guides that have to be in place before transferring data in order to avoid data inconsistencies.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Configure Required Settings © 2023 SAP AG or an SAP affiliate company. All rights reserved. 37
8 Data Transfer
8.1 Transfer of Business Partners Using Data Replication
Framework (DRF)
You set up the distribution of the following master data from the ERP system to the DSC system using SAP
standard technology DRF-with web services:
• Customers
• Vendors and Carriers
• Employees
• Addresses
The master data distribution for those objects is always from the ERP to the DSC system. In the DRF
communication settings, the sender system is always the ERP system and the receiver system is always the DSC
system.

8.1.1 Activate the Function Module for Master Data

Governance Change Handling
You activate Function Module MDG_BS_BP_OUTBOUND_DRF in the sender system only to transfer business
partner changes. For further details, see SAP Note 2211045.

Procedure
Carry out the following steps in the ERP system:
Activate the function module in Customizing under Cross-Application Components  SAP Business Partner
 Data Distribution > Activate Function Modules.
Search for the following entries:
1. Event: BPOUT
2. Object: BUPX
3. Item: 5000001
4. Function Module: MDG_BS_BP_OUTBOUND_DRF
Set the checkbox Call to active for this entry.
Save your changes.

8.1.2 Execute the Initial Business Partner Data Transfer with

DRF
You execute the initial transfer of business partners to the DSC system.

Procedure
Carry out the following steps in the ERP system:
Execute the initial data transfer of business partners in the SAP Easy Access Menu for Data Cross
Application Components  Processes and Tools for Enterprise Applications  Master Data Governance >
Data Replication  Execute Data Replication (transaction DRFOUT).
Enter the following selection data:

Enter Filter Crit eri a to Include Business Objects, for example for the account group:

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Data Transfer © 2023 SAP AG or an SAP affiliate company. All rights reserved. 38
 Field Value

Replication Model The name of your replication model, for example, BP_DSC001

Outbound Implementation 986_3 (Outbound Impl. for BP/REL via Services)

Replication Mode > Active

Initialization
Options for Report Control Inactive
> Test Run Only
Sav e your ent ries .

Select Execute (F8).

8.1.3 Execute the Delta Business Partner Data Transfer with

DRF
You execute the delta transfer of changed business partners to the DSC system.

Procedure
Carry out the following steps in the ERP system:
Execute the delta data transfer of business partners in the SAP Easy Access Menu for Data Cross
Application Components  Processes and Tools for Enterprise Applications  Master Data Governance 
Data Replication  Execute Data Replication (transaction DRFOUT).
Enter the following selection data:
Enter Filter Crit eri a to Include Business Objects, for example for the account group:

Field Value

Replication Model The name of your replication model, for example BP_DSC001

Outbound Implementation 986_3 (Outbound Impl. for BP/REL via Services)

Replication Mode > Inactive

Initialization
Replication Mode > Active
Changes
Options for Report Control Inactive
> Test Run Only
Sav e your ent ries .

Select Execute (F8).

Note
You can schedule the corresponding report RDRF_MESSAGE_OUT as a background job to transfer
the changes of business partner data regularly.

8.1.4 Monitor Business Partner Transfer with DRF

If you use point-to-point direct communication for the DRF data transfer, you use Web Services Message Monitor
(transaction SRT_MONI) to monitor the data exchange between the systems.
If you use an XI server for the communication, you use XI Message Monitoring (transaction SXI_MONITOR) to
monitor the data exchange between the systems.

8.1.5 Transfer Shipping Points

For more information about transferring shipping points, see TM Integration Guide for DSC Edition.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Data Transfer © 2023 SAP AG or an SAP affiliate company. All rights reserved. 39
8.1.6 Transfer Locations
For more information about transferring locations, see TM Integration Guide for DSC Edition.

8.2 Execute the Initial Transfer of Characteristics via ALE and

IDoc
You transfer characteristics for classification of batches.

Procedure
Carry out the following steps in the ERP system:
Launch Distribute All Characteristics Using ALE (transaction BD91).
Enter the data as shown in the following table:
Field Value

Characteristic Leave empty or enter an interval

Logical system <DSC logical system>, for example, DSCCLNT001

Select Execute.

8.3 Execute the Initial Transfer of Classes

You transfer classes for classification of batches.

Procedure
Carry out the following steps in the ERP system:
Launch Distribute Classes Using ALE: Send Direct (transaction BD92).
Enter the data as shown in the following table:
...

Field Value

Class Type 023 for batch classes

Class Enter the classes you use for batch classification

Logical system <DSC logical system>, for example, DSCCLNT001

Select Execute.

8.4 Execute the Initial Transfer of Material Masters

Prerequisites
You've completed the following steps:
• Configuration of data replication
• Configuration of cross-system production process (see PEO Implementation Guide for SAP Digital
Supply Chain Management, Edition for SAP S/4HANA)
• Configuration to avoid accounting in your DSC system

Procedure
Carry out the following steps in the ERP system:
Launch Execute Data Replication (transaction DRFOUT).
Specify the replication models defined for materials, work centers, and equipment/serial numbers.
Select Initialization under Replication Mode.
Execute the report.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Data Transfer © 2023 SAP AG or an SAP affiliate company. All rights reserved. 40
8.5 Execute the Initial Transfer of Batches
You transfer batch master data.

Prerequisites
SAP Note 2745236 is implemented in your ERP system.

Procedure
Carry out the following steps in the ERP system:
...

Launch Batch Master Record Initial Transfer (transaction BD90).

Enter the data as shown in the following table:
Field Value

Material Leave empty

Batch Leave empty

Logical system <DSC logical system>, for example, DSCCLNT001

Select Execute or, if you expect a big amount of data to be transferred, choose Program  Execute in
Background.

Note
Since the batch master records are dependent from the material master data, you want to transfer
only those master records whose material master data has already been transferred. To achieve
this, you must set a dependent filter in the batch distribution model that is not delivered in the
standard configuration, see SAP Note 2793298.

8.6 Execute the Delta Transfer of Master Data

You create IDocs based on change logging of master data.

Context
After activating change pointers for the message types, IDocs are created for the corresponding master data
based on logging of master data changes. In a productive environment, you create IDocs to transfer changed
master data automatically but in the implementation phase, you can also create these IDocs manually.

Note
If you use DRF framework for the distribution of customers and vendors, you must skip this step.
Instead, you use transaction DRFOUT, see section 8.1.3 Execute Delta Business Partner Data
Transfer with Data Replication Framework (DRF).

Procedure
Carry out the following steps in the ERP system:
...

Launch ABAP Program Execution (transaction SA38).

Enter program RBDMIDOC.
Create a variant for each of the following message types:
• CHRMAS: Class system: Characteristics master
• CLSMAS: Class system: Classes master
• CLFMAS: Class system: Classification master
• BATMAS: Batch
Choose Background to define a job to execute all variants of program RBDMIDOC in the background.
Schedule the job to run periodically. With each job run, the system will create IDocs for changed master
data automatically.

Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Data Transfer © 2023 SAP AG or an SAP affiliate company. All rights reserved. 41
Integration of SAP ERP or SAP S/4HANA with SAP Digital Supply Chain Management, Edition for SAP S/4HANA in a Single Client PUBLIC

Data Transfer © 2023 SAP AG or an SAP affiliate company. All rights reserved. 42
 www.sap.com/contactsap

www.sdn.sap.com/irj/sdn/howtoguides

© 2023 SAP AG 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
AG. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The
only warranties for SAP Group 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 AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.