CUSTOMER

Master Data Guide

Multiple Address Handling in SD Documents Using SAP
Business Partner

1
TABLE OF CONTENTS
1 MULTIPLE ADDRESS HANDLING IN SD DOCUMENTS USING SAP BUSINESS PARTNER .... 3
2 SAP BUSINESS PARTNER AND CUSTOMER MASTER DATA .................................................... 3
2.1 Overview ........................................................................................................................................... 3
2.2 Business Functions ......................................................................................................................... 7
2.3 Multiple and Time-Dependent Addresses in Business Partner Master Records ...................... 7
2.4 Address Usages ............................................................................................................................... 9
2.5 Business Partner: Address-Dependent Attributes .................................................................... 11
2.5.1 Address-Dependent International Location Numbers (ILN) ...................................................... 11
2.5.2 Tax Categories ............................................................................................................................... 11
2.6 Customer Master: Address-Dependent Attributes ..................................................................... 12
2.6.1 Address-Dependent General Data ............................................................................................... 12
2.6.2 Address-Dependent Sales Area Data .......................................................................................... 14
2.6.3 Partner Functions .......................................................................................................................... 18
2.6.4 Tax Classifications ........................................................................................................................ 20
2.6.5 Unloading Points / Receiving Points / Departments .................................................................. 21
2.7 Mapping of Partner IDs for B2B-Messages ................................................................................. 22
2.7.1 Convert External to Internal Partner Numbers with Table EDPAR ........................................... 22
2.7.2 Partner Functions with External Identifier (KNREF) .................................................................. 23
2.7.3 Customer Master External Identifier for an Address (Table KNADDR_EXT) ........................... 23
2.8 Integration ...................................................................................................................................... 23
2.8.1 SOAP ............................................................................................................................................... 23
2.8.2 OData .............................................................................................................................................. 24
2.8.3 Migration ......................................................................................................................................... 24
2.8.4 Master Data Governance for Customer (MDG-C) ....................................................................... 24
2.8.5 Master Data Governance, Consolidation and Mass Processing .............................................. 24
3 ADDITIONAL INFORMATION ........................................................................................................ 24
3.1 Multiple Address Handling vs. Multiple Assignment ................................................................. 24
4 APPENDIX....................................................................................................................................... 24
4.1 Table of Figures ............................................................................................................................. 24

2
1 MULTIPLE ADDRESS HANDLING IN SD DOCUMENTS USING SAP BUSINESS PARTNER

In SAP S/4HANA, SAP Business Partner is the leading entity in order to maintain customer and Supplier
master data. Documents in Sales and Distribution (SD) consume the customer master. The aim of the
feature “Multiple Address Handling in SD Documents Using SAP Business Partner” is to increase the
adoption of the SAP Business Partner data model.

The complete functionality of the feature can be enabled by activating two lightweight business functions
(lwBF):

• Activate the business function Multiple Address Handling for Customer Master Data in SAP Business
Partner (BPCUSTOMER_MULTIPLE_ADDRESSES)

• Activate the business function Multiple Address Handling for Business Partners in Sales and
Distribution (Q2C_MULTIPLE_BP_ADDRESSES)

Activating one or both business functions does not immediately impact current master data or processes.
Once the enhanced master data is maintained, the new functionality in SD enables SD applications and
documents to consume it.

The master data for the feature “Multiple Address Handling in SD Documents Using SAP Business Partner”
comprises:

• Multiple and time-dependent addresses of the business partner

• Time-dependent assignment of addresses to address usages

• Implicit address-dependent attributes on business partner and customer master level

If the value of an attribute in the master data would be different when using another address of the
business partner, the attribute is implicitly address-dependent. For example, the field ‘Delivering
Plant’ can have different values depending on the address to which the goods shall be shipped.

This guide describes the enhancements of the master data that are implemented with the feature “Multiple
Address Handling in SD Documents Using SAP Business Partner” and describes how this data can be
maintained.

2 SAP BUSINESS PARTNER AND CUSTOMER MASTER DATA

2.1 Overview
Customers are usually distributed across multiple locations and may have a multi-level structure consisting of
different legal entities:

Legal Entity (Level 1) Legal Entity (Level 2) Addresses Additional Information

SAP SE Germany, Walldorf, Dietmar-
Hopp-Allee
Germany, Rot

3
 SAP Deutschland SE & Germany, Walldorf, Hasso-
Co. KG Plattner-Ring
Germany, Duesseldorf
SAP China China, Beijing Chaoyang
China. Beijing Haidian
China, Shanghai, Nan Jing West
Road
SAP LABS China
China, Beijing
China, Shanghai, Chenhui Road
SAP France SIRET 37982199400215
LEVALLOIS-PERRET
ORSAY SIRET 37982199400264
Paris SIRET 37982199400256
Figure 1: Example of a customer „SAP“ (organizational structure)

The standard customer master data model only allows for a single customer address per customer master
record.

Figure 2: Simplified data model of business partner and CVI (without handling of multiple addresses)

A legal entity with N addresses was therefore typically maintained as N parallel customer master records
assigned to the same number of business partner (BP) master records:

4
 Customer Address Industry Tax Number Delivering Actual Legal Entity Being
Number (STCD1) Plant Shipped to (Not available
in customer master)
SAPWDF1 Germany, Walldorf, Software Munich SAP SE
Dietmar-Hopp-Allee
SAPROT1 Germany, Rot Software Munich SAP SE
SAPWDF2 Germany, Software Munich SAP Deutschland SE & Co.
Walldorf, Hasso- KG
Plattner-Ring
SAPDUE1 Germany, Duesseldorf Software Hamm SAP Deutschland SE & Co.
KG
SAPCHN1 Beijing Chaoyang Software Tianjin SAP China
SAPCHN2 Beijing Haidian Software Tianjin SAP China
SAPCHN3 China, Shanghai, Nan Software Hangzhou SAP China
Jing West Road
SAPCHN4 Beijing Software Tianjin SAP Labs China
SAPCHN5 China, Software Hangzhou SAP Labs China
Shanghai, Chenhui
Road
SAPFR1 LEVALLOIS-PERRET Software 37982199400215 Paris SAP France
SAPFR2 ORSAY Software 37982199400264 Paris SAP France
SAPFR3 Paris Software 37982199400256 Paris SAP France
Figure 3: Example of customer master records for customer SAP (without handling of multiple addresses)

The feature “Multiple Address Handling in SD Documents Using SAP Business Partner” aims to facilitate the
target state of being able to manage a single legal entity using a single business partner, thereby reducing
the required number of business partner and customer master records.
The data model of the SAP Business Partner has always supported the definition of multiple and time-
dependent addresses and their time-dependent assignment to usage types.
The enhanced data model of business partner and customer master records now supports address-
dependent attributes on different levels (for example, on the levels of Business Partner, Customer Data,
General Data, and on the level of Customer/Sales Area).

5
Figure 4: Simplified data model of SAP Business Partner and CVI (with handling of multiple addresses)

When multiple address handling is active, the customer master data can be consolidated. During
consolidation, the following data must be added into the central records:
• The addresses from the single customer master records
• Their address-dependent attributes
:

6
 Customer Industry Default Address Address- Delivering
Number Delivering Dependent Tax Plant /
(“central Plant Fields Address
record”)
SAPSE Software Munich Germany, Walldorf, Dietmar-
Hopp-Allee
Germany, Rot
SAPLGD Software Germany, Walldorf, Hasso- Munich
Plattner-Ring
Germany, Duesseldorf Hamm
SAPCHINA Software Tianjin Beijing Chaoyang
Beijing Haidian
China, Shanghai, Nan Jing Hangzhou
West Road
SAPLABSCN Software Beijing Tianjin
China, Shanghai, Chenhui Hangzhou
Road
SAPFRANCE Software Paris LEVALLOIS-PERRET 37982199400215
ORSAY 37982199400264
Paris 37982199400256
Figure 5: Example of customer master records for customer SAP (with handling of multiple addresses)

2.2 Business Functions

To activate the handling of multiple addresses in SD master data, the following lightweight business function
(lwBF) must be activated:
• Multiple Address Handling for Customer Master Data in SAP Business Partner
(BPCUSTOMER_MULTIPLE_ADDRESSES)
The activation of this lwBF is described in the “Configuration Guide / Multiple Address Handling in SD
Documents Using SAP Business Partner” (note 3067314).
With activation of this lwBF, the enhanced data model of the business partner and customer master is
enabled. The following transactions and integration technologies in SAP S/4HANA support the enhanced
data model:
• Transaction BP
• App Maintain Business Partner
• App Manage Business Partner Master Data
• App Manage Customer Master Data
• Integration: the new fields and structures are exposed independently of the activation of the lwBF.
However, it's required to activate the lwBF so that they can be processed by the system:
o OData (A2X API_BUSINESS PARTNER)
o SOAP (BusinessPartnerSUITEBulkReplicateRequest_Out and
BusinessPartnerSUITEBulkReplicateRequest_In)
o Migration object “Customer – extend existing object by multiple addresses”

2.3 Multiple and Time-Dependent Addresses in Business Partner Master Records

Assigning addresses to a business partner master record is a baseline prerequisite for multiple address
handling.
It is possible to assign as many addresses of a real-world customer to the business partner record as
required. Currently, these can be addresses for the following purposes:
• The central and legal address
• Ordering addresses

7
 • Delivery addresses
• Billing addresses
• Addresses for returns

Figure 6: Assignment of addresses to a business partner (example)

For every address assigned to a business partner, it's possible to add and maintain address-dependent
attributes on BP level and customer level. These address-dependent attributes are described in the chapters
“Business Partner: Address-Dependent Attributes” and “Customer Master: Address-Dependent Attributes” of
this guide.

If time dependency for addresses is activated in the system (ref. to “Configuration Guide / Multiple Address
Handling in SD Documents Using SAP Business Partner” (note 3067314)), the addresses can be managed
with validity periods.

Business Partner Categories and Address Types:

• The category of a business partner defines the address type of all addresses assigned to it:

Business Partner Category Address Type

1 – Person 2 – Personal Address
2 – Organization 1 – Organization Address
3 - Group 1 – Organization Address
Figure 7: Mapping of BP Categories to Address Types

The Customer master only uses addresses of type “1 – Organizational Address". In the case of
business partners of category “2 – Person” the first name, last name, and so on are mapped into the
NAME1/2/3/4-fields of the customer master. Master data synchronization between business partner
and Customer/Vendor (CVI = Customer/Vendor Integration) maps the overall standard address from
the business partner to an address of type “1 – Organization Address” in Customer/Supplier

8
 (KNA1/LFA1).

• With activation of the lwBF Multiple Address Handling for Business Partners in Sales and Distribution
(Q2C_MULTIPLE_BP_ADDRESSES), sales documents as well as their subsequent documents can
consume the addresses directly from the business partner master instead of from the customer
master. This results in the consumption of both aforementioned address types.

Figure 8: Example of an address of type "2 - Personal Address"

2.4 Address Usages

An address of a business partner becomes available for the handling of multiple addresses in sales
documents once it's assigned to an Address Usage.
After the lwBF Multiple Address Handling for Business Partners in Sales and Distribution
(Q2C_MULTIPLE_BP_ADDRESSES)” has been activated, these address usages are used for the handling
of multiple addresses:
• Standard Address (XXDEFAULT)
The address that is currently valid is used to compose the name of the busines partner. It is copied
into the address assigned to the customer master record (standard customer).
It is possible to assign multiple addresses, but their validity must not overlap any other validity.
• Billing Address (BILL_TO)
By assigning customer addresses assigned to this usage, you designate them as addresses to
which invoices (or other billing documents) can be sent.
It is possible to assign multiple addresses as valid at the same time. One of these addresses must
be marked as “default” to achieve an automatic derivation when creating sales documents.
The usage of an address for billing can be limited to a defined validity period.
It corresponds to the partner function “Bill-to Party” (BP).
• Delivery Address
By assigning customer addresses to this usage, you designate them as addresses to which the sold
goods can be sent.
It is possible to assign multiple addresses as valid at the same time. One of these addresses must
be marked as “default” to achieve an automatic derivation when creating sales documents.
The usage of an address as address for delivery can be limited to a defined validity period.
It corresponds to the partner function “Ship-to Party” (SH).
• Supplier Return-to Address
By assigning customer addresses to this usage, you designate them as supplier addresses to which
customers can return goods they purchased.
It is possible to assign multiple addresses as valid at the same time. One of these addresses must
be marked as “default” to achieve an automatic derivation when creating sales documents.

9
 The usage of an address as address for delivery can be limited to a defined validity period.
It corresponds to the partner function “Return-to Address” (RP).

Figure 9: Assignment of addresses to address usages

10
Please note: Multiple and time-dependent addresses and their time-dependent assignments to address
usages are already possible before activation of the lwBF Multiple Address Handling for Customer Master
Data in SAP Business Partner (BPCUSTOMER_MULTIPLE_ADDRESSES).

Please find details regarding time-dependent addresses and address usages and their impact on the
selection of addresses in sales documents in SAP Help Portal: “Understanding Address Selection in SD
Documents”.

2.5 Business Partner: Address-Dependent Attributes

2.5.1 Address-Dependent International Location Numbers (ILN)

ILNs are dependent on a location of a business partner. When multiple address handling is active, they can
be assigned to the respective addresses (table BUT022).
For the ILNs, it's an exclusive “either-or-decision” for address-dependent or independent ILNs. When at least
one ILN is assigned to an address of the business partner, the address-independent ILN must be removed.
There is no fallback logic.

Figure 10: Address-dependent ILN

2.5.2 Tax Categories

As a rule, the address-dependent assignment of tax categories to a business partner is enabled with the
lwBF Multiple Address Handling for Customer Master Data in SAP Business Partner
(BPCUSTOMER_MULTIPLE_ADDRESSES).

11
The address-dependent maintenance of a specific tax category is released with the implementation of the
required logic in the respective country version (individual decision per tax category).
Certain tax categories are released. For details, please check note 3083228 - SAP S/4HANA ON-PREMISE
2021, Globalization Restriction Note for Business Partner Multiple Addresses.

Generally speaking, if no address-dependent tax category is maintained for the business partner, the
address-independent tax category is consumed (fallback to address-independent attributes). However, a
more specific definition is possible in the case of certain tax categories (depending on the local and legal
requirements).

Figure 11: Address-Dependent tax numbers

2.6 Customer Master: Address-Dependent Attributes

2.6.1 Address-Dependent General Data

Address-dependent general data (table KNA1_ADDR) is split into multiple groups of fields. These groups are
arranged across the screens of customer master data.
Once an entry for an address of the business partner is created in one screen, all the values from the
address-independent data are initially copied. With immediate effect, the line for the address-dependent
attributes is added to all the described screens for General Data.
This procedure safeguards a consistent maintenance of the address-dependent attributes. A field with an
initial or empty value would be considered as initial by intention when retrieving address-dependent attributes
from the master data.

Fallback: If an application tries to retrieve data for an address of a business partner and no address-specific
record exists for this address, then the address-independent general data is used as the fallback.

12
• Address-Dependent General Data (for example, Express and Train Stations)
General Data -> Customer General Data

Figure 12: Address-dependent general data

13
 • Address-Dependent Tax Data (for example, City Code, County Code)
General Data -> Customer: Tax Data

Figure 13: Address Dependent Tax Data (General Data)

• Country-specific data
Some localizations (for example, India) are also able to manage address-dependent data. On the
respective screens, this data is added corresponding to the address-independent data.

2.6.2 Address-Dependent Sales Area Data

Address-dependent sales area data (table KNVV_ADDR) is split into multiple groups of fields. These groups
are arranged across the screens of customer master data.
Once an entry for an address of the business partner is created in one screen, all the values from the
address-independent data are initially copied. With immediate effect on all the described screens for Sales
Area Data, the line for the address-dependent attributes is added.
This procedure safeguards a consistent maintenance of the address-dependent attributes. A field with initial
or empty value would be considered as an initial by intention when retrieving address-dependent attributes
from the master data.

Fallback: If an application tries to retrieve data for an address of a business partner and no address-specific
record exists for this address, then the address-independent sales area data is used as the fallback.

14
• Address-Dependent Order Data (for example, Sales Office, Sales Group)
Sales and Distribution -> Orders

Figure 14: Address Dependent Order Data (Sales Area Data)

15
• Address-Dependent Shipping Data (for example, Shipping Conditions, Delivering Plant)
Sales and Distribution -> Shipping

Figure 15: Address-Dependent Shipping Data (Sales Area Data)

16
• Address-Dependent Invoicing Data (for example, Incoterms)
Sales and Distribution -> Billing

Figure 16: Address-Dependent Invoicing Data (Sales Area Data)

17
 • Address-Dependent Status Data (for example, Delivery Block)
Sales and Distribution -> Status

Figure 17: Address-Dependent Status Data (Sales Area Data)

2.6.3 Partner Functions

SAP has activated the handling of multiple addresses for the following partner functions (PF):
• SP – Sold-to
This PF is linked to all addresses of the business partner, that are valid today or in the future.
Note that you can use solutions described in “Configuration Guide / Multiple Address Handling in SD
Documents Using SAP Business Partner” (note 3067314) to restrict the number of addresses.

• SH – Ship-to
This PF is linked to all addresses of the Business Partner assigned to the usage “Delivery Address”,

18
 that are valid today or in the future.

• BP – Bill-to
This PF is linked to all addresses of the business partner assigned to usage “Billing Address”, that
are valid today or in future.

• RP - Return-to Address
This PF is linked to all addresses of the business partner assigned to usage “Supplier Return-to
Address”, that are valid today or in future.

Please note that the partner function “PY – Payer” does not support multiple addresses. The payer is used
as account in accounts receivable. Always the default address of the business partner is used here.

It is possible to combine various options when assigning customer records to partner functions. Here are
some examples:

a) Assign the same customer (reflexive) with multiple addresses:

Figure 18: Partner Functions with reflexive assignment

19
 b) Assign another customer with multiple addresses

Figure 19: Customer with multiple addresses is assigned in Partner Functions

c) Assigning same (reflexive) or another customer without multiple addresses leads to classic behavior
using just the default address

Partner Description and Reference to an Address

Business-to-business (B2B) messages often require a mapping to the identifier of the messaging partner.
When multiple address handling is active, it is not sufficient to just map the customer number, but both the
customer number and the address are required. For this purpose, the partner functions are enhanced by a
reference to the addresses of the business partner.

It is possible to use the same customer number to identify different addresses, for example, different plants
of the customer. The same customer number can now be used multiple times in the partner schema when
it's assigned to different addresses and partner descriptions:

Figure 20: references to addresses of a business partner in Partner Functions

2.6.4 Tax Classifications

Per tax category of the output tax classification, it's possible to define deviating values for the addresses of
the business partner.

20
Figure 21: Address-dependent tax classifications

Fallback: if a consuming application tries to retrieve data for an address of a business partner and no
address-specific record exists for this address, then the address-independent tax classification is used as the
fallback.

2.6.5 Unloading Points / Receiving Points / Departments

All these three entities depend on each other. So, they can be managed per address of the business partner.

21
Figure 22: Address-Dependent Unloading Points / Receiving Points / Departments

Fallback: if a consuming application tries to retrieve Unloading Points / Receiving Points / Departments for an
address of a business partner and no address-specific record exists for this address, then the address-
independent information is retrieved.

2.7 Mapping of Partner IDs for B2B-Messages

2.7.1 Convert External to Internal Partner Numbers with Table EDPAR

In case the customer sends its internal IDs (plant, purchasing organization), these are mapped, via table
EDPAR, to the respective customer numbers per partner role. With activation of multiple address handling,
the customer master now represents multiple locations. It is necessary to map the customer number and the
address, for example, the ship-to address.

This table supports the mapping independent of the sales area.

To map the partner ID and the corresponding address, this table now has the option to manage the
reference to the address of the business partner.

22
Figure 23: Convert External to Internal Partner Numbers

2.7.2 Partner Functions with External Identifier (KNREF)

The IDs a customer sends to identify its own addresses can be different per sales area. For this purpose, the
partner functions have been enhanced with address-dependent descriptions (external identifiers). Please
refer to “Partner Functions“.

2.7.3 Customer Master External Identifier for an Address (Table KNADDR_EXT)

In some setups, the customer already uses the partner ID from the supplier's system (= his customer number
in your system) in his messages. In the buyer's system, the mapping is stored in fields for “our customer
number with the vendor” (LFB1-EIKTO or LFM1-EIKTO), respectively.
If the customer sends the ID of the seller only, the intended address, for example, the ship-to address,
cannot be resolved from the sent customer number without further information. To manage these identifiers
for addresses of the business partner, a table exists on the level of general data in the customer master.

Figure 24: Address-Dependent External References

Note: Before activation of multiple address handling, each individual address was represented by a separate,
individual customer master record. Once the multiple address handling is activated, these customer records
can be consolidated into one record. With this new table the customer can continue to use the previous,
individual customer numbers in his messages.

2.8 Integration

2.8.1 SOAP
The new fields and structures are already exposed with SAP S/4HANA 2021 before activation of the lwBF
Multiple Address Handling for Customer Master Data in SAP Business Partner
(BPCUSTOMER_MULTIPLE_ADDRESSES)
Once this lwBF is activated in the processing system, the fields and structures can be processed (Create,
Read, Update, Delete).

23
2.8.2 OData
The new fields and structures are already exposed with SAP S/4HANA 2021 before activation of the lwBF
Multiple Address Handling for Customer Master Data in SAP Business Partner
(BPCUSTOMER_MULTIPLE_ADDRESSES).
Once this lwBF is activated in the processing system, the fields and structures can be processed (Create,
Read, Update, Delete).

2.8.3 Migration
The new fields and structures are already exposed with S/4HANA 2021 before activation of the lwBF Multiple
Address Handling for Customer Master Data in SAP Business Partner
(BPCUSTOMER_MULTIPLE_ADDRESSES).
Once this lwBF is activated in the processing system the fields and structures can be processed (Create).

2.8.4 Master Data Governance for Customer (MDG-C)

MDG-C was enhanced to support multiple address handling.
The new fields and structures in MDG are enabled when the lwBF Multiple Address Handling for Customer
Master Data in SAP Business Partner (BPCUSTOMER_MULTIPLE_ADDRESSES) is activated.

Please note: the existing restriction in MDG to not support time-dependent addresses and address usages
remains (refer to Time Dependency in SAP Help Portal for Master Data Governance for Business Partner).

2.8.5 Master Data Governance, Consolidation and Mass Processing

Master Data Governance, Consolidation and Mass Processing was enhanced to support multiple address
handling.
The new fields and structures in MDG are enabled when the lwBF Multiple Address Handling for Customer
Master Data in SAP Business Partner (BPCUSTOMER_MULTIPLE_ADDRESSES) is activated.
Please find further information regarding data model in SAP Help Portal: ERP Customer Data Model.

3 ADDITIONAL INFORMATION

3.1 Multiple Address Handling vs. Multiple Assignment

A business partner with multiple customers assigned (multiple assignment) conflicts with multiple addresses.
It is not possible to combine both within one business partner record. Therefore, the system runs checks to
see if any business partners have multiple assignments.
These checks are implemented in all methods of master data maintenance (SAP Fiori, transaction BP,
integration-scenarios).

4 APPENDIX

4.1 Table of Figures

Figure 1: Example of a customer „SAP“ (organizational structure) ................................................................... 4
Figure 2: Simplified data model of business partner and CVI (without handling of multiple addresses) .......... 4
Figure 3: Example of customer master records for customer SAP (without handling of multiple addresses) .. 5
Figure 4: Simplified data model of SAP Business Partner and CVI (with handling of multiple addresses) ...... 6
Figure 5: Example of customer master records for customer SAP (with handling of multiple addresses) ....... 7
Figure 6: Assignment of addresses to a business partner (example) ............................................................... 8
Figure 7: Mapping of BP Categories to Address Types .................................................................................... 8
Figure 8: Example of an address of type "2 - Personal Address" ..................................................................... 9

24
Figure 9: Assignment of addresses to address usages .................................................................................. 10
Figure 10: Address-dependent ILN ................................................................................................................. 11
Figure 11: Address-Dependent tax numbers................................................................................................... 12
Figure 12: Address-dependent general data ................................................................................................... 13
Figure 13: Address Dependent Tax Data (General Data) ............................................................................... 14
Figure 14: Address Dependent Order Data (Sales Area Data) ...................................................................... 15
Figure 15: Address-Dependent Shipping Data (Sales Area Data) .................................................................. 16
Figure 16: Address-Dependent Invoicing Data (Sales Area Data) .................................................................. 17
Figure 17: Address-Dependent Status Data (Sales Area Data) ...................................................................... 18
Figure 18: Partner Functions with reflexive assignment .................................................................................. 19
Figure 19: Customer with multiple addresses is assigned in Partner Functions ............................................. 20
Figure 20: references to addresses of a business partner in Partner Functions............................................. 20
Figure 21: Address-dependent tax classifications ........................................................................................... 21
Figure 22: Address-Dependent Unloading Points / Receiving Points / Departments ..................................... 22
Figure 23: Convert External to Internal Partner Numbers ............................................................................... 23
Figure 24: Address-Dependent External References ...................................................................................... 23

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.
www.sap.com/contactsap
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.

25