Business partner
The Business Partner (BP) is the central, unified way to model people and organisations, customers, vendors, employees, in S/4HANA. It replaces the older separate customer and vendor masters with a single object that can play multiple roles.
Anyone moving from ECC to S/4HANA must understand BP, master-data conversion to Business Partner is a mandatory and often significant part of migration.
- In classic ECC, a customer and a vendor were separate master records even if they were the same company.
- A single BP takes on roles such as FI Customer, FI Vendor, or a sales/purchasing role.
- It replaces the older separate customer and vendor masters with a single object that can play multiple roles.
- Watch out: Treating customer and vendor as separate, BP unifies them in S/4HANA.
Why BP exists
In classic ECC, a customer and a vendor were separate master records even if they were the same company. The Business Partner unifies this: one BP can be both a customer and a vendor (and more) through different roles, eliminating duplication and inconsistency. In S/4HANA, BP is the mandatory, leading approach, this is a key change from ECC.
Roles
A single BP takes on roles such as FI Customer, FI Vendor, or a sales/purchasing role. The role determines which data is maintained and how the BP participates in processes. Behind the scenes, BP still updates the underlying customer/vendor tables via Customer-Vendor Integration (CVI).
Why it matters
Anyone moving from ECC to S/4HANA must understand BP, master-data conversion to Business Partner is a mandatory and often significant part of migration. New learners should learn BP as the default.
Common pitfalls
- Treating customer and vendor as separate, BP unifies them in S/4HANA.
- Ignoring CVI, BP still feeds the classic tables.
- Missing required roles, a BP without the right role cannot act in a process.