How To Fix /ACCGO/SPOT_CONT_MSG028 - DPQS not found for selected schedule

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/SPOT_CONT_MSG -

• Message number: 028

• Message text: DPQS not found for selected schedule

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 /ACCGO/SPOT_CONT_MSG028 - DPQS not found for selected schedule ?

  The SAP error message /ACCGO/SPOT_CONT_MSG028 DPQS not found for selected schedule typically occurs in the context of the SAP S/4HANA system, particularly when dealing with the Advanced Compliance Reporting (ACR) or similar functionalities. This error indicates that the system is unable to find a specific data package (DPQS) for the selected schedule, which can hinder processes like reporting or data extraction.
  Causes:
  
  Missing Data Package: The specified data package (DPQS) may not exist in the system for the selected schedule.
  Incorrect Configuration: There may be a configuration issue in the scheduling or data package setup.
  Authorization Issues: The user may not have the necessary authorizations to access the data package or schedule.
  System Errors: There could be underlying system issues or bugs that are causing the data package to be unavailable.
  
  Solutions:
  
  
  Check Data Package Configuration:
  
  Verify that the data package (DPQS) is correctly configured and exists in the system. You can do this by navigating to the relevant configuration settings in SAP.
  Ensure that the data package is assigned to the correct schedule.
  
  
  
  Review Schedule Settings:
  
  Check the settings of the selected schedule to ensure that it is correctly set up to reference the appropriate data package.
  Make sure that the schedule is active and not in a status that would prevent it from being executed.
  
  
  
  User Authorizations:
  
  Ensure that the user encountering the error has the necessary authorizations to access the data package and execute the schedule.
  You may need to consult with your SAP security team to verify and adjust user roles and permissions.
  
  
  
  System Logs and Notes:
  
  Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Look for SAP Notes related to this error message in the SAP Support Portal. There may be known issues or patches that address this specific error.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error, including the context in which it occurs and any relevant logs.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SE80 (Object Navigator), and SPRO (Customizing) to help diagnose and resolve the issue.
  Documentation: Review SAP documentation related to Advanced Compliance Reporting and data package management for additional insights and best practices.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.