How To Fix /SAPAPO/CURTO_API035 - Version &2 for PDS &1, selection index &3, tables &4 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/CURTO_API -

• Message number: 035

• Message text: Version &2 for PDS &1, selection index &3, tables &4 does not exist

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 /SAPAPO/CURTO_API035 - Version &2 for PDS &1, selection index &3, tables &4 does not exist ?

  The SAP error message /SAPAPO/CURTO_API035 typically indicates an issue related to the Product Data Structure (PDS) in the Advanced Planning and Optimization (APO) module. This error suggests that the system is unable to find the specified tables associated with the PDS version you are trying to access.
  Cause:
  
  Missing or Inactive PDS: The PDS version specified in the error message may not exist in the system or may not be active.
  Data Consistency Issues: There may be inconsistencies in the database or issues with the data model that prevent the system from accessing the required tables.
  Incorrect Configuration: The configuration settings for the APO system may not be set up correctly, leading to the inability to retrieve the necessary data.
  Transport Issues: If the PDS was transported from another system, there may have been issues during the transport process that resulted in missing data.
  
  Solution:
  
  Check PDS Existence: Verify that the PDS version specified in the error message exists in the system. You can do this by navigating to the relevant transaction (e.g., /SAPAPO/PDS) and checking the PDS version.
  Activate PDS: If the PDS exists but is inactive, activate it. This can usually be done in the same transaction where you check for its existence.
  Data Consistency Check: Run consistency checks in the APO system to identify and resolve any data inconsistencies. You can use transaction /SAPAPO/TS to perform a consistency check.
  Review Configuration: Ensure that the configuration settings for the APO system are correct. This includes checking the settings for the PDS and related master data.
  Transport Logs: If the PDS was recently transported, check the transport logs for any errors or warnings that may indicate issues during the transport process.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for additional troubleshooting steps or patches that may be required.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/PDS, /SAPAPO/TS, and others that may help in managing PDS and troubleshooting issues.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal. There may be specific notes that address known issues or provide patches.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical team for further investigation.