cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Customer-specific data were not saved due to error CVI_MAPPING 042 (see long text!)

abulhasnat
Participant
0 Likes
3,346

 

Hello Team,

Can anyone tell us how we could resolve this issue? When we are trying to extend a new company code through FLCU00 in BP Role, the system is prohibiting the entry and showing the below message. 

 

abulhasnat_0-1739788466007.png

 

 

Customer-specific data were not saved due to error CVI_MAPPING 042 (see long text!)

Message no. CVI_BDT_ADAPTER050

 

Diagnosis

While saving the customer-specific data of the business partner the following error occurred:

Customer VD44 already exists
CVI_MAPPING 042

The business partner was created/changed, the corresponding customer was not created/changed.

Background

In your system, the so-called post processing office (PPO) is active. The update of the customer-specific data is delayed (occurs technically "on commit"), while all non-customer-specific business partner data are updated directly after pressing the save button. Due to technical reasons a "normal" error message is not possible any more during "COMMIT WORK" processing. Because of this errors that occur during processing of customer-specific data are saved in PPO and the corresponding customer-specific database tables are not updated. This leads to the situation that pure customer-specific fields in transaction BP are empty after saving, although they had been filled with values before pressing the save button.

System Response

Certain customer-specific fields in transaction BP are empty after saving, although they had been filled with values before.

Procedure

Correct your entries according to the error message mentioned above (also available in the message short text in brackets) and save the business partner again. If needed contact your system administrator.

Procedure for System Administration

You can get further details related to the error directly in PPO. For accessing PPO start transaction MDS_PPO2 and enter the corresponding date on which the error occurred in field "Technical Creation Date". The concerned business partner should then be available in the result list.

Thank you
Hasnat

Accepted Solutions (1)

Accepted Solutions (1)

abulhasnat
Participant
0 Likes

Hi All,

The possible case would be the BP number range is maintained externally, and if you are trying to upload a customer with your customized template, then you need to see the program for custom upload. In our case, if we create a customer through BP, then we do not find any issue; however, if we are trying it with the customer upload program, then the roles FLCU00 and FLCU01 internal BP codes were not updated. 

Thank You
Hasnat

 

Answers (0)