How To Fix CNV_20900182 - Participating vendors have different Purchasing block (LFA1-SPERM)

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20900 - Message class for package CNV_20900

• Message number: 182

• Message text: Participating vendors have different Purchasing block (LFA1-SPERM)

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 Centrally imposed purchasing block.(This setting
is determined by the indicator <ZH>'Centrally imposed purchasing block',
</>field <ZH>LFA1-SPERM</>).
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 Centrally imposed purchasing block setting 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_20900182 - Participating vendors have different Purchasing block (LFA1-SPERM) ?

  The SAP error message CNV_20900182 indicates that there is a discrepancy in the purchasing block status of participating vendors in a data migration or conversion process. Specifically, the error arises when the vendors involved have different settings for the purchasing block field (LFA1-SPERM) in the vendor master data.
  Cause:
  The purchasing block (LFA1-SPERM) is a field in the vendor master data that indicates whether a vendor is blocked for purchasing activities. If you are trying to migrate or convert vendor data and the participating vendors have different purchasing block statuses (e.g., one vendor is blocked while another is not), this error will occur.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Vendor Master Data:
  
  Review the vendor master data for the participating vendors. You can do this by using transaction code SE16N or MK03 to view the vendor details.
  Look specifically at the Purchasing Block field (LFA1-SPERM) for each vendor.
  
  
  
  Standardize Purchasing Block Status:
  
  If the vendors are supposed to have the same purchasing block status, update the vendor master records to ensure consistency. You can change the purchasing block status using transaction code MK02.
  If the vendors should have different statuses, you may need to adjust your migration logic to handle these differences appropriately.
  
  
  
  Data Migration Logic:
  
  If you are using a data migration tool (like SAP S/4HANA Migration Cockpit or LSMW), ensure that your mapping and transformation rules account for the purchasing block status.
  You may need to implement logic to handle cases where vendors have different purchasing block statuses.
  
  
  
  Consult Documentation:
  
  Review any relevant SAP documentation or notes related to the migration process you are using. There may be specific guidelines or best practices for handling vendor data.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test migration to ensure that the error is resolved and that the data is migrated correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  MK03: Display Vendor Master
  MK02: Change Vendor Master
  SE16N: Data Browser for table access
  
  
  Tables:
  
  LFA1: Vendor Master (General Data)
  
  
  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 resolve the CNV_20900182 error and successfully complete your data migration or conversion process.