How To Fix CL_SADL_GW_MDE_MSGX035 - & is not integer

SAP Error Message - Details

• Message type: E = Error

• Message class: CL_SADL_GW_MDE_MSGX - texts for parser

• Message number: 035

• Message text: & is not integer

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 CL_SADL_GW_MDE_MSGX035 - & is not integer ?

  The SAP error message CL_SADL_GW_MDE_MSGX035 typically indicates that there is an issue with data type validation, specifically that a value expected to be an integer is not in the correct format. This error often arises in the context of SAP Gateway and SADL (SAP ABAP Programming Model for SAP Fiori) when dealing with OData services.
  Cause:
  
  
  Data Type Mismatch: The error usually occurs when a field that is expected to be an integer is receiving a value that cannot be converted to an integer. This could be due to:
  
  Non-numeric characters in the input.
  A decimal value being passed where an integer is expected.
  An empty or null value being passed.
  
  
  
  Incorrect Mapping: If the OData service is incorrectly mapped to the underlying data model, it may lead to this error.
  
  
  Client-Side Issues: If the client application (like a Fiori app) is sending incorrect data types in the request payload, it can trigger this error.
  
  
  Solution:
  
  
  Check Input Values: Ensure that the values being sent to the OData service are valid integers. This includes:
  
  Removing any non-numeric characters.
  Ensuring that no decimal points are included.
  Making sure that the value is not null or empty.
  
  
  
  Review OData Service: Check the OData service definition and ensure that the data types are correctly defined and mapped to the underlying data model.
  
  
  Debugging: Use transaction codes like /IWFND/ERROR_LOG to check for detailed error logs related to the OData service. This can provide more context on what is causing the error.
  
  
  Client-Side Validation: If applicable, implement client-side validation to ensure that only valid integer values are sent to the backend.
  
  
  Testing: After making changes, test the OData service with valid integer inputs to ensure that the error is resolved.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context.
  Documentation: Review the SAP documentation for SADL and OData services to understand the expected data types and structures.
  Community Forums: Engage with SAP community forums or support channels for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.