How To Fix SPXN128 - All external message types must belong to the same package

SAP Error Message - Details

• Message type: E = Error

• Message class: SPXN - Proxy Generation

• Message number: 128

• Message text: All external message types must belong to the same package

What causes this issue?

The assigned message types are based on an external WSDL description and
lie in different packages (&v1& and &v2&).

System Response

Object is inconsistent, because it may be impossible to generate a
unique schema description of the contract or contract implementation.

How to fix this error?

On the 'Objects' tab, all used message types and their packages are
displayed. Navigate to the message type and change the package via
menu->Goto->Object Directory Entry

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 SPXN128 - All external message types must belong to the same package ?

  The SAP error message SPXN128 indicates that there is an issue with the configuration of external message types in your SAP system. Specifically, this error occurs when the external message types defined in your system do not all belong to the same package. This is a requirement for certain configurations in SAP, particularly when dealing with external systems or interfaces.
  Cause:
  The primary cause of the SPXN128 error is that the external message types you are trying to use or configure are defined in different packages. In SAP, a package is a container for objects, and certain configurations require that all related objects (in this case, external message types) be grouped within the same package.
  Solution:
  To resolve the SPXN128 error, you can follow these steps:
  
  
  Identify the External Message Types: Determine which external message types are causing the issue. You can do this by checking the configuration settings where the error is being triggered.
  
  
  Check Package Assignments: For each of the external message types, check which package they belong to. You can do this by navigating to the relevant transaction (e.g., SE11 for Data Dictionary objects) and looking up the message types.
  
  
  Reassign Packages: If you find that the external message types are in different packages, you will need to reassign them to the same package. This can typically be done in the object’s properties or settings.
  
  
  Create a New Package (if necessary): If the existing packages do not align with your requirements, consider creating a new package that can house all the relevant external message types.
  
  
  Transport Requests: If you are working in a development environment, ensure that any changes you make are included in a transport request so that they can be moved to other environments (e.g., testing, production).
  
  
  Testing: After making the necessary changes, test the configuration to ensure that the error no longer occurs and that the external message types function as expected.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SE37 (Function Module) to manage and check the configurations.
  Documentation: Refer to SAP documentation or help resources for more detailed guidance on managing external message types and packages.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error message.
  
  By following these steps, you should be able to resolve the SPXN128 error and ensure that all external message types are correctly configured within the same package.