Click on any node in the graph above to learn more about each configuration step.
The configuration process involves setting up account groups, number ranges, BP roles, and groupings, as well as defining the link between them.
Akila Wedasinghe
SAP S4 HANA MM
What are you looking for?
SAP S/4 HANA Vendor Configuration Guide
Understanding Business Partner and Vendor Integration
Overview
Key Concepts
Configuration Steps
Connections
Tables
Business Partner Approach in S/4 HANA
In SAP S/4 HANA, all vendors must be created through the Business Partner functionality. This represents a significant change from SAP ECC, where vendors could be created directly using transaction XK01.
Key Difference
In ECC, vendor creation (XK01) was independent of Business Partner. In S/4 HANA, XK01 transaction redirects to BP transaction, requiring first creating a Business Partner that will be extended to play a vendor role.
The integration between Business Partner and vendor master data is managed through a series of configuration steps that establish:
- How Business Partner numbers are assigned (BP Groupings)
- How vendor numbers are assigned (Account Groups)
- The relationship between these numbers
- The roles a Business Partner can play (vendor, customer, etc.)
This approach provides several benefits:
- Unified master data management
- Consistent handling of business entities
- Single view of business partners across roles
- Streamlined processes when entities play multiple roles
High-Level Process
The process of creating a vendor in S/4 HANA follows these general steps:
- Configure vendor account groups and Business Partner groupings
- Map these groupings together
- Create a Business Partner (BP) with general information
- Extend the BP to company code role (FLVN00)
- Extend the BP to purchasing organization role (FLVN01)
Once properly configured, this process creates both a Business Partner and a vendor that are linked together, enabling the entity to function within procurement processes.
Key Concepts in Vendor Configuration
👥 Vendor Account Group
Account groups control vendor master data properties, field selection, and number assignment. They determine which fields are mandatory, optional, or hidden when creating vendors.
Configuration Purpose: To group vendors with similar attributes and control how they are created and maintained.
Business Impact: Properly designed account groups streamline vendor creation and ensure consistent data quality.
Related Tables:
- T077K - Vendor Account Groups
- T077D - Field Selection for Account Groups
🔄 Business Partner Grouping
BP groupings control Business Partner number assignment and are the equivalent of account groups at the BP level. They determine what numbers are assigned to Business Partners.
Configuration Purpose: To organize Business Partners and control their number assignment.
Business Impact: Enables consistent numbering across the system and organizes Business Partners by type.
Related Tables:
- TB001 - Business Partner Groupings
- TB002 - Number Range Assignment for BP Groupings
🔗 BP-Vendor Mapping
The mapping between BP groupings and vendor account groups establishes how Business Partners are linked to vendors. This mapping determines whether they share the same number.
Configuration Purpose: To create the relationship between BP and vendor master data.
Business Impact: Enables data consistency across the system and simplifies cross-references.
Related Tables:
- CVI_VEND_LINK - Vendor-BP Links
- CVI_BP_LN_TYPE - BP Link Types
👤 Business Partner Roles
Business Partner roles define what functions a BP can perform in the system. For vendors, the key roles are FLVN00 (company code data) and FLVN01 (purchasing data).
Configuration Purpose: To enable a Business Partner to function in different areas of the system.
Business Impact: Allows a single business entity to play multiple roles (vendor, customer, etc.).
Related Tables:
- BUT100 - BP Roles
- TBP01 - BP Role Categories
🤝 Partner Functions
Partner functions allow vendors to have different sub-roles like ordering address, goods supplier, and invoice party. These functions enable representing complex vendor relationships.
Configuration Purpose: To represent different responsibilities within a vendor relationship.
Business Impact: Enables accurate representation of complex supplier relationships and supply chain processes.
Related Tables:
- T077D - Partner Functions
- LFM1 - Vendor Master Partner Functions
🔢 Number Assignment
Number assignment controls how system numbers are assigned to Business Partners and vendors. It can be internal (system-assigned) or external (user-entered).
Configuration Purpose: To control the numbering strategy for Business Partners and vendors.
Business Impact: Affects data migration, cross-system integration, and reporting capabilities.
Related Tables:
- TNRO - Number Range Objects
- NRIV - Number Range Intervals
Configuration Steps
1
Define Vendor Account Groups
Account groups control vendor number assignment, field selection, and partner roles. They determine which fields are mandatory, optional, or hidden when creating vendors.
IMG > Financial Accounting > Accounts Receivable and Payable > Vendor Accounts > Master Data > Preparation for Creating Vendor Master Data > Define Account Groups with Screen Layout
Why This Step Matters
Account groups are fundamental to vendor data management. They control how vendors are organized, what data is required, and what number ranges are assigned.
Tables Updated
T077K (Vendor Account Groups), T077D (Field Selection for Account Groups)
2
Create Number Ranges for Vendor Account Groups
Number ranges determine what vendor numbers will be assigned when creating vendors with a specific account group.
IMG > Financial Accounting > Accounts Receivable and Payable > Vendor Accounts > Master Data > Preparation for Creating Vendor Master Data > Create Number Ranges for Vendor Accounts
Why This Step Matters
Number ranges define the numbering system for vendors. For integration with Business Partner, it's critical that vendor number ranges are properly aligned with BP number ranges.
Important: For the "Same Number" functionality to work, vendor account groups must use external number assignment.
Tables Updated
TNRO (Number Range Objects), NRIV (Number Range Intervals)
3
Define Business Partner Groupings
BP groupings control Business Partner number assignment and are the equivalent of account groups at the BP level.
IMG > Cross-Application Components > SAP Business Partner > Basic Settings > Define Groupings
Why This Step Matters
BP groupings are the counterpart to vendor account groups at the Business Partner level. They determine how BPs are organized and what numbers they receive.
Tables Updated
TB001 (Business Partner Groupings)
4
Create Number Ranges for BP Groupings
Number ranges for Business Partners determine what numbers will be assigned to the BP, which can later be linked to vendor numbers.
IMG > Cross-Application Components > SAP Business Partner > Basic Settings > Define Number Ranges
Why This Step Matters
These number ranges determine what numbers Business Partners receive. For the "Same Number" functionality to work with vendors, these ranges must align with vendor number ranges.
Tables Updated
TB002 (Number Range Assignment for BP Groupings), NRIV (Number Range Intervals)
5
Map BP Groupings to Vendor Account Groups
This critical step creates the link between Business Partner and vendor, determining how numbers are assigned across both objects.
IMG > Cross-Application Components > SAP Business Partner > Master Data Synchronization > Customer Vendor Integration > Business Partner Settings > Settings for Vendor Integration > Define Number Assignment for Direction BP→Vendor
Why This Step Matters
This mapping is the glue that connects Business Partner and vendor master data. It determines whether they share the same number and how they relate to each other.
Key Setting: The "Same Number" flag determines if BP and vendor numbers will be identical.
Key Setting: The "Flexible Grouping" flag determines if account group selection is available during vendor creation.
Tables Updated
CVICONFIG (CVI Configuration), CVIACCOUNT (CVI Account Group Assignment)
6
Configure Partner Function Determination
Partner functions allow vendors to have different roles (e.g., ordering address, goods supplier, invoice party) within a single vendor entity.
IMG > Materials Management > Purchasing > Partner > Partner Settings in Supplier Master Record > Define Partner Schema and Assign to Account Groups
Why This Step Matters
Partner functions enable representing complex vendor relationships, such as when a vendor has separate ordering and shipping locations.
This configuration determines what partner functions are available for specific vendor account groups.
Tables Updated
T077D (Partner Functions), T077E (Partner Function Assignments)
7
Create Business Partner with Generic Role
Create the Business Partner with basic information before extending it to vendor roles.
Transaction: BP
Why This Step Matters
This creates the foundational Business Partner entity with general information like name, address, and contact details.
At this stage, the Business Partner is just a generic entity without any specific role.
Tables Updated
BUT000 (BP General Data), BUT020 (BP Addresses), BUT021 (BP Address Usage)
8
Extend BP to Company Code (Vendor Role)
Extend the BP to the company code role (FLVN00) to create financial/accounting data at the company code level.
Transaction: BP (Change mode)
Why This Step Matters
This step transforms the generic Business Partner into a vendor at the company code level, enabling financial transactions.
After this step, a vendor number is generated and linked to the BP based on the mapping configured in step 5.
Tables Updated
BUT100 (BP Roles), LFA1 (Vendor Master General Section), LFB1 (Vendor Master Company Code Section)
9
Extend BP to Purchasing Organization
Extend the BP to the purchasing organization role (FLVN01) to create purchasing-related data.
Transaction: BP (Change mode)
Why This Step Matters
This step completes the vendor setup by adding purchasing-specific information, enabling procurement transactions.
After this step, the vendor can be used in purchasing processes like creating purchase orders.
Tables Updated
BUT100 (BP Roles), LFM1 (Vendor Master Purchasing Organization Data)
How Configuration Steps Connect
Understanding the connections between different configuration elements is crucial for successful implementation. The diagram below shows how the various components relate to each other:
Key Integration Points
Account Group to Number Range
Vendor account groups must be assigned to number ranges. These number ranges determine what numbers vendors receive when created.
Impact: For the "Same Number" functionality to work with Business Partners, vendor account groups must use external number assignment.
BP Grouping to Number Range
Business Partner groupings must be assigned to number ranges. These determine what numbers BPs receive when created.
Impact: For the "Same Number" functionality to work, BP number ranges must align with vendor number ranges.
BP Grouping to Vendor Account Group
This is the critical mapping that connects Business Partner and vendor. It determines whether they share the same number.
Impact: Affects how vendors are created from Business Partners and whether they have the same identification numbers.
Account Group to Partner Functions
Partner function schemas are assigned to vendor account groups, determining what partner functions are available for vendors.
Impact: Affects the ability to represent complex vendor relationships with different roles and responsibilities.
Data Flow During Vendor Creation
- When creating a BP, the system uses the BP grouping to determine the number assignment.
- When extending the BP to vendor role (FLVN00/FLVN01), the system uses the BP-Vendor mapping to determine:
- What vendor account group to use
- What vendor number to assign (same as BP or different)
- The vendor account group then determines:
- What fields are required/optional
- What partner functions are available
Key Tables in Vendor Configuration
Understanding the underlying tables helps in troubleshooting and enhances your knowledge of the data model.
Business Partner Tables
BUT000 BP General Data
Contains the basic information about Business Partners, including names, address numbers, groupings, and other general data.
Key Fields: PARTNER (BP Number), BU_GROUP (BP Grouping), NAME_ORG1 (Company Name)
BUT020 BP Addresses
Contains address information for Business Partners, linked to the BP through the address number.
Key Fields: PARTNER (BP Number), ADDRNUMBER (Address Number)
BUT100 BP Roles
Contains the roles assigned to Business Partners (e.g., FLVN00, FLVN01).
Key Fields: PARTNER (BP Number), RLTYP (Role Type)
TB001 BP Groupings
Contains the configuration for Business Partner groupings.
Key Fields: BUSPARTGRP (BP Grouping), BUSPARTGRPTEXT (Description)
TB002 BP Number Ranges
Contains the assignment of number ranges to BP groupings.
Key Fields: BUSPARTGRP (BP Grouping), NROBJ (Number Range Object)
Vendor Master Tables
LFA1 Vendor Master (General)
Contains the general data for vendors, including name, address, and account group.
Key Fields: LIFNR (Vendor Number), KTOKK (Account Group), NAME1 (Name)
LFB1 Vendor Master (Company Code)
Contains vendor data specific to company codes, including payment terms and reconciliation account.
Key Fields: LIFNR (Vendor Number), BUKRS (Company Code), AKONT (Reconciliation Account)
LFM1 Vendor Master (Purchasing)
Contains vendor data specific to purchasing organizations, including currencies and payment terms.
Key Fields: LIFNR (Vendor Number), EKORG (Purchasing Organization)
T077K Vendor Account Groups
Contains the configuration for vendor account groups.
Key Fields: KTOKK (Account Group), TXT30 (Description)
T077D Field Selection
Contains field selection settings for account groups, determining which fields are required/optional.
Key Fields: KTOKK (Account Group), FNAM (Field Name), FOPT (Field Option)
Integration Tables
CVI_VEND_LINK Vendor-BP Links
Contains the links between vendors and Business Partners, creating the integration between the two objects.
Key Fields: PARTNER_GUID (BP GUID), LIFNR (Vendor Number)
CVICONFIG CVI Configuration
Contains the configuration for Customer Vendor Integration (CVI), including number assignment settings.
Key Fields: BUSPARTGRP (BP Grouping), ACCTGROUP (Account Group)
NRIV Number Ranges
Contains the number range intervals for all number range objects, including BP and vendor.
Key Fields: NROBJ (Number Range Object), FROMNR (From Number), TONR (To Number)
SAP S/4HANA Vendor Configuration
Interactive visualization of the vendor master data configuration process
Account Groups
Number Ranges
BP Roles
BP Groupings
Synchronization
Configuration Details
Define Account Groups
Account groups categorize vendors (e.g., domestic, import, employee, government). Different account groups determine which fields are mandatory or optional during vendor master data creation.
Configuration Path: SPRO > SAP Reference IMG > Financial Accounting > Account Receivable and Accounts Payable > Supplier Accounts > Master data > Preparation for creating vendor Master data > Define Account Group.
Example: Creating a new account group with code "9010" for "Domestic Vendor".
Define Number Ranges for Vendor Accounts
Number ranges assign unique identification numbers to vendors. You create the number range series itself.
Configuration Path: SPRO > SAP Reference IMG > Financial Accounting > Account Receivable and Accounts Payable > Supplier Accounts > Master data > Preparation for creating vendor Master data > Create number range for vendor accounts.
The system uses NR status, number range status to define number ranges.
Important note is that it is important to "make it as external" when defining the account group for business partner configuration.
Assign Number Ranges to Vendor Account Groups
Links the defined number ranges to the previously created account groups. This ensures that when a vendor is created under a specific account group, it's assigned a number from the linked number range.
Configuration Path: SPRO > SAP Reference IMG > Financial Accounting > Account Receivable and Accounts Payable > Supplier Accounts > Master data > Preparation for creating vendor Master data > Assign number range to vendor account groups.
Define BP Roles
BP roles determine the type of data that can be maintained for a business partner. Standard BP roles like FLVN00 (company code data) and FLVN01 (purchasing organization data) are used for vendors. General data is associated with the business partner role 'six zeros'.
"FLVN00 is used to maintain the company code information company code data ... if you are selecting the BP rule as FLVN01 that means you are going to maintain the purchasing information about the supplier and for General data we have the standard one again that will be with six zeros."
Configuration Path: SPRO > SAP Reference IMG > Cross Application Components > SAP Business Partner > Business Partner > Basic Settings > Business Partner Roles > Define BP Roles.
Define Number Ranges for Groupings
Assigns unique identification numbers to BP groupings. Crucially, the significance of aligning these number ranges with vendor account number ranges if the business wants vendors to have the same ID in both.
Configuration Path: SPRO > SAP Reference IMG > Cross Application Components > SAP Business Partner > Business Partner > Basic Settings > Number Ranges and Groupings > Define Number Ranges.
Define Grouping and Assign Number Ranges
A grouping is essentially a categorisation for Business Partners, and this step links a number range to the specific grouping.
Configuration Path: SPRO > SAP Reference IMG > Cross Application Components > SAP Business Partner > Business Partner > Basic Settings > Number Ranges and Groupings > Define Grouping and Assign Number Ranges.
Define Number Assignment for Direction BP to Vendor
This step is critical for ensuring that the business partner number and the vendor number are synchronized (or not, depending on the business requirement). It connects the vendor account group and the BP grouping.
Configuration Path: SPRO > SAP Reference IMG > Cross Application Components > Master Data Synchronization > Synchronization Control > Synchronization Control > Customer Vendor Integration > Business Partner Settings > Settings for Vendor Integration > Field Assignment for Vendor Integration > Assign Keys > Define number assignment for direction BP to enter.
The "Same numbers" checkbox is used to ensure the BP and vendor numbers are identical. "Whatever number range you had created for account group and grouping what's same then keep it as seen".
SAP S/4 HANA Vendor Configuration Connection Map
Explore the relationships between key configuration elements in the SAP S/4 HANA vendor management process
Click on any element to see its connections and details. Hover over connections to see their purpose.
Master Data Element
Highlighted Connection
Element Information
Description of the element goes here.
Configuration Purpose:
Purpose information goes here.
Related Tables:
Table information goes here.