![]() For Stages, the sequence is Left to right. The positioning of all the Stages and its related Tasks are already done in the intended logical sequence. At any given point of time, click of the display detail button (as shown above) will give the real-time total count of un-synchronized customer and vendor records. ![]() It is only enabled when the overall CVI Cockpit status is Green and remains disabled, otherwise. Next Steps – This button will provide information on the activities after Customer/ Vendor to BP synchronization. There should be no un-synchronized customer or vendor records (to BP) in the systemĪt all other times, when neither or none of the above conditions are met, the overall CVI Cockpit Status stays Red.The overall CVI Cockpit status becomes Green (Ready), only upon meeting the BOTH the below conditions: Unlike the Tasks and Stages, the Overall CVI Cockpit can have only two valid statuses- Red and Green, indicating Ready and Not Ready respectively. Stage status is Yellow, if one or more of its Tasks are set to yellow.Stage status is Green, only if all its Tasks are set to green.Stage status is Red, if one or more of its Tasks are set to red.Upon the first launch of the CVI Cockpit, all the statuses are defaulted (greyed out).īased on the status of the Tasks, the status of the corresponding Stage is automatically determined. There are three statuses – Red, Green and Yellow. The overall CVI Cockpit, all the Stages and their respective Tasks have a status associated to them.Īll the Tasks of the CVI Cockpit requires manual maintenance of statuses. The CVI Cockpit mainly comprises of three levels – In context of Business Partner – CVI Synchronization, after successful completion of this step, typically user can proceed for system upgrade to S/4HANA. The tasks in this stage mainly enables post-processing of records in the BP synchronization cockpit (to handle customer/vendor records that may have been parallelly created, as typically seen during course of a conversion project) This stage also helps to check the consistency of the BPs created. Upgrade Preparation: This is the fourth and currently the last Stage of CVI Cockpit. These tasks perform the main synchronization activities that creates BP Masterdata in system, for all the customer and vendor records. It has a total of 8 tasks divided into three sections – Pre-Load Activities, Real Load Activities, and Post Load Activities. This stage also gives a provision to customize the checks which user may intend to suppress in a test or sandbox system.ĬVI Load: This is the third stage of CVI Cockpit. The Tasks in this stage performs necessary business checks (functional and customizing) in the Customer and Vendor Masterdata required for CVI synchronization process to Business Partner data model. Preparation: This is the second Stage of CVI Cockpit. ![]() Users can get information about various pre-requisite OSS notes and help documentations, related to CVI migration processes. Read Me: This is the first Stage of CVI Cockpit. The following demonstrates the current structure of the CVI Cockpit, with 4 Stages and its related Tasks: This would enable customer/consultant community to perform CVI Synchronization in a hassle-free manner, assisted by a cognitive Cockpit, and get a holistic view of end-to-end conversion process.įor an ECC system, the CVI Cockpit can be launched via transaction code CVI_COCKPIT. To address the above for ERP/ECC Customers, SAP has delivered a standard centralized guided Cockpit, that would have seamless integration to all the required process components, in the intended sequence. This process was perceived as complex and resulted in high efforts invested by customers/consultants as part of BP/CVI conversion projects. Prior to this, Business Partner Synchronization for ERP customers involved execution of multiple standalone reports/transactions, implementing several OSS Notes, spread across multiple application components. To achieve this synchronization, Customer Vendor Integration (CVI) customizing settings must be active in the system, besides satisfying BP masterdata checks in the existing Customer and Vendor records. It is thereby also a mandatory step for an ERP customer upgrading to S/4HANA, to synchronize their Customer and Vendor Masterdata to Business Partners. In SAP S/4HANA, Business Partner(BP) is the leading object and single-entry point to maintain Customer and Supplier (formerly known as Vendor) master data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |