How To Fix ECATT_ODATA_TST028 - Error during metadata access: EntityType not found

SAP Error Message - Details

• Message type: E = Error

• Message class: ECATT_ODATA_TST - eCATT OData Testing - Messages

• Message number: 028

• Message text: Error during metadata access: EntityType not found

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 ECATT_ODATA_TST028 - Error during metadata access: EntityType not found ?

  The SAP error message ECATT_ODATA_TST028 indicates that there was an issue accessing the metadata of an OData service, specifically that the requested EntityType could not be found. This error typically occurs during automated testing with eCATT (extended Computer Aided Test Tool) when trying to access or validate an OData service.
  Causes:
  
  Incorrect EntityType Name: The name of the EntityType specified in the eCATT script may be incorrect or misspelled.
  Service Not Activated: The OData service may not be activated in the SAP Gateway or the corresponding backend system.
  Authorization Issues: The user executing the eCATT script may not have the necessary authorizations to access the OData service or its metadata.
  Service URL Issues: The URL used to access the OData service may be incorrect or not properly configured.
  Changes in the OData Model: If the OData model has been changed (e.g., entities added or removed), the eCATT script may be referencing an outdated EntityType.
  
  Solutions:
  
  Verify EntityType Name: Check the eCATT script for the correct spelling and casing of the EntityType. Ensure it matches the definition in the OData service.
  Activate the OData Service: Go to the SAP Gateway and ensure that the OData service is activated. You can do this using transaction code /IWFND/MAINT_SERVICE.
  Check Authorizations: Ensure that the user executing the eCATT script has the necessary authorizations to access the OData service. You may need to check roles and authorizations in transaction code PFCG.
  Validate Service URL: Confirm that the URL used in the eCATT script is correct and points to the right OData service endpoint.
  Update eCATT Script: If there have been changes to the OData model, update the eCATT script to reflect the current EntityType definitions.
  
  Related Information:
  
  OData Service Testing: You can test the OData service using tools like Postman or the SAP Gateway Client (transaction /IWFND/GW_CLIENT) to ensure that it is functioning correctly and returning the expected metadata.
  SAP Notes: Check for any relevant SAP Notes that might address known issues with OData services or eCATT.
  Debugging: If the issue persists, consider debugging the eCATT script to identify where the failure occurs and gather more context about the error.
  
  By following these steps, you should be able to diagnose and resolve the ECATT_ODATA_TST028 error effectively.