Customer Vendor Integration BLOG Part 3 of 3.
This is the third part of a three part blog post on SAP CVI (Customer/Vendor Integration).
Copyright @V3iT Inc
Copyright @V3iT Inc
Transaction Codes and Tables
We can still use the customer and vendor master data creation transaction codes (XD01/XD02/XD03, XK01/XK02/XK03) once the CVI synchronization procedure in the SAP ECC system is complete. The Business Partner (BP) tables will be updated because the CVI configuration is already in place. Furthermore, because the same numbers are used for vendors and customers, business teams can continue to use the same numbers in their business transactions. This has impact on all FRICE+W items that need due attention and consideration. Following the CVI conversion, it would be nice to know what tables get updated tabulated as below.
Copyright @ V3iT Inc.
As we see above the replacement of data in some tables has to be addressed.
Interfaces and Integrations
Integrations to SAP systems ( For example, SAP CRM, SAP SCM, SAP BW) and Non-SAP systems (EDI, Content or Document Management Systems) must address the replacement of data in specific tables, as seen above. It is necessary to alter and test the mapping structure especially CREMAS and DEBMAS.
The changed structures and tables have an impact on forms, outputs, and workflows. To accommodate the new tables, these must be altered and amended.
For custom enhancements to be accessible in the BP transaction, they must be updated in the Business Partner structures and link tables.
Output and Workflow
Forms have to be changed to reflect Business Partners. Examples of such forms include Purchase Orders, Sales Orders, Invoices and Dunning Letters. Also workflow customer / vendor / employee needs to get replaced by Business Partners in workflows involving Purchase requisitions or Orders for example, Credit Line, Leave of Absence and many more.
Archived / Aged Data
Archived / Marked for Deletion Customers and Vendors are not converted to Business Partners. However, when running MDS Load Cockpit (MDS LOAD COCKPIT), the suppression of data errors (business check) of customer/vendor records indicated for deletion is not performed, and we must repair the customer/vendor records before proceeding.
Copyright @V3iT Inc.
As I conclude the blog posts, it is imperative to consider various aspects before performing the Customer Vendor Integration, while doing the CVI and post CVI to address all the issues and have a successful migration to SAP S/4HANA.
This is the final part of my blog post. Please do read the first and second part of my blog post
"Considerations before CVI" https://blogs.sap.com/2022/04/10/considerations-before-cvi/ and "Lessons Learnt" https://blogs.sap.com/2022/04/28/lessons-learned-during-cvi-conversion/
This is the third part of a three part blog post on SAP CVI (Customer/Vendor Integration).
Copyright @V3iT Inc
Copyright @V3iT Inc
Transaction Codes and Tables
We can still use the customer and vendor master data creation transaction codes (XD01/XD02/XD03, XK01/XK02/XK03) once the CVI synchronization procedure in the SAP ECC system is complete. The Business Partner (BP) tables will be updated because the CVI configuration is already in place. Furthermore, because the same numbers are used for vendors and customers, business teams can continue to use the same numbers in their business transactions. This has impact on all FRICE+W items that need due attention and consideration. Following the CVI conversion, it would be nice to know what tables get updated tabulated as below.
Copyright @ V3iT Inc.
As we see above the replacement of data in some tables has to be addressed.
Interfaces and Integrations
Integrations to SAP systems ( For example, SAP CRM, SAP SCM, SAP BW) and Non-SAP systems (EDI, Content or Document Management Systems) must address the replacement of data in specific tables, as seen above. It is necessary to alter and test the mapping structure especially CREMAS and DEBMAS.
The changed structures and tables have an impact on forms, outputs, and workflows. To accommodate the new tables, these must be altered and amended.
For custom enhancements to be accessible in the BP transaction, they must be updated in the Business Partner structures and link tables.
Output and Workflow
Forms have to be changed to reflect Business Partners. Examples of such forms include Purchase Orders, Sales Orders, Invoices and Dunning Letters. Also workflow customer / vendor / employee needs to get replaced by Business Partners in workflows involving Purchase requisitions or Orders for example, Credit Line, Leave of Absence and many more.
Archived / Aged Data
Archived / Marked for Deletion Customers and Vendors are not converted to Business Partners. However, when running MDS Load Cockpit (MDS LOAD COCKPIT), the suppression of data errors (business check) of customer/vendor records indicated for deletion is not performed, and we must repair the customer/vendor records before proceeding.
Copyright @V3iT Inc.
As I conclude the blog posts, it is imperative to consider various aspects before performing the Customer Vendor Integration, while doing the CVI and post CVI to address all the issues and have a successful migration to SAP S/4HANA.
This is the final part of my blog post. Please do read the first and second part of my blog post
"Considerations before CVI" https://blogs.sap.com/2022/04/10/considerations-before-cvi/ and "Lessons Learnt" https://blogs.sap.com/2022/04/28/lessons-learned-during-cvi-conversion/
- SAP Managed Tags:
1 Comment
