After running CVI synchronization - popup to confirm changes shows on the BP transaction - F2225

[Regys]

Hi Experts, 

we migrated some bank data to the BP with a certified external tool directly on the relevant DB tables (KNBK and LFBK) and when the CVI synchronisation job is run and the BP are synchronised on the BP bank details, it comes a pop-up when we run the BP transations, saying that the changes are not confirmed and must be confirmed in the FD08. Do you know what could be the issue here?

Lets say following scenario:

ECC:               

Customer:100 - with bank details in KNBK (partner bank type A001)

Suppler: 100 - with bank details in LFBK (partner bakn type B001)

In S4 after we did the migration in the DB tables of the BP generated (BP:100 in S4 with both customer and supplier role):

Before CVI synchronisation job:

BUT0BK had no bank details. Only the LFBK and the KNBK had the above ones.

After CVI synchronisation job:

BUT0BK has both bank details from the vendor and the customer (which is correct), but when we check in the LFBK and KNBK, this has overwritten the current ones. Meaning it has added on the KNBK also the partner bank type and the bank details of the vendor and the same with the LFBK. So it looks now like this:

BUT0BK:

1. Bank details of vendor - B001 (partner bank type)
2. Bank details of customer - A001 (partner bank type)

LFBK:

1. Bank details of vendor - B001 (partner bank type)
2. Bank details of customer - A001 (partner bank type)--- this one here is incorrect and was added after CVI synch job in S4.

KNBK:

1. Bank details of vendor - B001 (partner bank type) --- this one here is incorrect and was added after CVI synch job in S4.
2. Bank details of customer - A001 (partner bank type)

So now when we run the BP Transaction, it comes the following popup, that the change is not confirmed and needs to be confirmed in FD08. Do you have any suggestions what is happening here and how to get rid of this change request popup?

Thanks,

Regys

[RaymondGiuseppi · Accepted solution]

Look for

• OSS notes such as 3416866 - Messages "Changes ... have not yet been confirmed" incorrectly displyed at creation of sup... or 1238924 - Sensitive fields cannot be updated via BP synchronization 
• Check your Customizing for 'Sensitive Fields'

Consider using another tool to upload data as direct insert in LFBK and KNBK seems to be insufficient, as well as improper use.

• Which 'certified external tool' did you use?

[Regys · Accepted solution]

Hi Raymond, actually the issue was not on the migration tool, but in fact on the dual control principle and the customising that checks the changes on the customer and vendor, because they were identified as sensitive fields.

For anyone else that might have this topic in the future, this note helped. https://me.sap.com/notes/3018771/E