How To Fix 28391 - New version of net compilation: &1 &2 &3 &4

SAP Error Message - Details

• Message type: E = Error

• Message class: 28 - Configuration

• Message number: 391

• Message text: New version of net compilation: &1 &2 &3 &4

What causes this issue?

The net compilation has changed. This message is generated to help you
locate problems in the net in case of new error messages.

System Response

The R/3 System writes an internal message to the application log, to
log the location of the error in the program, the index of the superior
node, and the net ID (KNNUM).

How to fix this error?

This message is written to the application log for information only, as
a tool for analyzing any error messages that are triggered by changes
to the constraint net or rule net compilation. No action is required.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 28391 - New version of net compilation: &1 &2 &3 &4 ?

  The SAP error message 28391, which states "New version of net compilation: &1 &2 &3 &4," typically relates to issues with the SAP NetWeaver Application Server, particularly in the context of ABAP or Java-based applications. This error can occur when there are inconsistencies or issues with the compiled objects in the system, often after a system upgrade, transport, or changes in the development environment.
  Cause:
  
  Inconsistent Object Versions: The error may arise when there are different versions of objects in the system, which can happen after transports or upgrades.
  Compilation Issues: If there are changes in the underlying code or dependencies that have not been properly compiled, this can lead to version mismatches.
  Transport Errors: If a transport request did not complete successfully, it may leave the system in an inconsistent state.
  System Upgrade: After an upgrade, some objects may need to be recompiled to align with the new version of the system.
  
  Solution:
  
  
  Recompile Objects: 
  
  Use transaction codes like SE80 (Object Navigator) or SE38 (ABAP Editor) to recompile the affected objects. You can also use the program RS_ABAP_SOURCE_SCAN to identify and recompile objects that need it.
  
  
  
  Check Transport Logs: 
  
  Review the transport logs to ensure that all objects were transported successfully without errors. If there are issues, you may need to re-transport the affected objects.
  
  
  
  Clear Buffer: 
  
  Clear the buffer using transaction code SM12 (for lock entries) and SM21 (for system logs) to ensure that there are no stale entries causing the issue.
  
  
  
  Check for Dependencies: 
  
  Ensure that all dependent objects are also up to date and compiled. Sometimes, a change in one object requires recompilation of others.
  
  
  
  System Restart: 
  
  In some cases, a restart of the application server may help clear temporary issues.
  
  
  
  Consult SAP Notes: 
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  SAP Notes: Always check for specific SAP Notes related to this error message, as they may provide tailored solutions or patches.
  System Logs: Use transaction SM21 to check system logs for any additional error messages that may provide context.
  Performance Monitoring: Use transaction ST22 to check for dumps that may be related to the error.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.