Lesson 1 of 5
Why one partner object
7 min
Every company does business with other parties: customers who buy, suppliers who sell, carriers, banks, employees, contact people. In SAP S/4HANA all of them are modeled with one master data object, the business partner (BP). If you came from SAP ECC, this is one of the biggest day-to-day changes. If you are new to SAP, it is simply how partners work.
How ECC did it
SAP ECC kept separate master records for customers and vendors. Sales and finance maintained customers with transactions such as XD01 and VD01; purchasing and accounts payable maintained vendors with XK01 and MK01. Each master had its own number range, its own address, its own bank details and its own tables. A business partner object existed too, but mainly for other components such as CRM, treasury and contract accounting.
That design caused real problems. A company that was both a customer and a vendor existed twice, with two addresses that drifted apart. Netting what you owe a partner against what they owe you needed manual links. Every interface and every migration had to handle two models.
| Topic | SAP ECC | SAP S/4HANA |
|---|---|---|
| Master data object | Separate customer master and vendor master | One business partner with roles |
| Maintenance | XD01/VD01 for customers, XK01/MK01 for vendors | Transaction BP or the Fiori business partner apps; the old customer and vendor transactions redirect to BP |
| Partner that is both customer and supplier | Two records, two addresses | One record, one address, two roles |
| Customer and vendor tables | Primary place data was maintained | Still exist and are filled automatically through customer-vendor integration |
| Other partners (contacts, carriers, employees) | Mixed models | Business partners too, with the appropriate roles |
What SAP S/4HANA does instead
In SAP S/4HANA, the business partner is the single point of entry. You create a BP once with its general data (name, address, communication, bank details, tax numbers) and then add roles for each way you do business with it: customer, supplier, credit management and so on. Behind the scenes, customer-vendor integration (CVI) keeps the familiar customer and supplier records in step, because sales, purchasing and finance processes still read them.
Who notices the change
- Master data teams: one maintenance transaction or app, with role-specific tabs.
- Sales, purchasing and finance users: documents still show customer and supplier numbers, which normally match the BP number.
- Testers: master data tests now cover roles and synchronization, not just one master record.
- Integration teams: interfaces and migration loads target the BP, and CVI creates the customer and supplier records.
Where you maintain business partners
In on-premise and Private Edition systems, transaction BP is the classic maintenance screen; you choose the role in a drop-down at the top and the tabs change to match. The Fiori launchpad offers business partner apps as well, such as Maintain Business Partner, plus apps focused on customers or suppliers, depending on your release and roles. Use the SAP Fiori apps reference library to see which ones apply to your release, and agree as a project which route each team uses so test cases name one app consistently.
What would you do?
A Contoso project member proposes keeping two separate business partners for Lakeside Components, one for purchasing and one for selling scrap back to them, "to keep it simple like ECC". What is the best response?
- SAP S/4HANA models customers, suppliers and other parties as business partners.
- ECC's separate customer and vendor masters caused duplication; the BP removes it.
- General data is entered once; roles add customer, supplier and other views.
- Customer and supplier records still exist and are synchronized by customer-vendor integration.
- Old customer and vendor maintenance transactions redirect to BP in on-premise and Private Edition.
Check your understanding · not graded
Lesson check
1. What is the single point of entry for customer and supplier master data in SAP S/4HANA?
2. A company is both a customer and a supplier. How is it modeled?
3. What happens to the customer and supplier tables in SAP S/4HANA?
4. What happens if you enter XD01 in an on-premise SAP S/4HANA system?