How To Fix 5C735 - Posting was created with value type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: 5C - HR: Messages for Switzerland

• Message number: 735

• Message text: Posting was created with value type &1

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 5C735 - Posting was created with value type &1 ?

  The SAP error message 5C735, which states "Posting was created with value type &1," typically occurs in the context of financial postings, particularly in the area of Asset Accounting (FI-AA) or General Ledger (FI-GL). This error indicates that there is a mismatch or inconsistency with the value type used in the posting.
  Cause:
  The error can be caused by several factors, including:
  
  
  Incorrect Value Type: The value type used in the posting does not match the expected value type for the transaction. This can happen if the configuration for the value types is not set up correctly.
  
  
  Posting Period Issues: The posting might be attempted in a period that is not open for the specific value type.
  
  
  Configuration Errors: There may be issues in the configuration of the financial document types or value types in the system.
  
  
  Data Entry Errors: Manual entries might have been made incorrectly, leading to the use of an inappropriate value type.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Value Type Configuration:
  
  Go to the configuration settings for value types in the SAP system (Transaction code: OAOA for Asset Accounting).
  Ensure that the value type used in the posting is correctly defined and allowed for the transaction type.
  
  
  
  Review Posting Period:
  
  Check if the posting period is open for the value type being used. You can do this in the transaction code OB52 (Maintain Posting Periods).
  
  
  
  Analyze the Document:
  
  Use transaction code FB03 to display the document that generated the error. Check the details of the posting and the value type used.
  
  
  
  Correct the Posting:
  
  If the posting was made incorrectly, you may need to reverse the document and create a new posting with the correct value type.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to value types and postings to ensure compliance with the expected configurations.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Value Types: In SAP, value types are used to differentiate between various types of financial transactions (e.g., acquisition, retirement, transfer).
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OAOA (for value type configuration), OB52 (for posting periods), and FB03 (for document display).
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to this error message.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary corrections to resolve it.