This is a series of blogs written by SAP subject matter experts to prepare you for your journey to SAP S/4HANA. Ready? Let’s go!
Topic #8 is about the business partner data model, customer vendor integration (CVI), and data cleansing – and their role in correcting your master data before migrating to SAP S/4HANA
When moving to SAP S/4HANA, you must implement the business partner data model in your SAP ERP application. However, the well-known “Customer” and “Vendor” master data objects are still available in SAP S/4HANA and continue to be used in sales, logistics, and financial transactions.
SAP S/4HANA puts high-quality standards on master data and applies an extended set of check rules. You need to correct any inconsistencies found by these checks
before moving to SAP S/4HANA – not during the project.
Include the business partner data analysis in SAP Readiness Check
You can spot possible data inconsistencies in customer and vendor data in the SAP ERP application before implementing the business partner data model and CVI by accessing the master data consistency check report (transaction code CVI_PRECHK). This report is integrated with the data collector of the SAP Readiness Check tool. Make sure you implement and include the analysis results in SAP Readiness Check. For more information, check the blog
Customer Vendor Integration Analysis in SAP Readiness Check.
To learn more about the master data consistency check report, refer to
this blog.
Use the CVI cockpit to synchronize master data
When converting from SAP ERP to SAP S/4HANA, you must synchronize your customer and vendor master data to the business partner data model. Our CVI cockpit (CVI_COCKPIT) provides a centralized tool to guide you through this process. For more on how the cockpit can help, read
this blog.
Need help cleansing address data?
Errors in customer and vendor address data are common. You can automatically find the right postal address and correct erroneous ones by integrating the master data consistency check report with SAP Data Quality Management, microservices for location data. Learn how by reading
this blog.
Check out all topics of the series:
tip #1:
Check Your Add-ons. Now.
tip #2:
Check Your Finance Data Quality
tip #3:
Don’t Just Rework Custom Code. Rethink it!
tip #4:
How to Build Custom Extensions
tip #5:
Plan Ahead with Compatibility Packs
tip #6:
Gain Insight to Build a Solid Business Case
tip #7:
Hardware Planning and Data Volume Management
tip #8:
Curate Your Master Data before Deployment
tip #9:
Understand the Functional Impact
tip #10:
Fix Issues Without Bogging Down Conversion
tip #11:
Optimizing Downtime in Conversions
tip #12:
Find Relevant SAP Notes
tip #13:
Accelerate your Rollout with Test Automation
tip #14:
Implementing SAP Fiori
tip #15:
Integration Analysis in SAP Readiness Check
