How To Fix SRT_WSP542 - Global property &1 (&2): Value (group &3) deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_WSP - Messages for SRT WSP

• Message number: 542

• Message text: Global property &1 (&2): Value (group &3) deleted

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 SRT_WSP542 - Global property &1 (&2): Value (group &3) deleted ?

  The SAP error message SRT_WSP542 indicates that a global property value has been deleted in the context of SAP's web service framework. This error typically arises in scenarios involving web service communication, particularly when using the SAP Process Integration (PI) or SAP Process Orchestration (PO) systems.
  Cause:
  The error message "Global property &1 (&2): Value (group &3) deleted" suggests that:
  
  A global property that was previously defined is no longer available or has been deleted.
  The system is trying to access a property value that has been removed, which can happen due to changes in configuration or updates in the web service definitions.
  It may also occur if there are inconsistencies in the configuration or if the web service consumer is trying to access a property that has not been properly set up.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Global Properties: 
  
  Navigate to the relevant configuration in the SAP system where global properties are defined (e.g., in the Integration Directory or the relevant web service configuration).
  Verify if the global property mentioned in the error message still exists and is correctly configured.
  
  
  
  Recreate or Restore Deleted Properties:
  
  If the property has been deleted, you may need to recreate it or restore it from a backup if available.
  Ensure that the property values are correctly assigned to the relevant groups.
  
  
  
  Review Web Service Configuration:
  
  Check the web service configuration to ensure that all required properties are defined and correctly referenced.
  Make sure that the web service consumer is using the correct endpoint and that the service definitions are up to date.
  
  
  
  Check for Changes in the System:
  
  If there have been recent changes to the system (e.g., upgrades, migrations, or configuration changes), review those changes to identify any potential impacts on global properties.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version of SAP you are using for any known issues or additional troubleshooting steps.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, providing them with the error details and any relevant logs.
  
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to the specific error message or the components you are using (e.g., SAP PI/PO).
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SOAMANAGER for web service management and SXMB_MONI for monitoring messages in PI.
  Logs and Traces: Review application logs and traces for additional context around the error, which can help in diagnosing the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.