[Type here]

BUSINESS PARTNER
 SAP Business Partner is used to centrally manage master data for
business partners, customers, and vendors. Business Partner Application
allows you to create, maintain, and manage business partners. You can
also use this to perform integration with other functions and data
exchange
 A business partner can be 1) organization 2) person
3)group
WHY BUSINESS PARTNER
 Master data is managed centrally
 Maximum data sharing and reuses of data which leads to easier
data consolidation
 General Data available for all different Business Partner roles,
specific data is stored for each role.
 In classical transactions, one customer can only be associated with one
account group. But in Business Partner, multiple roles can be associated
with the same Business Partner A person can be vendor customer
VENDOR/SUPPLIER
The vendor is a Business Partner for whom the material or services can
be procured (Or) Vendor is a business partner to whom amounts are
payable for goods delivered/ services performed by him. Note: The
vendor is also called a creditor, he is the external source of supply.
VENDOR/SUPPLIER MASTER DATA
The vendor master database contains information about the vendors that
supply an enterprise. This information is stored in individual vendor
master records. A vendor master record contains the vendor’s name and
address, as well as data such as:
 The currency used for ordering from the vendor
 Terms of payment
 Names of important contact persons (sales staff)
Since, to the accounts department, vendors are generally creditors
(accounts payable), the vendor master record also contains accounting
information, such as the relevant control account (reconciliation account)
in the general ledger.
Therefore, the vendor master record is maintained by
both Accounting and Purchasing.
[Type here]

Types of Vendoes/Suppliers
 Internal Vendor - Supplier by another company code/Plant within same
company/client
 External Vendor - A company/supplier/vendor who supplies
material/service from outside
 Regular Vendors – A vendor/supplier supplies the material/service at
the client level Regular Vendor is the one where you purchase material
or service regularly. This you can maintain in Info Record (ME11).

 Fixed Vendor: based on the price contract or your understanding with

vendor, you can fix the vendor for supplying material or service. This you
can maintain in Source List (ME01).Here also you can block a vendor for
material or service procurement.

 One Time Vendoe – Supply Only Once

Configuring Business Partner (Vendor) in S/4 Hana

Following are the sequence of Steps:

1. Define BP Role
IMG menu SPRO-Cross-Application Components ® SAP Business Partner ® Business
Partner ® Basic Settings ® Business Partner Roles ® Define BP Roles
Transaction FI_APAR_SEPA_CUST or BUCG
code

BP Role Title Description

000000 Business Partner (Gen.) Business Partner (Gen.)
FLVN00 FI Vendor * Business Partner Vendor
FLVN01 Purchase Vendor * Business Partner
Supplier/VENDOR

Check if not exist, create. Normally even though 000000 is a standard not exist.

These are like our ECC General data, Company code data and Purchasing data
[Type here]

*Note: Change the Title description as per your need. We changed text for easy
understanding

2. Define Number Ranges for BP Group

IMG menu SPRO-Cross-Application Components ® SAP Business Partner ® Business
Partner ® Basic Settings ® Number Ranges and Groupings ® Define Number
Ranges
Transaction BUCF
code

No From No. To Number Ext

01 0010000000 0019999999
02 002000000 0029999999
03 CZA000001 CZA999999 X
04 G0001 GZZZZ X

Here we assign number ranges for each BP Group (like Local / Foreign Vendor).
Same we did in ECC.

Note: Define number ranges as per your business requirement. I have taken only
Four. As per business need we can keep internal or external without any clash

3. Define Groupings and Assign Number Ranges

[Type here]

IMG menu SPRO-Cross-Application Components ® SAP Business Partner ® Business

Partner ® Basic Settings ® Number Ranges and Groupings ® Define Groupings
and Assign Number Ranges
Transaction BUC2
code

Field Name Entry 1 Entry 2

Grouping BP01 BP02
Short Name Local Vendor Foreign Vendor
Description Internal Local Vendor Internal Foreign
Vendor
Number range 01 02
External leave empty Leave Empty
Int. Std. Grping leave empty leave empty
Ext. Std. Grping leave empty leave empty
Hide leave empty leave empty

Field Name Entry 1 Entry 2

Grouping BP03 BP04
Short Name Local Emp Vend Forign Emp Vend
Description External Local External Foreign
Employee Vendor Employee Vendor
Number range 03 04
External X X
Int. Std. Grping leave empty leave empty
Ext. Std. Grping leave empty leave empty
Hide leave empty leave empty

Likewise, as per business requirement make no. ranges and assign as shown if you
more requirement.

Note:i). Internal Std. Grouping can be done for ONE role only. Whatever role you
select here as Internal Std. Grouping, that role will be selected automatically at the
time of BP Creation (in Master data creation- transaction) if you didn’t select any
role.

Note :ii) As Standard SAP, at least ONE internal std. grouping to be defined. SAP
note: 2344905– BP cannot be created from Customer due to error R11124
[Type here]

This means that Standard group will be default if we didn’t select any value.

4. Configure field attributes per client

IMG Menu Cross-Application Components ® SAP Business Partner ® Business
Partner ® Basic Settings ® Field Groupings ® Configure Field
Attributes per Client
Transaction S_A2C_40000180
Code

Double-click Configure Field Attributes for Each Client.

On the Change View “Field Grouping Client-Wide”: Overview screen, create the
following settings:

Create the following settings:

Configure Field Attributes per BP Role: BP Role : BUPA

Double click BUPA à Double click Central Data

 Set Organization: Name 1 to Req.entry

 Set Person: Last Name to Req.entry
[Type here]

5. Configure field attributes per BP Role

IMG menu Cross-Application Components ® SAP Business Partner ® Business Partner ®
Basic Settings ® Field Groupings ® Configure Field Attributes per BP Role
Transaction BUCG
code

Double-click Configure Field Attributes for Each Role Category: FLVN00 and
FLVN01

On the Change View “Field Group BP Role”: Overview screen, choose data correct
data set

We made following fields as mandatory.

FLVN00 >>Vendor: General Company Code >> make mandatory fields :

Reconciliation acct, Sort key and check Double Invoice
[Type here]

FLVN01 >> Vendor: Purchasing>> make mandatory fields : Vendor: Purchase Order
Currency, Vendor: Terms of Payment

Likewise, you can do as per your requirement in other roles and data sets

Each field is assigned with field group no. Even though some data set description not
showing it has field groups assigned to it.

6. Bringing non visible fields in BP Role screen and making mandatory

Sometimes we didn’t find fields in BUCG screen. Like Schema Vendor Group
(Schema Group Supplier- LFM1-KALSK) is not visible in screen. It is hidden /
missing in FLVN01 BP role. Follow below steps to bring that field on screen
[Type here]

BUCG initial screen

Above missing Field group description and Data set description missing can be done
based on Note: 2332494 – Field Groups and Data sets Description missing for the
fields developed for customer and vendor functionality

Step A: Define Field group description in BUS2. Click on New entries

Step B: In BUS2
[Type here]

Please make sure ‘Not a req. field’-flag is not set. After that the customizing in
SPRO can be made for the required field

Select 3352 field group >> Field Group -> Fields

Step C: Define data set description in BUS23

Step D : In BUCG make that field mandatory

[Type here]

7. If field group is assigned two fields and want to make one field mandatory

2032 field group is common for GR-Based Invoice Verification (LFM1-WEBRE)

and Free Goods (LFM1-NRGEW)

If requirement is GR Based Invoice verification is to be made mandatory, but Free

goods is not mandatory.

Step A: in BUS2 do setting as shown

Step B: BUCG do mandatory as shown

[Type here]

8. Maintain form of address

IMG PATH Cross-Application Components ® SAP Business Partner ® Business Partner ® Bas
Settings ® Forms of Address ® Maintain Forms of Address
T-CODE S_ABA_72000037

User Action Key Title Person Org. Grp. Gender

Create 0001 Ms. X X 2 Female
Create 0002 Mr. X X 1 Male
Create 0003 Company X Gender not known
Create 0004 Mr. and Mrs. X Gender not known
Create 0005 Mrs. X X 2 Female

9. Define Identification types

IMG Menu Cross-Application Components ® SAP Business Partner ® Business
Partner ® Basic Settings ® Identification Numbers ® Define
Identification Types
Transaction S_A2C_40000110
Code

On the Change View “Identification Types”: Details screen, create the following
settings, if not exists. Normally all will exist.
[Type here]

10.ERP Customer / Vendor Account group settings

Here we will map BP with our ERP vendor

IMG PATH Financial Accounting (New) ® Accounts Receivable and Accounts Payable ®
Vendor Accounts ® Master Data ® Preparations for Creating Vendor Master Data ®
Create Number Ranges for Vendor Accounts
TCODE S_ALR_87003103

Here we will make all vendor no. ranges as external. Take the same number range
which we defined at BP Group no. ranges BUCF

This is the same what we are doing in ECC

[Type here]

11.Define Account groups with screen layout (Vendors)

IMG PATH Financial Accounting (New) ® Accounts Receivable and Accounts Payable ®
Vendor Accounts ® Master Data ® Preparations for Creating Vendor Master Data
® Define Account Groups with Screen Layout (Vendors)
TCODE S_ALR_87003126

Account Name One-time Field Status

Group account
Z001 Local Vendor Set for all fields the status to “Optional
entry”
Z002 Foreign Vendor Set for all fields the status to “Optional
entry”
Z003 Employee Vendor Local Set for all fields the status to “Optional
entry”
Z004 Employee Vendor Set for all fields the status to “Optional
Expatriate entry”

12.Assign No. range to Vendor account groups

IMG PATH Financial Accounting (New) ® Accounts Receivable and Accounts Payable ®
Vendor Accounts ® Master Data ® Preparations for Creating Vendor Master Data
® Assign Number Ranges to Vendor Account Groups
TCODE S_ALR_87003201
[Type here]

Group Name Numer

range
Z001 Local Vendor 01
Z002 Foreign Vendor 02
Z003 Employee Vendor Local 03
Z004 Employee Vendor Expatriate 04

13.Activation Switch for Functions

IMG Menu Cross-Application Components ® SAP Business Partner ® Activation
Switch for Functions
Transaction S_ABA_72000243
Code

User Action Development Active Description

Set to active BUT020 X Time Dependency BP Addresses
Set to active BUT0BK X Time Dependency BP Bank Data
Set to active BUT100 X Time Dependency BP Roles
[Type here]

14.Activate Function Modules

IMG Menu Cross-Application Components ® SAP Business Partner ® Data
Distribution ® Activate Function Modules
Transaction S_ABA_72000207
Code

User Action Evenet Object Item Function module Call

Create MERGE BUPA 1000000 MERGE_BUPA_CENTRAL X
Create MERGE BUPA 2000000 MERGE_BUPA_FINSERV X
Create MERGE BUPR 1000000 MERGE_BUPR_CENTRAL X
Create BPOUT BUPX 1000000 MDS_BUPA_OUTBOUND X
[Type here]

15.Activate PPO Requests for Platform Objects in the Dialog

IMG PATH Cross-Application Components ® Master Data Synchronization ®

Synchronization Control ® Synchronization Control ® Activate PPO Requests for
Platform Objects in the Dialog
TCODE S_PAB_09000016

User Action Syn. Object PPO Active

Create BP X

16.Activate Creation of Postprocessing Orders

IMG Menu Cross-Application Components ® General Application Functions ®

Postprocessing Office ® Business Processes ® Activate Creation of
Postprocessing Orders
Transaction /SAPPO/72000178
Code

On the Change View “Activate Creation of Postprocessing Orders”:Overview screen,

create the following settings:

User Action Component Business Process Act.

Create AP-MD CVI_03 X
Create AP-MD CVI_04 X
[Type here]

17.Activate Synchronization Options

IMG Menu Cross-Application Components ® Master Data Synchronization ®
Synchronization Control ® Synchronization Control ® Activate
Synchronization Options
Transaction S_PAB_09000018
Code

User Action Component Business Process Act.

Create BP CUSTOMER X
Create BP VENDOR X

18.Define No. assignment for Direction BP to Vendor

IMG PATH Cross-Application Components ® Master Data Synchronization ®

Customer/Vendor Integration ® Business Partner Settings ® Settings for Vendor
Integration ® Field Assignment for Vendor Integration ® Assign Keys ® Define
Number Assignment for Direction BP to Vendor
TCODE S_ALN_01002326

User BP Short Name Vendor Name Same

Action Grouping Account Group Number
Create BP01 Local Vendor Z001 Local Vendor X
[Type here]

User BP Short Name Vendor Name Same

Action Grouping Account Group Number
Create BP02 Foreign Vendor Z002 Foreign Vendor X
Create BP03 Employee Z003 Employee Vendor X
vendor Local
Create BP04 Emp Vendor Z004 Employee Vendor X
Expa Expatriate

Here we assign BP Group and Vendor account group.

19.Set BP Role Category for Direction BP to Vendor

IMG Menu Cross-Application Components ® Master Data Synchronization ®
Customer/Vendor Integration ® Business Partner Settings ® Settings for
Vendor Integration ® Set BP Role Category for Direction BP to Vendor
Transaction S_ALN_01002328
Code

Field Name Entry Value Comment

BP Role Cat. FLVN01
Description Business Partner Vendor (FS: BP)
Vendor-Based X
Optional for Vendor leave empty
Role Control Setting leave empty
Default Settings leave empty
[Type here]

20.Define Tax Categories

IMG PATH SPRO -> Cross-Application components -> SAP Business Partner -> Business
Partner ->Basic Settings -> Tax Number -> Maintain Tax Categories

TCODE S_AEC_66000043

In the note 775919, you can find all the standard tax categories. You could also
define the customized ones. This is addressed in note 201073.

Below are the tax number categories that SAP delivers:

AE0 UAE: VAT Registration Number

BG0 Bulgaria: Vat Registration Number

BG1 Bulgaria: Unified ID Code
BG2 Bulgaria: Personal ID

DE0 Germany: VAT Registration Number

DE1 Germany: Income Tax Number
DE2 Germany: VAT Number
[Type here]

21.Tax Number Categories of Business Partner

Go to >>SM30 :V_TFKTAXNUMTYPE

The function module for those tax number types ends with ‘0’ (eg. DE0, AT0) is
VAT_REGISTRATION_NUMBER_CHECK.
For the others, assign the function module BUPA_TAX_NUMBER_CHECK.

22.Tax Categories system messages

T.Code: SM31 : Table/View ‘T100s’

Field Name Entry 1

Application Area BUPA_TAX
Message no 400
Allowed WEIS-
Standard I
[Type here]

Field Name Entry 1

Switch Off

23.Define Tax Category message control

With this we can control entering same tax number twice in system for ay vendor

T.Code: OBA5

Field Name Entry 1

Application Area BUPA_TAX
Message 400
Online E
Batch E
[Type here]

24.Postal code mandatory can be done in OY07 transaction

25.Partner Roles, Assigning Vendor Account Group, Partner Schemas, Assign

Partner Schemas to Vendor Account Groups is same as we do in ECC

26.Following standard like: Maintain Industry Systems and Industries,Assign

Industries, Maintain Legal Forms, Define Departments, Define Functions,
Define Contact Person Functions, Define Authority, Define VIP Entries,
Maintain Authorization Groups,and their Assignment is common or Business
requirement so not discussed

27.For Mass upload of BP, new transaction Migration cockpit like LTMC. SAP
has delivered some standard objects. All templates available on transaction
download fill and upload then proceed. You need to map the fields.

You also can use XK99 standard Vendor Mass Maintenance