How To Fix CNV_20900188 - Participating vendors have different Posting block (LFB1-SPERR)

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20900 - Message class for package CNV_20900

• Message number: 188

• Message text: Participating vendors have different Posting block (LFB1-SPERR)

Diagnosis
According to the mapping, you want to merge two or more old vendor
records into one target vendor record. However, not all the old records
have identical master data settings: It was found that old vendor
records have different Posting block for company code. (This setting is
determined by the indicator 'Posting block for company code',<ZH>
</>field <ZH>LFB1-SPERR)</>.
This may lead to inconsistencies in some applications related to target
vendor data.
System Response
<ZH>Error</>
From a technical perspective, this message can be ignored. This may make
sense in the following cases:
No postings to the respective vendor records have been made.
The respective vendor records are not used any longer and are meant to
be merged into a dummy record.
Procedure
Analyze the situation, and either change the mapping so that only vendor
records with identical master data settings are merged or decide to
ignore the message because one of the special cases described above
applies.
If you decide to ignore the error even though none of the special cases
described above applies, consider that <ZH>the target vendor record will
get the Posting block for company code of the old vendor record for
which the priority indicator is set.</> Make sure to evaluate the impact
of this decision - for example regarding potential inconsistencies and
required follow-up activities - <ZH>before</> you continue with the
conversion.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20900188 - Participating vendors have different Posting block (LFB1-SPERR) ?

  The SAP error message CNV_20900188 indicates that there is a discrepancy in the posting block settings for participating vendors in the system. Specifically, the error arises when the vendors involved in a transaction have different posting block statuses, which can prevent the transaction from being processed correctly.
  Cause:
  The error is typically caused by the following factors:
  
  Different Posting Block Settings: The participating vendors have different values in the LFB1-SPERR field, which indicates their posting block status. This can happen if one vendor is blocked for posting while the other is not.
  Data Migration Issues: If you are migrating data from one system to another (e.g., during an SAP S/4HANA migration), inconsistencies in vendor master data can lead to this error.
  Manual Changes: Changes made to vendor master data after the initial setup can lead to discrepancies.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Vendor Master Data:
  
  Go to the vendor master data (transaction code XK03 or MK03).
  Check the LFB1 table for the SPERR field for each participating vendor.
  Ensure that the posting block status is consistent across all vendors involved in the transaction.
  
  
  
  Update Posting Block Status:
  
  If you find that one of the vendors has a posting block that is not required, you can change the posting block status using transaction code XK02 or MK02.
  Make sure to communicate with relevant stakeholders before making changes to vendor statuses.
  
  
  
  Data Migration Review:
  
  If this error occurred during a data migration process, review the migration mapping and ensure that the vendor master data is consistent.
  You may need to adjust the migration scripts or processes to ensure that posting block statuses are aligned.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific recommendations or patches that may address the issue.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the error no longer occurs and that transactions can be processed as expected.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  XK03 - Display Vendor
  XK02 - Change Vendor
  MK03 - Display Vendor (Purchasing)
  MK02 - Change Vendor (Purchasing)
  
  
  
  Tables:
  
  LFB1 - Vendor Master (Company Code)
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.