Skip to Content
Product Information
Author's profile photo Saptarshi Sen

CVI Cockpit – Enabling Movement to SAP S/4HANA through seamless BP Synchronization

Business Context / Motivation:

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. 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. 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.

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. This process was perceived as complex and resulted in high efforts invested by customers/consultants as part of BP/CVI conversion projects.

 

Solution:

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 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.

Details:

Transaction

For an ECC system, the CVI Cockpit can be launched via transaction code CVI_COCKPIT.

 

Structural Overview

The following demonstrates the current structure of the CVI Cockpit, with 4 Stages and its related Tasks:

Overall CVI Cockpit <Status> <Info>

  • Read Me
    • Note Checker
    • CVI Library
  • Preparation
    • Master Data Consistency
    • Automated Customizing
    • Suppress Checks
  • CVI Load
    • Pre-Load Activities
      • Activation/Deactivation of Interfaces
      • Block Maintenance Transactions
      • Further Information
    • Real Load Activities
      • Load Tool
      • Post Processing
      • Completeness Check
    • Post Load Activities
      • Activation/Deactivation of Interfaces
      • Release Maintenance Transactions
  • Upgrade Preparation
    • Post Processing
    • Upgrade Prechecks

 

Stages

Read Me: This is the first Stage of CVI Cockpit. Users can get information about various pre-requisite OSS notes and help documentations, related to CVI migration processes.

Preparation: This is the second 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. This stage also gives a provision to customize the checks which user may intend to suppress in a test or sandbox system.

CVI Load: This is the third stage of CVI Cockpit. It has a total of 8 tasks divided into three sections – Pre-Load Activities, Real Load Activities, and Post Load Activities. These tasks perform the main synchronization activities that creates BP Masterdata in system, for all the customer and vendor records.

Upgrade Preparation: This is the fourth and currently the last Stage of CVI Cockpit. 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.

In context of Business Partner – CVI Synchronization, after successful completion of this step, typically user can proceed for system upgrade to S/4HANA.

 

Characteristics

The CVI Cockpit mainly comprises of three levels –

  • Overall CVI Cockpit
    • Four Stages under the cockpit
      • Individual Tasks under each Stage

The overall CVI Cockpit, all the Stages and their respective Tasks have a status associated to them.

All the Tasks of the CVI Cockpit requires manual maintenance of statuses. There are three statuses – Red, Green and Yellow. Upon the first launch of the CVI Cockpit, all the statuses are defaulted (greyed out).

Based on the status of the Tasks, the status of the corresponding Stage is automatically determined.

  • Stage status is Red, if one or more of its Tasks are set to red
  • Stage status is Green, only if all its Tasks are set to green
  • Stage status is Yellow, if one or more of its Tasks are set to yellow

Unlike the Tasks and Stages, the Overall CVI Cockpit can have only two valid statuses- Red and Green, indicating Ready and Not Ready respectively.

The overall CVI Cockpit status becomes Green (Ready), only upon meeting the BOTH the below conditions:

  • All the Stages are Green (confirmed)
  • There should be no un-synchronized customer or vendor records (to BP) in the system

At all other times, when neither or none of the above conditions are met, the overall CVI Cockpit Status stays Red.

Next StepsThis button will provide information on the activities after Customer/ Vendor to BP synchronization. It is only enabled when the overall CVI Cockpit status is Green and remains disabled, otherwise. 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.

 

Activities & Functions

The positioning of all the Stages and its related Tasks are already done in the intended logical sequence. For Stages, the sequence is Left to right. For Tasks, the sequence is Top to Bottom.

Across the CVI Cockpit stages, there are 2 types of Tasks – Executable and Non-executable. The non-executable Tasks are active both in Display and Edit Mode. User is expected to perform the following actions to operate through the cockpit stages.

Click on Edit to activate the Tasks.

Click on Execute button to launch individual Tasks.

Click on the Information button to know more about respective Tasks.

Click on the Status Lights to maintain the status of the task.

During execution of a Task, user is mandatorily required maintain a Task Status by selecting one of the below Status, along with comments.

User also needs to enter a mandatory comment in the Comment field. Last Executed By field indicates the last person who handled the Task.

Precaution: One can achieve Stage status as Green, even with task statuses 04 – ‘Skip Step (Project Decision)’ and 06 – ‘OK with Reservation’. In such cases, user is expected to ensure completion of the concerned task before proceeding to next stage, in order to attain system consistency.

Click on the Change Log button to get the change history of all the Tasks in the current stage.

Screen and Status controls

Users may require noting the below screen behaviors while making changes to the various tasks across the stages of CVI Cockpit.

Save Options

In the middle of a task, if user exits the CVI Cockpit program, then the task will not get automatically saved. User is required to press SAVE to persist the data. Also, multiple concurrent users executing the Cockpit simultaneously is not supported presently.

Backward Navigation

If user tries to edit a confirmed stage, system will reset the all the tasks of subsequent stages.

  1. The current stage (the one being modified) will retain all the task statuses, and the status of the current stage will be re-determined based on the modified task status.
  2. All subsequent stages and it tasks will reset.

Forward Navigation

If user wants to edit subsequent stages, the edit option for the stages will be available based on below actions-

  1. If all the task statuses of the current stage are set to Green, then edit option is enabled in the immediate next stage. Edit option does not activate in the further subsequent stages.
  2. If any task status of the current stage is not set to Green, then edit option is disabled in the immediate next stage and remains disabled in any subsequent stages thereafter as well.

Currently Out of Scope

The current version of CVI Cockpit specifically takes care of BP Synchronization for Customer and Vendor Master Data only. The following data sets are currently out of executable scope:

  1. Contact Person Objects
  2. HCM/Employee Objects
  3. CRM Integration Scenarios
  4. MDG Capabilities

Benefits:

Below are some of the advantages of the new CVI cockpit –

  • Gives a standard guidance with a Structured & Sequential application cockpit
  • Interactive Steps for the user to maintain activity status across phases
  • Provides a Flexible Sequence Control to navigate across stages as per synchronization stage
  • System based messaging for the Cockpit’s overall status, over a manually driven one
  • Users can also track the steps and change history via Status Logging under each stage
  • Provides a very user-friendly documentation, helping end-users operate the Cockpit

Summary:

This new development from SAP aims at enabling the ERP customer community to perform CVI Synchronization seamlessly and independently. The standard availability of the CVI Cockpit comes with SAP ECC EHP8 SP13 – SAP_APPL 618 release, however it would also be made available in the lower releases (until SAP_APPL 600), as well.

Although the given solution is primarily developed for ERP/ECC customers, a similar Cockpit is also planned to be made available in the SAP S/4HANA landscape. This would focus on the business customizing checks being performed in the reverse direction – BP to Customer/Supplier, alongside various consistency checks for the BPs in SAP S/4HANA.

Stay tuned and watch this space for more development updates.

Assigned tags

      23 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Amit Paithankar
      Amit Paithankar

      Hi Saptarshi,

      Regarding the transaction "CVI_COCKPIT" i do not find any documentation.

      We are currently performing the S/4Hana Migration to 1809, however the transaction does not exists in our ECC version.

      Our ECC version is ERP 6.0 EHP6.

      Can you share some more information please

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      Hi Amit,

       

      As mentioned above, the standard availability of CVI Cockpit is with the latest EHP8 SP13 – SAP_APPL 618 release.

      However, this would also be made available in the lower releases, including the ECC version you've mentioned, very shortly.

      Watch this space, for more updates! 🙂

       

      BR

      Saptarshi.

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      As  mentioned above, the CVI Cockpit would be made available for the lower ECC Releases as well (until SAP_APPL 600).  An OSS Note (valid for all lower ECC releases) for the same, will be released by end of November 2019.

      Author's profile photo Chirdeep Rastogi
      Chirdeep Rastogi

      Hi Saptarshi

      Please share the details on the OSS note for CVI Cockpit if the same has been released by end of Nov 2019 as you have suggested...

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      You can access the note - 2832085.

      https://launchpad.support.sap.com/#/notes/2832085

       

      BR

      Saptarshi.

       

      Author's profile photo SANDEEP JAIN
      SANDEEP JAIN

      Hi Saptarshi,

       

      Thanks for sharing the valuable info on CVI Cockpit.

       

      Regards,

      Sandeep Jain

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      Most welcome!

      Author's profile photo Jeroen Zijderveld
      Jeroen Zijderveld

      Hi Saptarshi,

       

      The automated customizing is very useful and convenient. However I experienced that is doesn't create transport request for the automatically created entries. Is that a known issue?

      regards,

      Jeroen

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      Hi Jeroen,

       

      Yes the issue is identified and acknowledged internally. This has now been fixed, and would be available with EHP8 SP14. The created entries would now prompt for a Transport Request, provided the report is run in a customizing client.

      Additionally, the CVI Customizing report is now revamped to have a new look and feel – improving on the usability aspects, with the original functionality intact. This would also be made available in the lower ERP releases until SAP_APPL 600.

       

      BR

      Saptarshi.

      Author's profile photo Chris Bowling
      Chris Bowling

      Hi Saptarshi,

       

      Thank you for the very useful information. When the overall cockpit status is red due to the "There should be no un-synchronized customer or vendor records (to BP) in the system" condition, what does this mean and how is it corrected?  Any information would be appreciated.  Thank you.

      Chris

      Author's profile photo Chris Bowling
      Chris Bowling

      As a follow up to my comment, I was confused about the overall status indicator.  I am trying to understand why all the options are greyed out in the cockpit and I mistakenly thought the status indicator meant the cockpit is ready to use.  I am not sure why I can't run the pre-check reports.  We are on ECC 6 EHP 8 stack 12 so we installed a bunch of notes to get the cockpit installed and it wasn't a straight forward process as we had to file an incidence with SAP to get the cockpit transaction to even work. We are not sure why all the pre-check reports are greyed out. Any insight would be appreciated. Thank you.

      Author's profile photo Chris Bowling
      Chris Bowling

      All I had to do was click on the pencil icon and the Execute options on the Prep tab all lit up.  Issue solved.

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      Hope your question/issue is answered.

       

      The CVI Cockpit aims at guiding the user through the sequenced steps of removing masterdata errors and ensure a complete synchronization of Customer/Vendor to Business Partners masterdata. Any feedback on the usability of the tool would be most welcome!

       

      Regards,

      Saptarshi.

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      This means, that in the system you still have Customer and Vendor records (KNA1, LFA1) which are not synchronized to a BP (via CVI Link tables). This would have been the case due to numerous factors (Masterdata/BP Semantic errors, CVI Customizing errors or Synchronization unattempted) due to which there are no BP’s created for the concerned C/V records. The CVI Cockpit accomplishes the same goal of ensuring synchronization of each and every C/V records.

      Author's profile photo Jeroen Zijderveld
      Jeroen Zijderveld

      Hi Saptarshi,

       

      The pre-check report reports customers that are created outside of the number range that belongs to their account group. Apparently that was possible somehow, in this case the customers were created by a DEBMAS interface.

      However this gives a problem when we want to have the BP's with the 'same number' functionality. Is there a way to create BP's outside their assigned number range? Other checks can be suppressed but can the check on number range be suppressed somehow?

      hope you can point me in the right direction.

      Jeroen

       

      Author's profile photo Michael Schliebner
      Michael Schliebner

      Dear Jeroen,

       

      Here for Vendors which might shade some light on numbering ranges:

      https://blogs.sap.com/2018/11/15/business-partner-configuration-in-s4hana/

       

      Best regards

      mitch

      Author's profile photo Klaus Bader
      Klaus Bader

      Great blog, great tool. Thanks!

      Unfortunately I ran into some dumps in the pre check of email addresses as the pre check can't handle several wrong email address in one customer  or its contacts (duplicate key error in the report). Is it a known issue?

      Why is there no check regarding consistency of title/sex. Happens actually quite often to find combinations like Mr. / female  or Mrs. / Male within the contacts.

       

      Thanks

      Cheers

      Klaus

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      Hi Claus,

       

      Thanks for your comments!

       

      I believe you're referring to a scenario expected to be checked under the Masterdata Check Report (MDC) tool as part of CVI Cockpit>Preparation stage.

      The checks in MDC are primarily based on the most important pain points faced by customers from C/V -> BP data model expectation. Based on further customer use cases the tool may be enhanced, once approved from the Product Management forums.

      You may check a detailed blog post on the MDC tool, and comment on possible improvement points here - https://blogs.sap.com/2019/07/22/business-partner-cvi-master-data-consistency-checks-supporting-the-sap-s4hana-move/

      BR

      Saptarshi.

      Author's profile photo Naveenkumar Duraisamy
      Naveenkumar Duraisamy

      Hi Saptarshi,

       

      I am getting dump while executing CVI_COCKPIT report. I have done implementation  of note 2832085. System is ECC 6.0 EHP6 SP8.kindly advice.

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      If your issue is unresolved, you may reach out to Product Support team for the respective application component via a ticket, they can assist you or route you to the concerned technical support team.

      Author's profile photo Chris Reyneke
      Chris Reyneke

      Hi Saptarshi.

       

      What a great article. I am a bit lost however as I have implemented Note 2832085 and I am running the CVI_COCKPIT but I cannot get past the "Read Me" tab. I have a big grey X on the tab and when I click on the EDIT button nothing happens.

      What am I missing here?

      Regards,

       

      Chris

      Author's profile photo Saptarshi Sen
      Saptarshi Sen
      Blog Post Author

      Thanks! The CVI Cockpit tabs are designed in intended sequence, and User needs to Click Edit, and  chronologically enter into each task (traffic lights icon) within a tab/stage, and set their status. Once all tasks in a given tab/stage are set as Green, the subsequent tab/stage becomes editable. May refer to the Application help documentation as well.

      Author's profile photo Ashwini Chaskar
      Ashwini Chaskar

      We have executed Master data consistency step in CVI_COCKPIT transaction.

      we have approximately 8lakhs customers and 50k vendors in our system.

      The execution for customer took a lot of time and now whenever we try to view the output it gives us dump SQL_CAUGHT_RABAX .

      dump%20when%20executed%20CVI_COCKPIT

      has anyone experienced this before?

       

      dump when executed CVI_COCKPIT