If you want to switch to S/4HANA, there is no getting round the SAP business partner. Implementing the business partner and thus transforming your own customer, supplier and contact data is mandatory during an S/4HANA project.
In today's SAP ECC, a business partner, i.e. a company, person or group in which you as a company have an interest, can appear in several processes. Unfortunately, the same master data source is not used for all processes, although there is information that is identical in every process. This forces you to keep generalised data redundant. If you maintain both sales and purchasing relationships with an entity, a supplier and a customer must be created and maintained in the system. If generally valid data changes, both data records must be kept up to date accordingly. The maintenance of redundant data is no longer necessary thanks to the business partner. Where previously several transactions were necessary to keep the master data up to date and of high quality, there is now only one. Knowledge about business relationships becomes more transparent and shifts away from the specialised departments.
The SAP Business Partner represents a centrally maintained entity with which your company maintains relationships. As a superordinate instance, it contains all generally valid information and forwards it to customers and suppliers that continue to exist. This means that the customer/supplier objects continue to exist in an SAP S/4HANA system, but are automatically kept up to date by maintenance in the Business Partner via the so-called customer-vendor integration, or CVI for short.
At least that's the theory according to SAP. In practice, however, this ‘simplified data storage’ actually causes problems. For example, only one email address can now be entered for customers and suppliers, i.e. in the Business Partner. This is then used when sending documents from both sales and purchasing. This causes problems because this information often varies. It should also be mentioned that the ‘Business Partner’ object is not integrated in almost all logistics modules. The customer/vendor objects continue to be used there.
Sounds confusing – and it is.