This is Sherry from SAP Technical Support Team, in this blog series, I will share common issues and essential documentation related to the migration from ECC to S/4HANA, organized by topic. If you are currently upgrading ECC to S/4HANA and encounter any CVI-related issues, please feel free to contact me via Teams/Email and provide your case number. My email is sherry.wang01@sap.com.

Useful blog for MDS_LOAD_COCKPIT

https://blogs.sap.com/2016/11/18/how-to-use-mds_load_cockpit/

Enhancements to MDS_LOAD_COCKPIT – ECC EHP8 SP15

Please note that even if the customer/vendor data has already been synchronized to the Business Partner (BP), you can still execute MDS_LOAD_COCKPIT. We typically use this transaction code to analyze any issues encountered during the synchronization process.

3401603 Error using transaction MDS_LOAD_COCKPIT – No documentation available – Message no. SH720

3027262 – Documentation added to Synchronization Cockpit(MDS_LOAD_COCKPIT)

SPRO -> Cross-Application Components -> General Application Functions -> Postprocessing Office -> Business Processes -> Activate Creation of Postprocessing Orders Business Process CVI_01 Customer -> Business partner CVI_02 Vendor -> Business partner CVI_03 Business partner -> Customer CVI_04 Business partner -> Vendor
IMG -> Cross-Application Components -> Master Data Synchronization -> Synchronization Control → Synchronization Control -> Activate Synchronization Options	In hana system, Please deactivate synchronization directions Customer ->BP and Vendor ->BP direction see KBA 3300946
3346373 MDS_LOAD_COCKPIT triggers reverse synchronization	Symptom MDS_LOAD_COCKPIT is being used to synchronize data between Customer/Vendor and Business Partner. However, after executing, for example, synchronization from Customer to BP, system also executes BP to Customer.

3627356 Datasets are not shown for transaction code MDS_LOAD_COCKPIT

3524020 – MDS_LOAD_COCKPIT: Synchronization does not happen for several reasons related to datasets

3485475 – Enabling dataset level synchronization in MDS_LOAD_COCKPIT – Prerequisite Note for 3362595
3362595 – Enabling dataset level synchronization in MDS_LOAD_COCKPIT

3133069 – Simplification of Customizing synchronization option in MDS_LOAD_COCKPIT transaction

block size

Block Size for Mass Synchronization
The block size specifies the number of source objects contained in a data package.
Use
You can use the block size to define the size of the data packages. By default, the number of source objects is set to 50. You can change this value if necessary. However, we recommend that you do not choose a value greater than 100.

No of customers/vendors + additional contact persons

Background processing

2995924 Batch job for MDS_LOAD_COCKPIT

2448409 Background Processing in MDS_LOAD_COCKPIT does not work

Customer Example for block size and number of processes: Synchronization (after master data cleansing
and solving configuration issues) with 14 Mio. Customer. A block size of 50.000 in combination with 60
dialog tasks for CVI has proved to be a good size in order to optimize the usage of available processes.
• IMPORTANT: Queue processing (Checkbox Background Processing is activated) triggers dialog tasks and
not batch jobs.

Test run

3411430 Option Test Run can't be selected in MDS_LOAD_COCKPIT

2785172 – Simulation functionality in Business Partner 2785172 – Simulation functionality in Business Partner

2647788 – Simulation functionality in Business Partner

On the Processing tab of Synchronization Cockpit, you find the checkbox ‘Test Run’ which is greyed in
standard. You can enable the test run functionality by implementing SAP Note 2874184 – Information on test
run behaviour..
When the test run mode is set from Customer to Business partner or from Vendor to Business partner,
transaction MDS_PPO2 will show the logs, but the Business Partner will not be committed to databases.

2874184 – Information on test run behaviour.

2804399 – Synchronization to BP fails post test run execution.

3493426 Dump occurs when using MDS_LOAD_COCKPIT to synchronize customer/vendor to BP in test mode

Server Group

3024796 – MDS_LOAD_COCKPIT: Parameter Server Group replaced with Int. RFC Dest.

1490298 – Introducing Server Group option for txn MDS_LOAD_COCKPIT.

Max Processes

No. of dialog tasks
For Max. Processes, the Max. Processes field specifies the number of data blocks processed in parallel by the system during synchronization. It is used in conjunction with background processing and the Queue Name field. The value in the Max. Processes field should not be greater than the number of batch processes defined in the system. t-code RZ11 Parameter rdisp/wp_no_btc can be used to check the batch processes
Number of Parallel Processes The Max. Processes field specifies the number of data blocks processed in parallel by the system during synchronization. Use The Max. Processes field is used in conjunction with background processing and the Queue Name field. Dependencies The value in the Max. Processes field should not be greater than the number of batch processes defined in the system. We recommend that you use the default value.
Performance MDS_LOAD_COCKPIT: creating a single Business Partner consumes reasonable time. Although SAP has improved the performance of it the full load could exceed given times for synchronization. MDS_LOAD_COCKPIT provides the option to run the synchronization in parallel processes. It is highly recommended to use this option. Based on some experiences the database performance isn’t the bottleneck. So more than 10 processes in parallel do not slow down DB performance. Usually, the number ranges used by BP are not buffered in SAP-Standard. Each single process generated a new number from NRIV. This could lead, e.g when using massive parallel processing, to parallel locks on the number ranges. This can be prevented when using buffering for number ranges. https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H.0781%20SAP%20S4HANA%20Cookbook%20Customer%20Vendor%20Integration.pdf

Synchronization Scope

3257138 You notice the wrong text in MDS_LOAD_COCKPIT for vendor contacts

3411942 Incorrect text for Synchronization Scope – Vendor

Excel

2600528 100 entries from excel upload are used in MDS_LOAD_COCKPIT

2903696 Excel upload option in MDS_LOAD_COCKPIT has upper limit

2399368 – Excel upload option in MDS_LOAD_COCKPIT

2913255 – MDS_LOAD_COCKPIT Selection screen improvement: Excel template download

2955619 – MDS_LOAD_COCKPIT excel upload rows count

selection screen

2643749 Material Group single load is not working with Synchronization Cockpit

3028123 Selection screen disappeared in MDS_LOAD_COCKPIT

3791734 Multiple selection icon missing in MDS_LOAD_COCKPIT – SAP ERP & SAP S/4HANA

2907519 – Master Data Synchronisation Tool Revamp

2954330 – Performance Improvement of Monitor Tab in MDS_LOAD_COCKPIT

2958046 – CVI : MDS_LOAD_COCKPIT does not display Logs of a specific date

3118605 – All errors not displayed in MDS_LOAD_COCKPIT

877061 – Synchronization cockpit: Integrating the application log

3070976 – MDS_LOAD_COCKPIT – Warning status if no records are synchronized

3384482 BP synchronization is not happening without error or with error MDS_LOAD 047 – SAP ERP & SAP S/4HANA

3120605 – Incorrect error shown in MDS_PPO2

3652238 MDS_LOAD_COCKPIT only works in English language

3081101 – Update field help for Synchronization Cockpit

Other functionality

3072409 – Simplified Handling of Records Marked for Deletion -Enhancements to MDS Load Cockpit (MDS_LOAD_COCKPIT)

2506262 – Suppression of Change Pointers while CVI synchronization via MDS_LOAD_COCKPIT
3458173 – Change Documents were not suppressed post following SAP Note 2506262

Source link

Useful document collection for MDS_LOAD_COCKPIT

Useful blog for MDS_LOAD_COCKPIT

Other functionality

Leave a Reply Cancel reply

Categories

Recent Posts

Services

Company

Support

Useful document collection for MDS_LOAD_COCKPIT

Useful blog for MDS_LOAD_COCKPIT

Other functionality

Leave a Reply Cancel reply

Categories

Recent Posts

Related Posts

Self-Service Audit Log Retrieval for SAP Signavio Is Now Available: Faster, Consistent and Secure

New Guided Missions for SAP Partners: Build Once. Scale to Many.

From 7 Seconds to 2: How We Broke the Silence in Our AI Voice Agent

Screen Personas in CE2608: Smarter Flavor Management and Option to Define Custom Industrial Devices