How To Fix /IWFND/CM_MGW_RT135 - Complex type property '&1' references to disabled complex type '&2'

SAP Error Message - Details

• Message type: E = Error

• Message class: /IWFND/CM_MGW_RT -

• Message number: 135

• Message text: Complex type property '&1' references to disabled complex type '&2'

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 /IWFND/CM_MGW_RT135 - Complex type property '&1' references to disabled complex type '&2' ?

  The SAP error message /IWFND/CM_MGW_RT135 indicates that there is an issue with the definition of complex types in your OData service. Specifically, it means that a complex type property is referencing another complex type that has been disabled or is not properly defined in the service.
  Cause:
  
  Disabled Complex Type: The complex type that is being referenced (&2) has been marked as disabled in the service definition. This can happen if the complex type was removed or not activated properly.
  Model Definition Issues: There may be inconsistencies or errors in the data model definition, such as missing or incorrectly defined complex types.
  Service Activation: The OData service may not have been activated correctly after changes were made to the data model.
  
  Solution:
  
  
  Check Complex Type Definitions:
  
  Go to the SAP Gateway Service Builder (transaction code SEGW).
  Locate the service and check the definition of the complex types involved.
  Ensure that the complex type &2 is defined and activated.
  
  
  
  Activate the Complex Type:
  
  If the complex type is disabled, you can enable it by right-clicking on the complex type in the Service Builder and selecting the option to activate it.
  
  
  
  Rebuild the Service:
  
  After making changes, ensure to regenerate the runtime artifacts by right-clicking on the service and selecting "Generate Runtime Objects".
  
  
  
  Check Service Registration:
  
  Ensure that the OData service is properly registered in the SAP Gateway (transaction code /IWFND/MAINT_SERVICE).
  If necessary, re-register the service.
  
  
  
  Test the Service:
  
  After making the necessary changes, test the OData service to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SEGW: Service Builder for OData services.
  /IWFND/MAINT_SERVICE: Maintenance of OData services.
  
  
  Documentation: Refer to SAP Help documentation for OData services and complex types for more detailed information on how to define and manage them.
  Debugging: If the issue persists, consider using the SAP Gateway error log (transaction code /IWFND/ERROR_LOG) to get more insights into the error.
  
  By following these steps, you should be able to resolve the error message /IWFND/CM_MGW_RT135 and ensure that your OData service functions correctly.