How To Fix 61147 - Explosion data has changed, please re-explode

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 147

• Message text: Explosion data has changed, please re-explode

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 61147 - Explosion data has changed, please re-explode ?

  The SAP error message 61147, "Explosion data has changed, please re-explode," typically occurs in the context of production planning and material requirements planning (MRP) when there are changes in the bill of materials (BOM) or routing that affect the explosion of components for a particular production order or planned order.
  Cause:
  
  
  Changes in BOM or Routing: The most common cause of this error is that the BOM or routing for the material has been modified after the initial explosion was performed. This could include changes in component quantities, addition or removal of components, or changes in the routing steps.
  
  
  Data Consistency Issues: Sometimes, inconsistencies in the data due to system updates or manual changes can trigger this error.
  
  
  Versioning: If there are multiple versions of a BOM or routing, and the system is referencing an outdated version, this can lead to the error.
  
  
  Solution:
  
  
  Re-Explosion: The primary solution is to re-explode the BOM. This can usually be done by navigating to the production order or planned order and selecting the option to re-explode the BOM. This will refresh the component list based on the latest BOM and routing data.
  
  
  Check for Changes: Review the BOM and routing for any recent changes. If changes were made, ensure that they are correct and that the latest version is being used.
  
  
  Consistency Check: Run a consistency check on the BOM and routing data to ensure there are no discrepancies. This can often be done through transaction codes like CS02 (Change BOM) or CS03 (Display BOM) to verify the details.
  
  
  Transaction Codes: Use transaction codes such as:
  
  CO02: Change Production Order
  CO03: Display Production Order
  MD04: Stock/Requirements List
  CS01/CS02/CS03: Create/Change/Display BOM
  
  
  
  System Logs: Check system logs for any additional error messages or warnings that might provide more context about the issue.
  
  
  User Authorization: Ensure that the user has the necessary authorizations to view and modify BOMs and production orders.
  
  
  Related Information:
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  
  
  Documentation: Review SAP documentation related to BOM management and production order processing for best practices and troubleshooting steps.
  
  
  Training: If this error occurs frequently, consider providing training for users on how to manage BOMs and production orders effectively to minimize changes that could lead to this error.
  
  
  By following these steps, you should be able to resolve the error message 61147 and ensure that your production planning processes run smoothly.