EHP5 for SAP ERP
6.0
June 2011
English
Create Vendor Master
(155.14)
Master Data Procedure
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Create Vendor Master (155.14): MDP
Copyright
© 2010 SAP AG. 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.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System
z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,
OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,
POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,
HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,
WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer,
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.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP France in the United States and in other
countries.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. 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 AG
Page 2 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
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 text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
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 text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 3 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
Contents
Create Vendor Business Scenario ....................................................................................................... 5
1
Purpose ......................................................................................................................................... 5
2
Prerequisites.................................................................................................................................. 5
2.1
3
4
Roles ...................................................................................................................................... 5
Process Steps ............................................................................................................................... 5
3.1
Create Vendor Master for Purchasing Org., Company Code (with or without Procurement) 5
3.2
Create CPD Vendor ............................................................................................................... 7
3.3
Create One-Time-Vendor....................................................................................................... 9
3.4
Create Vendor for Travel...................................................................................................... 10
Appendix...................................................................................................................................... 11
4.1
Reversal of Process Steps ................................................................................................... 11
© SAP AG
Page 4 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
Create Vendor Business Scenario
1
Purpose
In this document, you create a vendor business scenario.
Before you run any processes in this document:
Option A: If the vendor is Procurement - related, go to step 3.1.
Option B: If the vendor is not Procurement - related, go to step 3.1.
2
Prerequisites
2.1 Roles
Use
The following roles must have been installed to allow the relevant activities to be carried out in the
SAP NetWeaver Business Client (NWBC). In addition, they must be assigned to the user or users
who will perform the process steps described in this document. You do not need these roles if you
are not using the NWBC interface, but the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user(s) who will perform the process steps described
in this document.
Business role
Technical name
Process step
Employee
(Professional User)
SAP_NBPR_EMPLOYEE_S
Assignment of this role is necessary
for basic functionality.
Purchaser
SAP_NBPR_PURCHASER_S
Create Vendor Master
3
Process Steps
3.1 Create Vendor Master for Purchasing Org., Company
© SAP AG
Page 5 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
Code (with or without Procurement)
Use
Detailed information about the vendor (for example, name, address, payment terms) is
communicated to accounts payable.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP Menu
Logistics Materials Management  Purchasing  Master Data
 Vendor  Central  Create
Transaction code
XK01
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role
Business role (Name)
Purchaser (SAP_NBPR_PURCHASER_K)
NWBC Menu
Purchasing  Master Data  Vendors  Create Vendor
2. Select the Create vendor: Initial Screen, and maintain the necessary fields.
Field Name
User Action and Values
Comment
Vendor
Vendor number
Number range is
300000 – 399999
Company code
1000
Purchase
organization
Account group
1000
YB01
Account group for
regular vendors
Reference:
It is possible to use an existing vendor as reference and make an entry in the area “reference” in
the fields Vendor, Company code and Purchasing Organization (Several field values of the
reference vendor will posted by the system in the new vendor master data).
3. Choose Enter
4. On the Create Vendor : Address screen, enter Name, Search term 1, Street, House number,
District, Postal code, City, Country, Tax jurisdiction code , Region, Telephone, Fax, then choose
Next Screen (F8).
5. On the Create Vendor: Control screen, enter their customer number (if vendor is also customer;
the number must be a valid customer number), on field Tax number 1 enter CNPJ, on field Tax
number 3 enter Insc. Estadual, if necessary on field Tax Number 4 enter Insc. Municipal, Tax
Jur., Tax base (0), then choose Next Screen (F8).
© SAP AG
Page 6 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
6. On the Create Vendor: Payment transactions accounting screen, on Banck Details enter
Country, Bank Key, Bank Account, , then choose Next Screen (F8).
7. On the Create Vendor: Accounting information accounting screen, enter the Recon. account,
Sort Key, Cash mgmnt group, Interest freq, then choose Next Screen (F8).
8. On the Create Vendor: Payment transactions Accounting enter payment terms, Chk double inv.,
and Payment methods, then choose Next Screen (F8) twice
9. On the Create Vendor: Correspondence Accouting data screen, enter Dunning level, then
choose Next Screen (F8).
10. On the Create Vendor: Withholding tax Accouting, enter the necessary Withholding Tax Type,
Withholding Tax Code, flag Liable as the following table..
Wth.t.type
W/tax code
Liable
Exem.%
Description
CA
CA
X
0,00
COFINS at Payment
WHT
IS
R5
X
0,00
ISS
IW
IW
X
0,00
ISS WHT
PA
PA
X
0,00
PIS at Payment WHT
RA
RA
X
0,00
IR at Payment WHT
SA
SA
X
0,00
CSLL at Payment
WHT
11. On the Create Vendor: Purchasing data screen, enter Order currency, terms of payment,
Incoterms, GR based inv. verif.,
12. Choose Save.
Result
The Vendor Master for Purchasing Organization is created.
3.2 Create CPD Vendor
Use
In this activity, you create the vendor master for a so-called CPD vendor. A CPD vendor could e.g.
be used when the payment of purchase order is effected in cash money.
© SAP AG
Page 7 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP Menu
Logistics Materials Management
Data  Vendor  Central  Create
Transaction code
XK01
 Purchasing  Master
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role
Business role (Name)
Purchaser (SAP_NBPR_PURCHASER_S)
NWBC Menu
Purchasing  Master Data  Vendors  Create Vendor
2. Select Create vendor: Initial Screen screen, and maintain the necessary fields.
Field Name
User Action and Values
Comment
Vendor
Vendor number
Number range is
A – ZZZZZZ
Company code
1000
Purchase
organization
1000
Account group
CPDL
Account group for
regular vendors
3. Choose Enter.
4. On the Create Vendor : Address screen, enter Name, Search term 1, Street, Country, Language,
then choose Next Screen (F8).
5. On the Create Vendor: Control screen, enter reference account group, e.g. 0001, then choose
Next Screen (F8) .
6. On the Create Vendor: Accounting information accounting screen, enter the Recon. Account.,
e.g. 212000 and choose Next Screen (F8) .
7. On the Create Vendor: Payment transactions Accounting enter payment terms and Payment
methods, then choose Next Screen (F8).
8. On the Create Vendor: Correspondence Accouting data screen, is not necessary to fill fields,
then choose Next Screen (F8).
9. On the Create Vendor: Withholding tax Accouting screen, is not necessary to fill fields, then
choose Next Screen (F8).
10. On the Create Vendor: Purchasing data screen, enter Order currency,.
11. Choose Enter.
12. Save your entries
© SAP AG
Page 8 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
3.3 Create One-Time-Vendor
Use
In this activity, you create the vendor master for a so-called one-time-vendor. A one-time-vendor
could e.g. be created by a purchaser during a telephone call with a vendor who wants to deliver
goods, but a vendor master does not yet exist for him in the system and an order confirmation is
immediately required.
Later, when the purchaser has time to enter all data properly, he can create a regular vendor master
and exchange the vendor number in the relevant purchase order.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP Menu
Logistics Materials Management  Purchasing  Master Data
 Vendor  Central  Create
Transaction code
XK01
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role
Business role
Purchaser (SAP_NBPR_PURCHASER_S )
NWBC Menu
Purchasing  Master Data  Vendors  Create Vendor
2. Select Create vendor: Initial Screen, and maintain the necessary fields.
Field Name
User Action and Values
Comment
Vendor
Vendor number
Number range is
A – ZZZZZZ
Company code
1000
Purchase
organization
1000
Account group
YB01
Account group for regular
vendors
3. Choose Enter.
4. On the Create Vendor : Address screen, enter Name, Search term 1, Street, Country, Language,
then choose Next Screen (F8).
5. On the Create Vendor: Control screen, enter their customer number (if vendor is also customer;
the number must be a valid customer number), on field Tax number 1 enter CNPJ, on field Tax
number 3 enter Insc. Estadual, then choose Next Screen (F8) .
6. On the Create Vendor: Accounting information accounting screen, enter the Recon. account,
Sort Key, then choose Next Screen (F8) .
7. On the Create Vendor: Payment transactions Accounting enter payment terms, Chk double inv.,
and Payment methods, then choose Next Screen (F8)
8. On the Create Vendor: Correspondence Accouting data screen, is not necessary to fill fields,
then choose Next Screen (F8).
© SAP AG
Page 9 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
9. On the Create Vendor: Withholding tax Accouting screen, is not necessary to fill fields, then
choose Next Screen (F8).
10. On the Create Vendor: Purchasing data screen, enter Order currency reference to Vendor. (E.g:
BRL – Real Brazil)
11. Choose Enter.
12. Save your entries
Result
The one-time-vendor master is created and can be used to create a purchase order. Later, the
created vendor number can be exchanged by a regular vendor number.
3.4 Create Vendor for Travel
Use
In this activity, you create the vendor master for Travel.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP Menu
Logistics Materials Management  Purchasing  Master Data
 Vendor  Central  Create
Transaction code
XK01
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role
Business role (Name)
Purchaser (SAP_NBPR_PURCHASER_K)
NWBC Menu
Purchasing  Master Data  Vendors  Create Vendor
1. Select Create vendor: Initial Screen, and maintain the necessary fields.
Field Name
User Action and Values
Comment
Vendor
Vendor number
Number range is
YB999XXX – YB999XXX
Company code
1000
Purchase
organization
Account group
Your company code
Leave empty for the commercial
traveller
YREI
Account group for commercial
traveller
2. Choose Enter.
3. On the Create Vendor : Address screen, enter Name, Search term 1, Street, House number,
District, Postal code, City, Country, Tax jurisdiction code , Region, Telephone, Fax, then choose
Next Screen (F8).
© SAP AG
Page 10 of 11
SAP Best Practices
Create Vendor Master (155.14): MDP
4. On the Create Vendor: Control screen, enter their customer number, on field Tax number 2 enter
CPF, Natural Person, then choose next screen.
5. On the Create Vendor: Payment transactions screen, on Banck Details enter Country, Bank Key,
Bank Account, enter payment terms, then choose Next Screen (F8) twice.
6. On the Create Vendor: Accounting information: Accounting screen, enter Recon. Account, e.g.:
Travel expenses payable, the Personnel number that is the employee relating to the vendor in
the system.
7. On the Create Vendor: Payment transactions accounting screen, enter payment terms, Chk
double inv., and Payment methods, then choose Next Screen (F8) twice.
8. Choose Enter.
9. Save your entries.
Result
The vendor for travel master is created and can be used to create a purchase order. Later, the
created vendor number can be exchanged by a regular vendor number.
4
Appendix
4.1 Reversal of Process Steps
In the following section, you can find the most common reversal steps, which you can take to
reverse some of the activities described in this document:
Create Vendor Master
Transaction code ( SAP GUI)
XK01
Reversal:
Set Deletion Indicator
Transaction code ( SAP GUI)
XK06
Business role
Purchaser (SAP_NBPR_PURCHASER_K)
NWBC Menu
Purchasing  Master Data  Vendors  Flag Vendor for
Deletion
Comment
Set checkbox all areas.
© SAP AG
Page 11 of 11