GANESH BP Configuration PDF
GANESH BP Configuration PDF
GANESH BP Configuration PDF
1
1. Introduction about Business Partner
Use:-
SAP Business Partner Screening for SAP S/4 HANA is used to centrally manage
master data for business partners, customers, and vendors. With the current
development, it is a single point of entry to create, edit, and display master data for
business partners, customers, and vendors.
Business partners are divided into different categories, which have different attributes
assigned to them. The system distinguishes between:
Groups (for example, societies according to the German Civil Code, people living in
shared apartments)
You use business partner roles to define the functions of the business partner in the
financial transaction. Such roles include counterparty, issuer, paying bank, or
depository bank. You define the rights and responsibilities of the business partner by
assigning the role category. A business partner can have several roles. You define the
roles by assigning a role category.
2
3. Prerequisites Business Partner
We need to do basic customization before creating Business partner configuration. The
below steps are mandatory to update the BP into Customer master while creating
Business partner.
3
If we check the external number range for a customer in XDN1then system will always
consider it as an internal number in BP
Usage:-
Customer Account group control the master data of customer
It helps to determine customer number assignment
It helps to determine which field should be optional and which field should be
mandatory and hide
It control transaction of a customer master
Click or copy from standard and define with your own code.
4
Every one known about this configuration so no need to explain briefly.
Assign number range to account group which is created as per client requirement.
Field status:
Once you select the field status, a new window will open. Then, select Account
Management from the selected group and the click Reconciliation account ‘Req. Entry’
5
3. Configuration for Partner determination
Partner function is two-character identification key that describes the people and
organization with whom you do the business, and who are therefore involved in
transaction. Here is some standard Partner Function for customer-
Sold-to party
Ship-to party
Bill-to party
Payer
The Partner and business partner term in SAP SD refers to parties with whom you do
business. Each business partner has specific role. E.g. Sold-to party - Business
Partner who order the goods / Services. The Partner Determination can be done in
three steps-
IMG Menu Sales and Distribution Basic Functions Partner Determination Set Up Partner
Determination Set Up Partner Determination for Customer Master
Transaction S_AL0_96000423
Code
6
Click system Screen as below appear
Double click PDP and enter our own PDP code with description as per client business
terms then select second option system screen as below appear
7
Step: - 3 Assign PDP to Account group
Select our account group and assign our PDP which is created with initial step.
Assign partner functions to our respect account group then system picked up partner
functions while creating BP
8
4. Business Partner Configuration Setup:-
A business partner role is help to classifying the business partners as per business
terms.
A business partner can take on different business partner roles, which allow different
views of the business partner data depending on the business function.
The above flow chart explains how the BP working in S4 HANA same as VENDOR also.
9
1. Define Business Partner Roles
The role defines the functions a BP has and the business transactions in which it can
be involved and BP roles are to controls the BP views and determine the field’s related
to specific BP role.
Transaction SPRO
Code
10
SAP has given standard roles in S4 HANA BP if we want to create new role as per client
business terms we need to copy the standard role and create our own role as client name.
Transaction SPRO
Code
11
SAP has given standard role category in S4 HANA BP if we want to create new role
category as per client business terms we need to copy the standard role category and
create our own role category as client name
Note: - After creating role category, we need to assign role category to our respect BP
role. Otherwise system will not allow creating BP
12
3. Define Business Partner Role Groupings
In this step we are grouping the multiple BP roles into one BP role grouping whenever
select this role group in dropdown list while creating BP system will show all BP views
related to our BP roles and no need to extend BP role wise.
Transaction SPRO
Code
Here we are grouping the multiple BP roles into one BP role group and system will
show our BP roles in single screen while creating BP.
13
Select our BP role group and double click and add our BP roles
Save it.
After assigning BP roles we need to create BP role grouping category and assign BP role
grouping category into BP role groupings. This is same as e initial configuration steps BP
role category in to BP roles.
14
4. Define Application Transactions
According to this configuration BP role category wise or BP role grouping category wise
we can assign transaction codes as per Client business terms means user defined BP
transactions
Usage:- if we assign our role grouping category to BUP1 system automatically selecting
our BP role group while executing BUP1 and No need to select manually and it will save
end user time
Transaction SPRO
Code
Select any one transaction BUP1 then click details icon system screen as appear as
below:
15
Add our role grouping category and save it then system always considered our
respected role grouping while executing transaction code BUP1.
1. Activity: - if we add any activity system will always considered that activity while
executing BP with respect to BP role category.
2. BP Role category: - if you add our role category system will always considered
respected role category while executing this transaction then system automatically
selected our BP role.
3. BP Role: - if you add our BP role system will always considered respected role
category while executing this transaction then system automatically selected our
BP role.
4. BP Role Groupings: - if you add our role groupings system will always considered
respected role category while executing this transaction then system automatically
selected our BP role.
Add our BP role group category and save it and check it whether it is working fine or not.
If you assign our BP role category to BUP1 transaction code system is always working
with our BP role groupings or BP role while executing BUP1 or ZTCODE.
16
5. Define Number ranges for BP
A Number range is a Group of numbers to which the unique-Id created for an SAP Object
belongs. In each module we have master data having SAP objects such as Equipment,
Notification, Order, Measuring Point, and Maintenance Plans etc. in PM, Material
number, Material Document, Purchase Requisition, Purchase Order in MM, Sales Order,
and Sold-to-party etc. in SD
1. Internal Number ranges: - when we are maintaining number ranges in XDN1 without
external check box system automatically generates the BP or Customer master
number while creating BP or Customer master.
2. External Number ranges: - when we are maintaining number ranges in XDN1 there is a
external check box. if we check the external number range we have to enter manually
while creating BP master or Customer Master.
IMG Menu IMG Cross-Application Components SAP Business Partner Business Partner
Basic Settings Number Ranges and Groupings Define Number Ranges
Transaction BUCF
Code
17
In BP number ranges are always internal and customer number is always external.
Because of while creating BP system background automatically creates customer number
with help of external check box in XDN1 (Customer master) and it will be update in BP
related tables and Customer master tables.
Transaction SPRO
Code
Click enter our account group, number ranges same as created in customer
master and no need to select anything and save it.
18
7. Business Partner Field Grouping (Optional)
In this step we can control the fields like….optional, suppress, and display same as
customer account group field controls.
Transaction SPRO
Code
19
Double click the and system
screen as appear below
This is optional configuration if client wants to suppress any sales related fields we need
to select sales related BP role and control the fields.
In ECC we have same option for controls the customer master fields through customer
account group level but in we can controls through BP role wise etc.…..
20
1. Master Data Synchronization :-
Master data synchronization synchronizes master data objects in an SAP system that are
similar from a business, but not from a technical, point of view, and in this way allows
you to integrate different SAP applications seamlessly in your business processes.
You can use master data synchronization, for example, to set up integration of the SAP
Business Partner with the customer master. This allows you to integrate SAP
applications that make technical use of the Business Partner in their user interface, and
use the customer master as a technical basis in subsequent business processes.
2. Synchronization objects:-
Transaction SPRO
Code
Note: - In this IMG activity you can display synchronization objects provided by SAP for
the master data Synchronization and Do not change anything here.
21
3. Activate PPO Requests for Platform Objects
Use this IMG activity to define for which platform objects a post-processing order
should be written in the event of a synchronization error. This definition is not direction-
specific, that means a request is always written when the platform object is used either
as a source or as a target object in the synchronization. Since we are creating BP from
customer, the BP becomes the platform object here. So add BP in this setting.
Transaction SPRO
Code
Select the required source objects and target objects and mark Active. Since we are
creating BP from customer select Customer BP here
Transaction SPRO
Code
Active.
22
This is main configuration for master data synchronization for BP to Customer mater.
If we uncheck the BP to customer while creating BP only and system will not allow
creating customer master data.
8. Customer/Vendor Integration
The FLCU00 is the role for the FI part of the customer data
The FLCU01 is the role for the SD part of the customer data
23
2. Define BP Role for Direction Customer to BP
Here the link between the BP roles and the FI customer group is defined
We need to assign customer account group to our respected BP roles and system
Always consider this account group is works only for particular account group.
24
3. Field Assignment for Customer Integration
Here the FI account groups are linked to the BP groups. This customizing also links the
number ranges with the option [same numbers] you make sure the BP and customers
are in sync
If we maintaining the same number ranges in customer account group and BP group
then we required check same number.
25