Business Partner & Vendor Master in SAP S/4 HANA | End-to-End Tutorial | BP and Vendor Configuration

Main ideas and lessons (SAP S/4HANA BP ↔ Vendor Master)

• Vendor master in SAP S/4HANA is the central repository of vendor-related master data used across SAP modules for procurement and accounting.
• In ECC, vendor master data was typically handled via multiple segments/transaction codes (general + purchasing + accounting).
• In S/4HANA, SAP introduces/uses the Business Partner (BP) as the leading master data object:
  • BP becomes mandatory for creating Vendor (and Customer) master data.
  • The vendor master is created in the background when you save the BP with the appropriate BP roles and configuration.

---

Vendor master structure (what data is stored where)

Vendor master data is conceptually maintained in segments, used for different business activities:

• General data (identifier-level)
  • Vendor name, address, tax info, bank details, contact information, etc.
• Purchasing data (Purchasing side)
  • Stored at the Purchase Organization level
  • Includes purchasing attributes such as currency, payment terms, partner roles, purchasing indicators, etc.
• Company code data (Accounting side)
  • Stored at the Company Code level
  • Includes FI attributes such as reconciliation account (GL), withholding tax, payment method, etc.

---

ECC vs S/4HANA concept shift (why BP matters)

• ECC
  • Different TCodes to maintain purchasing and accounting segments (e.g., MK01/MK02/MK03, FK01/FK02/FK03; centralized XK01/XK02/XK03).
• S/4HANA
  • Vendor/customer TCodes are obsolete and redirect to BP.
  • Only BP (transaction BP) is used to create/maintain vendor/customer data.
  • Without BP, vendor master creation is not possible.

---

Vendor account group (ECC concept carried into S/4 via configuration)

A vendor account group is a configuration object that classifies vendor masters and controls:

• Field selection / field status (mandatory/optional/hidden/display)
• Number range assignment
• One-time vendor control
• Partner functions admissibility

---

Business Partner key elements (BP category, BP grouping, BP role)

1) BP Category

• Defines the type of entity:
  • Person, Organization, Group
• Impacts:
  • Which entry screens/fields are shown
• Category is static once created.

2) BP Grouping

• Classifies BP into logical groups and controls:
  • BP number range assignment
  • Derivation of the vendor account group in the background
    • i.e., BP grouping → determines vendor account group when creating vendor

3) BP Role (most critical for segment creation)

• Defines the business usage/context of the BP and which data segments get created.
• For vendor creation, roles map to the vendor master segments:
  • General data role (client-level / “general BP”)
  • Company code role (FI/accounting data)
  • Purchase organization role (purchasing data)
• BP role selection controls:
  • Which vendor segments are created in the background
  • Which fields/screens become available (via field selection)

Segregation of duties (SoD):

• Standard roles encourage maintaining FI vs purchasing data separately.
• A central “all-at-once” role may require custom configuration.

---

Sequence for creating a vendor master via BP (high-level logic)

1. Choose BP Category (typically Organization for vendor)
2. Choose BP Grouping
3. Choose required BP Roles:
   • General role (optional for vendor creation, depending on approach)
   • FI role (company code data)
   • Purchasing role (purchase organization data)
4. On saving the BP:
   • System derives vendor account group via BP grouping
   • Creates the vendor master in the background
   • Applies:
     • field status (mandatory/optional/etc.)
     • number range logic
     • one-time/vendor partner function logic (as configured)

---

Configuration methodology (detailed bullet steps from the video)

A) Vendor-related configuration (3 steps)

1. Define vendor account groups and maintain screen layout / field selection
   • T-code: OBD3
2. Define vendor master number ranges
   • T-code: XKN1
3. Assign vendor number ranges to vendor account groups
   • T-code: OBS

B) Business Partner-related configuration (2 steps)

1. Define BP number ranges
   • In BP customizing: Number ranges & groupings
2. Define BP grouping and assign BP number ranges
   • Set up internal vs external “standard grouping” behavior (internal standard / external standard)

C) Integrate BP ↔ Vendor (final “connection” step)

1. Assign BP grouping to vendor account group (key integration)
   • Path: SAP Business Partner → Master Data Synchronization → Customer/Vendor Integration
   • Use configuration for direction BP to vendor (assign keys / number assignment)

Controls include:

• whether BP number and Vendor number should be the same
• whether vendor account group can be flexible on the BP screen

---

Number range logic: when can BP number = Vendor number?

The video explains four possible combinations:

• BP external + Vendor external
  • Same numbers possible (config: “same number ranges for BP and vendor”)
• BP internal + Vendor internal
  • Same numbers not possible (both generated independently)
• BP internal + Vendor external
  • Same numbers possible (BP generated internally, then used externally for vendor)
• BP external + Vendor internal
  • Same numbers not possible (vendor internal generated independently)

Key requirement: To get same numbers, the vendor account group must use an external number range.

---

Field control via configuration (what gets mandatory)

• Vendor account group field status controls which vendor fields are:
  • required entry / optional / suppressed / display
• BP roles trigger vendor segments and thus trigger those field statuses during BP maintenance.

---

Demonstration workflow (what happens “in action” in the video)

1) Create vendor account groups (example)

• Create two vendor account groups:
  • LCL1 (local vendors)
  • FRN1 (foreign vendors)
• Configure field statuses:
  • Example from the demo: mobile phone marked required for the local account group

2) Create vendor number ranges (example)

• 1ZED = external
• 2ZED = internal
• Assign:
  • LCL1 → 1ZED (external)
  • FRN1 → 2ZED (internal)

3) Create BP number ranges and BP groupings (example)

• BP number ranges created to match vendor number ranges as needed
• BP groupings:
  • LCL1 (local BP grouping) with range 1ZED
  • FRN1 (foreign BP grouping) with range 2ZED
• BP groupings configured to support internal/external standard grouping behavior.

4) Integrate BP grouping ↔ vendor account group

• Assign:
  • LCL1 BP grouping → LCL1 vendor account group
  • FRN1 BP grouping → FRN1 vendor account group
• Demonstrate:
  • “same numbers” checkbox allowed only when vendor account group uses external number range
  • “flexible grouping” checkbox allows changing vendor account group on BP screen

5) Verify BP roles drive vendor creation

• Standard BP roles used in demo include:
  • FLVN00 (FI/company-code data)
  • FLVN01 (purchasing/purchase-organization data)
• Vendor creation is controlled by BP role category and integration settings that decide whether vendor master is created.

6) Create a BP and see vendor created in background

• Create BP with BP role Business Partner general first:
  • Saving creates BP only, no vendor yet (unless vendor-triggering roles are selected)
• Then select FI/purchasing roles and save again:
  • Vendor master created in background
  • Same number assigned when configured (e.g., local case)

7) Create vendor master by selecting combined roles (popup behavior)

• Demonstrates an alternative approach where the system creates BP and vendor together when selecting certain roles upfront.

8) Demonstrate different number outcomes

• Show same numbers (when “same numbers” enabled and vendor external range used)
• Show different BP vs vendor numbers when vendor range is internal
• Demonstrate flexible grouping enabling vendor account group change on BP screen.

9) Explain internal vs external standard BP grouping

• If BP grouping left blank:
  • system chooses internal standard grouping (and internal numbers)
• If BP grouping left blank but BP number is entered manually:
  • system chooses external standard grouping (and validates number range)

10) Extend vendor master to additional company codes / purchase organizations

• Extend vendor by selecting:
  • FI role and choosing another company code
  • Purchasing role and choosing another purchase organization
• Demonstrates how vendor master segments expand over time.

11) Reporting vendor extensions

• Uses report M K V Z (Decode MKVZ in demo) to view vendors by purchase organization.

---

Speakers / sources featured

• Primary speaker: The YouTube channel creator (unnamed in subtitles; speaks directly throughout)
• Primary source: SAP documentation concepts and configuration artifacts referenced via SPRO paths and transaction codes (e.g., OBD3, XKN1, OBS, BP, etc.)