How To Fix 32035 - Maintain the record version tables for record type & and date &

SAP Error Message - Details

• Message type: E = Error

• Message class: 32 - HR: Public Sector Austria

• Message number: 035

• Message text: Maintain the record version tables for record type & and date &

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 32035 - Maintain the record version tables for record type & and date & ?

  The SAP error message 32035, which states "Maintain the record version tables for record type & and date &," typically occurs in the context of managing record versions in SAP systems, particularly in modules related to document management or data archiving.
  Cause:
  This error usually arises when the system is unable to find the necessary versioning information for a specific record type and date. This can happen due to several reasons:
  
  Missing Entries: The required entries for the specified record type and date are not maintained in the version tables.
  Data Inconsistency: There may be inconsistencies in the data that prevent the system from retrieving the correct version information.
  Configuration Issues: The configuration settings for record versioning may not be properly set up in the system.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Version Tables:
  
  Go to the transaction code related to maintaining record version tables (e.g., SARA for archiving or SCDO for document management).
  Verify if the entries for the specified record type and date exist. If not, you may need to create or update them.
  
  
  
  Maintain Record Types:
  
  Ensure that the record types are correctly defined in the system. You can check this in the customizing settings under the relevant module (e.g., document management, archiving).
  
  
  
  Data Consistency Check:
  
  Run consistency checks to identify any discrepancies in the data. This can often be done through specific transaction codes or reports designed for data integrity checks.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific module you are working with. There may be specific instructions or patches available that address this 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 the error message details and any relevant context to help them diagnose the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration), SCDO (Document Management), or others specific to your SAP module.
  SAP Notes: Search for SAP Notes related to error 32035 in the SAP Support Portal. There may be specific fixes or recommendations available.
  User Forums: Check SAP community forums or other user groups for discussions related to this error. Other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.