Sample Master Data For Business Partners
Sample Master Data For Business Partners
English
https://www.linkedin.com/in/andersonbrunopaes/
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices Sample Master Data for Business Partners [local] (JA2):
Configuration Guide
1.1.1.1.1 Copyright
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.
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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional
trademark information and notices.
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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names,
screen titles, pushbuttons as well as menu names, paths, and options.
Cross-references to other documentation.
Example Emphasized words or phrases in body text, titles of graphics and tables.
text
EXAMPLE Names of elements in the system. These include report names, program
TEXT names, transaction codes, table names, and individual key words of a
programming language, when surrounded by body text, for example, SELECT
and INCLUDE.
Example Screen output. This style includes file and directory names and their paths,
text messages, source code, names of variables and parameters as well as names
of installation, upgrade, and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER
key.
Example Exact user entry. These are words or characters that you enter in the system
text exactly as they appear in the documentation.
<Example Variable user entry. Pointed brackets indicate that you replace these words
text> and characters with appropriate entries.
Content
Sample Master Data Business Partners, Local: Configuration Guide ....................................... 6
2 Purpose .............................................................................................................................. 6
3 Preparation ......................................................................................................................... 6
3.1 Prerequisites ............................................................................................................ 6
3.2 Supported Deployments ........................................................................................... 6
4 Configuration ...................................................................................................................... 6
4.1 Create Domestic Customers .................................................................................... 6
4.2 Create Domestic Vendors ...................................................................................... 11
4.3 Create Domestic Contacts for Business Partners ................................................. 14
4.4 Create Domestic Customers with Withholding Tax ............................................... 17
4.5 Create Domestic Vendor with Withholding Tax ..................................................... 20
4.6 Create Domestic Vendor (ERS) ............................................................................. 25
5 Manual Build Steps .......................................................................................................... 27
2 Purpose
The purpose of this document is to describe the general configuration steps required to
manually set up the configuration within the system landscape that has already been installed
using the corresponding installation or configuration guides for installation.
If you want to install SAP S/4HANA locally (on-premise) and if you do not want to configure
manually and prefer an automated installation process using BC Sets and other tools, you
can set up a best-practice client and activate the implementation content. For more
information, see the Administration Guide for the Implementation of SAP S/4HANA, on
premise edition which is linked in the content library (included in the documentation package).
3 Preparation
3.1 Prerequisites
Before you start installing this scenario, you must install the prerequisite building blocks. For
more information, see the Building Block Prerequisites Matrix.
4 Configuration
4.1 Create Domestic Customers
1. Access the transaction using the following navigation path:
SAP GUI Transaction BP _Maintain Business Partner
(Enter </nbp> in the transaction call field)
Access via FIORI Launchpad in an OP (On Premise) environment:
Business Role ID and SAP_BR_BUPA_MASTER_SPECIALIST
Name Master Data Specialist - Business Partner Data
Access via FIORI Launchpad in a CLOUD environment:
Business Catalog Role ID SAP_BCR_CMD_BP_MAINT_PC
IW X