MM Purchasing, SD (Sales and Distribution)

How to create a BP – Business partner

Business Partners

Business Partner can be a person, organization, group of people, or a group of organizations, in which a company has a business interest. It is the single point of entry to create, edit, and display the master data for business partners, customers and vendors. A Business Partner consists of general data like name, address, bank information, etc. as well as role specific information i.e. customer/vendor/employee data.

In Traditional ERP, Customer and Vendor are 2 different partners.

For Customer, we have following views:

  • General Data
  • Company Code Data (Finance)
  • Sales Area Data

For Vendor, we have following views:

  • General
  • Company Code (Finance)
  • Purchasing

In ECC we used to have multiple Transaction codes to created – Customer/Vendor

Customer Master:

  • Overall Customer Master: XD01/XD02/XD03
  • Finance Data: FD01
  • Sales Area Data: VD01

Vendor Master:

  • Overall Vendor Master: XK01
  • Vendor Finance Data: FK01
  • Purchasing Date: MK01

In S4 HANA both customer and vendor get created with one Transaction BP.

Reasons/Advantages of BP:

  1. Data Redundancy: A person can be a Vendor as well as customer, in traditional ERP we must create two objects. With business partner single object is only required.
  2. Multiple Transactions: To create vendor or customer we must go to different transactions. With Business Partner single transaction “BP” is required both objects.
  3. Centrally managing master data for business partners, customers, and vendors.

Business Partner creation

Transaction Code: BP.

Business Partner General Data

You will get a default role 000000 (Business Partner General).

The Business Partner roles you assign to a business partner reflect the functions it has and the business transactions in which it is likely to be involved.

Select the grouping from dropdown which decides the number range.

Number Range

Internal Number Range –Business partner numbers that are assigned internally by SAP when a user attempts to create.

External Number range: Business Partner Number has to be provided manually when creation of BP.

Enter the all mandatory fields for Business Partner General and then save.

We can mark the field mandatory/Optional based on the business requirement.

After entering data click on save.

Customer

Extend BP to Customer Role FLCU00 for Financial Accounting.

Click on Company code and enter the company code for which you wanted to extend the customer:

Maintain all the mandatory fields and then save.

Note: Here in the Company Code Section customer number is presented as .

After saving it will get updated same as BP number.

Go to Account management tab:

Reconciliation Account: We cannot post directly into recon accounts. We can post at sub ledger (Customer) level, it will hit recon GL at the time of general ledger view in the document.

Go to payment Transaction Tab:

Payment Term: Terms of Payment are conditions agreed between business partners for the payment of invoices. The conditions define the due date and the cash discount offered for payment of the invoice within a certain period.

Go to Correspondence tab:

Dunning Procedure: Dunning us for to give remainder to customer, In dunning procedure field we use dunning variant to correspondence.

Go to Customer Status tab:

Posting Block:

1. All Company Codes: Indicates that the account is blocked for posting for all company codes.

2. Selected company codes: Indicates that the account is blocked for posting in the specified company code

Extend Customer for Sales Data with Role FLCU01.

Press Sales and Distribution data button and fill all the mandatory fields.

Sales district: The customer belongs to a certain district

Customer group:

System identifies a group of customers Ex: Wholesaler or Retailer for pricing or generating statistics.

Order probability: The Probability of the customer confirming the inquiry or quotation item as a part of the sales order.

Exchange rate type: We can specify the exchange rate type of this customer depending upon the country of the

customers.

Product proposal procedure: In product proposal procedure we determine how the product proposal should be

displayed in the sales document.

Price group: Ex: [01 = Bulk buyer]

A group of customers who shares the same pricing requirements.

Customer pricing procedure: Ex: [1 = Standard]

The value of this field will be taken into consideration by the system to determine pricing procedure.

Price list: Ex: [01 = Wholesale]

The value of this field can be taken into consideration to create condition table.

Shipping tab:

Delivery priority: Ex: [01 = High]. The delivery priority assign to an item.

Use: We can assign delivery priority to either a material or to a combination of customer and material.

When we process deliveries collectively we can use delivery priority as one of the selection criteria.

Shipping conditions: Ex: [10 = Immediately]

The value of this field will be taken into consideration by the system to determine shipping point (outbound

delivery) along with loading group from the material master and delivering plant of line item.

The value of this field also will be taken into consideration to determine ROUTE

Delivering plant:

We can specify the plant from which the goods should be delivered to the customer.

Use: The plant is automatically copied into the sales order item as a default value.

Partial deliveries: It indicates whether sales order must be delivered completely in a single delivery or whether the order can be partially delivered and completed over several deliveries.

Partial delivery for item: If the business wants to allow partial deliveries for item that we can specify here.

Ex: Value “D” stands for no limit to subsequent deliveries.

Maximum partial deliveries: [9] The line item can be spitted into partial deliveries up to “9” only (system

proposes this value). That means we cannot do more than “9” partial deliveries for line item. This value is not

worthwhile if we set “D” in the partial delivery for item field.

Billing Tab:

Check Rebates: If the business wants to process Rebates for this customer

Invoice dates: It identifies the calendar that determines the schedule of billing dates for

the customers.

INCO TERMS:

Terms of payment:

Account assignment group: We can use this field to determine Revenue accounts, sales deductions, etc as an

account determination. These fields will be used as a mandatory field for account determination (SD and FI/CO integration).

Output Tax: It specifies the tax liability of the customer based on the tax structure of the customer’s country.

Use: We use the tax classification to specify whether the customer is liable for sales taxes Ex: VAT, sales tax, etc.

Then Save.

Customer Master Data is saved

6.2. Vendor

To create FI Vendor, we can extend the Business Partner already created with Role FLVN00 (FI Vendor).

The role can be selected from dropdown.

Click on Company Code.

After selecting Company code press Enter and then fill the Recon account and other mandatory fields.

Go to Account Management tab:

Reconciliation Account: We cannot post directly into recon accounts. We can post at sub ledger (vendor) level, it will hit recon GL at the time of general ledger view in the document.

Go to payment Transaction Tab:

Payment Term: Terms of Payment are conditions agreed between business partners for the payment of invoices. The conditions define the due date and the cash discount offered for payment of the invoice within a certain period.

Payment Method: which may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.

Go to Withholding Tax tab:

Withholding tax Type: This indicator is used to classify the different types of withholding tax. Withholding tax types are to be distinguished from withholding tax codes, to which are allocated the withholding tax percentage rate.

Withholding Tax Code: One or more “withholding tax codes” are assigned to each withholding tax type. One of the things these codes determine is the various percentage rates for the withholding tax type

Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.

Go to Vendor Status tab:

Posting Block:

1. All Company Codes: Indicates that the account is blocked for posting for all company codes.

2. Selected company codes: Indicates that the account is blocked for posting in the specified company code.

But after saving Vendor number will come same as BP number.

Tables LFA1 and LFB1 gets updated.

Extending Vendor to Purchasing Data, select Role FLVN01 from dropdown.

Select Purchasing Data and then choose Purchasing Org and press enter.

Enter all the mandatory fields.

Table LFM1 gets updated.

In a display mode, you can check all the roles Business partner having.

Save the vendor.

* vendor master created successfully*

This is how a BP is created as a vendor as well as a Customer.

Read More: SAP SD Certification Preparation Guide

Leave a Reply

Your email address will not be published. Required fields are marked *