Omprakash Netula

6-12-22

Integration between ERP and EWM in S/4 HANA

The following are prerequisites

Org. Master Data Value Master Data Description Comments

Company Code BTO BTO AUTO MANUF S/4HANA Object
Purchasing BTO S/4HANA Object
Organization
Plant BTO S/4HANA Object

Location 0001 Storage Location BTO

AFS S/4HANA Object

ROD
Storage Location SL1 Goods Receipt
SL2 Bin Location
SL3 Bulk Location
Division BO S/4HANA Object

Business area BTO1 S/4HANA Object

Sales org BTOS S/4HANA Object

Distribution Channel BT S/4HANA Object

Sales office BTO S/4HANA Object

Sales Group BTO S/4HANA Object

ERP Warehouse BTO S/4HANA Object

Number
Receiving Point S/4HANA Object
Loading point 01 S/4HANA Object
Supply Chain Unit BTO1 EWM Specific Objects
in S/4HANA
 BTO1
EWM Warehouse EWM Specific Objects
Number in S/4HANA
Custodian Business partner S/4HANA Object
9300000007
created

Entitled to Dispose Business partner S/4HANA Object

9300000007
created

Goods Receipt Office EWM Specific Objects

in S/4HANA
Shipping Point BTO EWM Specific Objects
in S/4HANA
Fiscal Variant S/4HANA Object

MATERIAL S/4HANA Object

Shipping Office BTO EWM Specific Objects

in S/4HANA
OVL2 & OVL3 BTO S/4HANA Object

Delivery split S/4HANA Object

PO S/4HANA Object

BP 9300000007 S/4HANA Object

Storage Type S/4HANA Object

 Client 800
RFC Destination
EW9CLNT800
Logical System EW9CLNT800 S/4 HANA Logical System

Logical System S91CLNT80

EWM Logical System
Logical System Dummy S91CLNT80

Business System Group

BSG
Business System
S3H

Integration between ERP and EWM in S/4 HANA

1 Define REF Destination SM59

SPRO>Integration with other SAP components>EWM>Basic settings up system
Landscape>Setup RFC Destination

T.Code: SM59

2. Define Dummy Logical System

3. BD97

SPRO>SAP NetWaver>Application Server>Idoc Interfaces/Application Link Enabling

(ALE)>Communication>Determine RFC destination for Method Calls.

4. On the assign RFC destination for synchrononous Method of Calls Screen, select relevant
EWM Logical system and choose standard BAPI destination.

In RFC destination for BAPI calls filed enter the RFC destination of SAP S/4 HANA system.

5. Define Queue for Transfer for SAP EWM

 Integration between ERP and EWM in S/4 HANA

For Client 800

Part–A: System Landscape System

ERP Settings
1a: Define Logical System
IMG Path
SPRO>Integration with other SAP components>EWM>Basic settings up system
Landscape>Define Logical System
 Logical System Name

EW9CLNT800 ECC Logical System

S91CLNT80
EWM Logical System

2a: Define RFC Destination

SPRO>Integration with other SAP components>EWM>Basic settings up system

Landscape>Define RFC Destination.

Define RFC Destination with same number as the logical systems (in our example
EW9CLNT800 and S91CLNT800).
Note: Define an RFC user in each target system / client before this step

Comment
RFC Connection Type

S91CLNT80 3 S91CLNT80
EWM Settings

2a: Define Logical System

Define a logical system for each system and assign it to the client being used in each server .

Logical System Name

EW9CLNT800 ECC Logical System

S91CLNT80
EWM Logical System

2b. Define RFC Destinations

Define RFC Destination with same number as the logical systems (in our example
EW9CLNT800 and S91CLNT800).

Comment
RFC Connection Type

EW9CLNT800 3 EW9CLNT800

Additional Settings –
3 Define Business System
➢ A business system will be defined for the EWM (own business system) and for each ERP
system that is connected to EWM system.
 ➢ The SAP EWM system stores the business system in the document flow tables of the
cross-system and cross partner document flow and helps to determine to which ERP
system a document belongs to.
➢ Business systems is mapped to their corresponding logical systems, because the delivery
documents sent from the SAP ERP system to the SAP EWM system contain only the
logical system number of the SAP ERP system.
➢ This mapping helps to determine the business system based on logical system so that the
warehouse request document in EWM can be updated with the corresponding business
system.

SPRO>SCMEWM>EWM>Interfaces>ERP Integration>General Settings>Define Own Business

System>
Business System
BSG

<<IMG
Define Business System

Business System Logical System Maintained Manually

BSG EW9CLNT800 X Flag set

EWM dummy logical system S91CLNT800 X Flag set

3. Assign Business system to Logical system

What is a Logical System and Business system in SAP? What are they used for? What role
do they play in RFC connections?

Here is what I understand by the 2 different systems:

Logical system:

• This is representation for your physical SAP system.

• Usage: This is used to transfer data between 2 systems.
• Ex: if you have a PRD system as PRDECC300. Here, PRDECC300 is the logical
system. This logical system is assigned to your client ex: 100 or 300. In case of
decentralized / embedded EWM, there will be 2 logical systems: 1. ECC or S/4HANA
and other EWM system. Both logical systems must be defined in both systems.

Business system:

• This is name for your logical system.

• Usage: This name is used for mapping logical systems to business systems.
• Ex: if you have a PRD system and name it as PRDECC300. A business system
name BS_ECC is also given to this system. This business system name BS_ECC is
mapped or assigned to logical system name PRDECC300.

Linkage:

• Business system is mapped to Logical System

• ERP warehouse # is mapped to EWM warehouse # via business system
• Distribution model between ERP and EWM logical systems

How it works:

• When a delivery is created in ERP and sent to EWM, the delivery contains
information about the logical system. Since EWM needs the business system name
for warehouse requests, it gets the business system name from the logical system
name.

Let me know if you have any further questions?

 Part - B
Organization Structure Integration

These settings establish the connection between the elements of organization structure (plant,
storage location, warehouse) of ERP and EWM system.

Example

Overview of
Organization Structure Integration between ERP and EWM
Plant: BTO
Storage Location ROD and AFS
ERP WHN: BTO
EWM WHN: BTO1
BP:930000007

ERP Settings

Overview of Organization Structure Integration between ERP and EWM

ERP Settings

4a. Assign Plant to Business Partner (with role FLVN01-Vendor)

➢ From a stock management perspective, plant does not exists in EWM system.
➢ ERP plant is represented by ‘Party Entitled to Dispose’ in EWM stock details.
➢ Party Entitled to Dispose is nothing but a Business Partner (with role FLVN01-Vendor)
that is transferred from the ERP for which Plant is assigned in the general data.( see 4b).

5a-1. Activating Warehouse Management for Plant and Storage Location

An intermediate warehouse number is created and it is assigned to the combination of plant and
storage locations for which EWM is required. This warehouse number is the logical
representation of EWM warehouse in ERP system.

Note: Do not create ERP warehouse by copying template warehouse, as it does not require all the
structural elements of ERP warehouse.
5a-2. Configure EWM Control Parameters

Warehouse is activated as EWM warehouse and a distribution model is created to ensure the
transfer of SAP ERP delivery data to and from the SAP EWM system.
 At the activation of the warehouse as EWM warehouse, the following settings can be chosen.

▪ Comm. WM (Communication external WM)

The correct entry for EWM is Queued and Serialized Asynchronous RFC.

▪ UD (Unchecked Deliveries)

This setting controls if unchecked deliveries are to be distributed. An unchecked delivery is a

delivery with a reduced scope of check. This reduced scope of check refers mainly to the
availability checks, but can also affect other checks. CRM can create unchecked deliveries in
ERP.

▪ Dist. Mode (Distribution Mode)

The setting controls if a delivery is distributed immediately at creation (default entry) or not
(Stop distribution). If the distribution is not done immediately, you trigger the distribution in the
Outbound Delivery Monitor (For Distribution) or with transaction VL06D. You can override this
default setting through the entry in the Distribution Mode of the delivery type. Additionally a
form routine controls the distribution. By manipulating this form routine, you can implement
specific checks and requirements. You can find this by using the transaction code VOFM and
choosing Requirements > Subsequent functions > Distribution.

▪ SN Dec. WM (Allow Serial Numbers in Decentralized WMS)

Once you have selected that the warehouse number is an EWM warehouse, this indicator is set
and not changeable anymore. It means that you can work with serial numbers in EWM, the
details are controlled by the serial number profiles.

▪ BatchDetEW (Batch Determination in EWM via Batch Attribute Replication)

This indicator controls the behavior of the automatic batch determination in ERP outbound
deliveries.
▪ GR fr. EWM only (Goods Receipt from EWM Only)

This indicator enables you to control whether the process of posting the goods receipt for a
manufacturing order into an EWM-managed warehouse can be started from both ERP and EWM
or from EWM only

6a. Linking ERP Warehouse to EWM Warehouse

A link is established between the logical warehouse number of ERP and its counterpart in EWM.

SPRO>SCMEWM>EWM>Interfaces>ERP Integration> GOODS Movement>Map Storage

Location from ERP System to EWM

EWM Settings

SRPO>IMG>EWM>Goods Receipt Process> Configure Availability Group for Putaway

a) Define Availability Group

6b. Linking ERP Warehouse to EWM Warehouse

A link is established between the EWM warehouse number and its logical counterpart in ERP.
Note: This mapping is required in decentralized as well as in embedded EWM.
 Business System plays critical role if decentral EWM system is connected to more than one ERP
systems. It may be possible that the same ERP warehouse number is available in more than one
ERP system that is connected to decentral EWM system. Business system helps to maintain
uniqueness in such cases.

Business Process Integration

These settings establish connection between the elements of business processes (inbound,
outbound, production) of ERP and EWM systems. Business process integration is achieved via
delivery documents.

ERP Settings

7a. Generate Distribution Model

Distribution models required to transfer business documents such as deliveries (inbound,

outbound, posting change) and process/production orders (as Production Material Request).

For creating the distribution model enter –

▪ The ERP warehouse number

▪ The logical system key of the EWM system
▪ A distribution model view

The distribution model view is how you can later locate the distribution model in the
transaction BD64 – Maintenance of Distribution Model.

You can select any of the following as Objects for the distribution model:

▪ Inbound Delivery
▪ Outbound Delivery
▪ Production Material Request
▪ All

It is not helpful to have separate models, so All is the correct choice. Only in case you would
know that the advanced production integration will not be used, it could make sense to
select Inbound Delivery and Outbound Delivery separately.
Following is the display of distribution model in BD64
8. Assign ERP Delivery to EWM Document (Inbound Delivery)

In certain business scenarios such as kit-to-stock and GR for expected goods receipt, it is
possible to push the deliveries from EWM directly which will then create corresponding inbound
delivery document in ERP.

9. Assign ERP Delivery to EWM Document (Direct Outbound)

In certain business scenarios such as direct sales (without sales orders), GI for cost center,
scrapping, kit-to-stock / reverse kitting, immediate deliveries, it is possible to push the deliveries
from EWM directly which will then create corresponding outbound delivery document in ERP.
EWM Settings

7b. Assign EWM Document to ERP Delivery

ERP Delivery Type and Item Category are assigned to EWM Document Type and Item Type
respectively.

Assign EWM Delivery Type

EWM Delivery Type is assigned to ERP Delivery as show in the following picture.

Business System plays significant role if more than one ERP system is connected to decentral
EWM.

The Code for Initiator of a Communication Chain is an additional key, which helps to
distinguish different processes.

This is necessary as sometimes the determination of the document type in ERP is very simple or
because additional information is determined within the context of the received delivery
information.

In this example, ERP delivery type remains same for normal and expected goods receipt but
from EWM context different Document Type required, which is differentiated by Code for
Initiator of a Communication Chain.

In a decentralized EWM system, the “EWM delivery document type” would be an Inbound
Delivery Notification, an Outbound Delivery Request, or a Posting Order Request.
Since EWM 9.5 or with a decentralized EWM based on SAP S/4HANA it is possible to “skip”
these requests or notifications.

The path to do this is EWM Customizing, SCM Extended Warehouse Management > Extended
Warehouse Management > Interfaces > ERP Integration > Delivery Processing > Skip Request
for Messages from ERP (for a SCM based EWM) or SCM Extended Warehouse Management >
Extended Warehouse Management > Interfaces > ERP Integrations > ERP Integration for
Decentralized EWM > Skip Request for Messages from ERP (for a SAP SAP S/4HANA-based
EWM).

This has certain consequences, so you should read the documentation for this Customizing topic
before deactivation.

In a SAP S/4HANA embedded EWM these interim documents are generally not created.

Assign EWM Delivery Item Type

EWM Item Type is assigned to ERP Delivery Item category as show in the following picture.

Differentiation Attribute for Item Type Mapping is an additional key, which helps to
distinguish different processes. This is necessary as sometimes the determination of the item
category in ERP is very simple or because additional information is determined within the
context of the received delivery information.

In this example, ERP item category remains same for normal GR and GR against different
scenarios of stock transfer but form EWM context different Item Type is required, which is
differentiated by Differentiation Attribute.

7c. Assign EWM Document to ERP Order (Manufacturing)

EWM production material request (PMR) Document Type and Item Type are assigned to ERP
manufacturing Order Type as show in the following picture.
Additional Settings – Control Parameters for ERP Version Control

Once the connection between ERP and EWM system is established, set control parameters to
indicate various data transfer options between the systems. These settings are dependent on the
business system of the connected SAP ERP system, and the release and support package.

This table is in Customizing for SCM Extended Warehouse Management under

Extended Warehouse Management > Interfaces > ERP Integration > General Settings > Set
Control Parameters for ERP Version Control

or

Extended Warehouse Management > Interfaces > ERP Integration > ERP Integration for
Decentralized EWM > Set Control Parameters for ERP Version Control (for a SAP S/4HANA-
based EWM). SAP provides standard entries for this table.

Note:
It is actually optional to create an entry for the ERP system in this table. If there no entry in your
EWM system. EWM will behave as if the highest possible ERP enhancement package were
connected. This table is not used for embedded EWM.
References

Google Search engine etc…