How To Fix /SCDL/MSG_SRV036 - Error reading administrative data at item level

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCDL/MSG_SRV -

• Message number: 036

• Message text: Error reading administrative data at item level

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 /SCDL/MSG_SRV036 - Error reading administrative data at item level ?

  The SAP error message /SCDL/MSG_SRV036 indicates that there is an issue with reading administrative data at the item level in the context of SAP Supply Chain Management (SCM) or Advanced Planning and Optimization (APO). This error typically arises during processes that involve data retrieval or processing for specific items, such as during planning runs, data uploads, or when accessing certain reports.
  Causes:
  
  Data Inconsistency: There may be inconsistencies or missing data in the administrative tables related to the item in question.
  Authorization Issues: The user may not have the necessary authorizations to access the required data.
  Configuration Issues: Incorrect configuration settings in the system can lead to problems when trying to read item-level data.
  Technical Issues: There could be underlying technical issues, such as database connectivity problems or issues with the SAP application server.
  
  Solutions:
  
  
  Check Data Consistency:
  
  Use transaction codes like SLG1 to check for logs related to the error and identify any inconsistencies in the data.
  Verify that the administrative data for the item exists and is complete.
  
  
  
  Review Authorizations:
  
  Ensure that the user encountering the error has the necessary authorizations to access the relevant data. This can be checked in transaction SU53 or by consulting with your security team.
  
  
  
  Configuration Review:
  
  Review the configuration settings related to the SCM/APO module to ensure they are set up correctly. This may involve checking settings in transaction SPRO.
  
  
  
  Technical Troubleshooting:
  
  Check for any system messages or logs that might indicate a technical issue. This can include looking at the system logs in transaction SM21 or checking the application server logs.
  If the issue persists, consider reaching out to your SAP Basis team to investigate any potential database or server issues.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message. There may be patches or updates available that resolve known issues.
  
  
  
  Testing:
  
  If changes are made, ensure to test the process again to confirm that the error has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SU53 (Authorization Check), and SPRO (Customizing).
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Documentation: Review SAP documentation related to SCM/APO for best practices and troubleshooting steps.
  
  If the problem persists after trying the above solutions, it may be necessary to escalate the issue to SAP support for further assistance.