How To Fix CX800 - Limited explosion not possible - &1/&2 is still saved in the old tables

SAP Error Message - Details

• Message type: E = Error

• Message class: CX - Nachrichten für Konfigurationsprozess

• Message number: 800

• Message text: Limited explosion not possible - &1/&2 is still saved in the old tables

What causes this issue?

You want to process an order BOM in a function that requires a complete
BOM explosion.
Since the sales order item is still stored in the old configuration
tables (INOB, KSSK, and AUSP) a complete BOM explosion must be
executed.
If the BOM is not exploded completely, only the exploded assemblies are
copied to the new storage table (CBASE), and the data in the old tables
is deleted.
This means that any assemblies that are not exploded will be lost.

System Response

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

How to fix this error?

First explode the BOM fully, and save the result. When you save, the
sales order item will be copied to the CBase, so that a limited
explosion is possible the next time you process the order BOM.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CX800 - Limited explosion not possible - &1/&2 is still saved in the old tables ?

  The SAP error message "CX800 Limited explosion not possible - &1/&2 is still saved in the old tables" typically occurs in the context of the SAP system's handling of master data, particularly when dealing with the Bill of Materials (BOM) or similar structures. This error indicates that there is an inconsistency in the data, specifically that the system is trying to perform an operation (like a BOM explosion) on a material or assembly that is still linked to old data structures or tables.
  Cause:
  
  Data Migration Issues: The error often arises after a data migration or upgrade where some records have not been fully updated to the new structure.
  Inconsistent Data: The material or assembly in question may still reference old BOMs or routing data that have not been migrated or updated.
  Master Data Changes: Changes in the master data (like material master or BOM) that have not been fully propagated or updated in all relevant tables.
  
  Solution:
  
  Check Data Consistency: Use transaction codes like CS15 (BOM explosion) or CS03 (Display BOM) to check if the BOM or material is correctly set up and does not reference old data.
  Recreate BOM: If the BOM is found to be inconsistent, consider recreating it to ensure it is linked to the correct tables and structures.
  Data Migration Tools: If this error occurred after a migration, use SAP's data migration tools or programs to ensure all data is correctly updated.
  Check for Old Entries: Use transaction SE16 or SE11 to check the relevant tables (like STPO, STPOB, etc.) for any old entries that may still exist and need to be cleaned up.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  System Refresh: In some cases, a system refresh or reorganization of the database may be necessary to clear out old data.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CS01 (Create BOM), CS02 (Change BOM), and CS03 (Display BOM) for managing BOMs.
  SAP Documentation: Review SAP documentation related to BOM management and data consistency checks.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.