How To Fix WG150 - Migration of condition change pointers has not yet taken place

SAP Error Message - Details

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 150

• Message text: Migration of condition change pointers has not yet taken place

What causes this issue?

Migration of the condition change pointers has not yet begun or is not
yet fully completed.
Investment Buying can only be performed after the data migration has
been completed.

System Response

INCLUDE ISR_STOP

How to fix this error?

Start the Investment Buying run once migration has been completed.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WG150 - Migration of condition change pointers has not yet taken place ?

  Certainly! Here's a detailed explanation regarding the SAP error message WG150 - Migration of condition change pointers has not yet taken place:
  
  SAP Error Message: WG150
  Text: Migration of condition change pointers has not yet taken place
  
  Cause
  This error occurs when the system expects that the migration of condition change pointers (from the old pricing procedure change pointer mechanism to the new one) has been completed, but it has not been done yet.
  
  In SAP, condition change pointers are used to track changes in pricing conditions for billing and sales documents.
  With newer SAP releases (especially from SAP ERP 6.0 EhP4 onwards), the mechanism for condition change pointers was enhanced.
  Before using certain functions or reports related to condition change pointers, the system requires that the migration of old condition change pointers to the new format be completed.
  If this migration has not been performed, the system throws the WG150 error.
  
  
  When does this happen?
  
  When you try to run billing or pricing reports that rely on condition change pointers.
  When you execute transaction VK13 or related condition pointer transactions.
  During billing document creation or pricing procedures that check for condition changes.
  After system upgrade or support package installation where the condition change pointer mechanism was updated.
  
  
  Solution
  Step 1: Check if migration has been done
  
  The migration program for condition change pointers is RVKRED00.
  This program migrates old condition change pointers stored in table KOMP to the new tables like KONV and others.
  
  Step 2: Run the migration program
  
  Execute transaction SE38 or SA38.
  Run program RVKRED00.
  This program will migrate the old condition change pointers to the new format.
  
  Step 3: Verify migration
  
  After running the migration, try to reproduce the scenario that caused the error.
  The error WG150 should no longer appear.
  
  Important Notes:
  
  Always perform this migration in a test or development system first.
  Make sure to have a backup before running the migration.
  The migration should be done only once.
  If the system is already in productive use, coordinate with your SAP Basis and functional team before running the migration.
  
  
  Related Information
  
  SAP Note: Check for SAP Notes related to condition change pointer migration for your specific SAP version.
  Tables involved:
  
  Old condition change pointers: KOMP
  New condition change pointers: KONV, KONP
  
  
  Transactions related to condition change pointers:
  
  VK13 - Display Condition Records
  VK12 - Change Condition Records
  VK11 - Create Condition Records
  
  
  Pricing and billing documents rely on condition change pointers to detect changes in pricing conditions.
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Migration of old condition change pointers not done yet.
  
  
  Solution
  Run migration program RVKRED00 to migrate old pointers to new format.
  
  
  When it occurs
  During pricing, billing, or condition pointer related processing after system upgrade or support package.
  
  
  Related transactions
  SE38, SA38, VK13, VK12, VK11
  
  
  Precautions
  Backup system, test migration in non-production system first.
  
  
  
  
  If you need further assistance or step-by-step guidance on running the migration program, feel free to ask!