Gelsenwasser is migrating to SAP S/4HANA®.
#STORY
The core system includes complete business partner support. This includes everything related to the creation and modification of business partners in SAP S/4HANA®, with regard to the subledger department with accounts payable and accounts receivable accounting as well as all payment transactions.
The data migration follows the approach that master data is a valuable asset. Each business partner may only exist once in the system. This approach references the new data model of the central business partner master that SAP is introducing with SAP S/4HANA®. Each business partner can have different roles, which remain as separate entities under the central partner master. These roles can be customer, vendor, client, or supplier. Eric Tüshaus, Head of Subsidiary Ledgers at Gelsenwasser, summarizes: "We are aware that our target vision is not the easiest approach to pursue. But this is the path we are taking. Anything else would be half-hearted and make no sense."
In line with the chosen approach that master data is a valuable asset, the declared goal from the start of the project has been to maintain high data quality:
- No data may be duplicated.
- All adjustments should be made directly in SAP.
- Special attention is paid to the customer-vendor relationship.
However, after the migration to SAP S/4HANA®, a lot of master data is duplicated in the system. Much of this should have been cleaned up before the data migration. In order to keep to the schedule for the overall migration, the data was migrated largely unchanged. The resulting duplicates contradict the chosen approach that each business partner should only exist once in the system.