How To Fix 68167 - Document reversal under $/$; New posting under $/$

SAP Error Message - Details

• Message type: E = Error

• Message class: 68 - Message for DARWIN Loans (continued)

• Message number: 167

• Message text: Document reversal under $/$; New posting under $/$

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 68167 - Document reversal under $/$; New posting under $/$ ?

  The SAP error message 68167, which states "Document reversal under $/$; New posting under $/$," typically occurs in the context of financial document processing, particularly when dealing with document reversals and postings in the SAP system. This error can arise due to various reasons, and understanding the cause and potential solutions is essential for resolving it.
  Cause:
  
  
  Document Type Restrictions: The error often indicates that the document type being used for reversal or posting does not allow for the operation you are trying to perform. This can happen if the document type is configured in a way that restricts reversals or new postings.
  
  
  Posting Period Issues: If the posting period is closed or not open for the document type you are trying to reverse or post, this error may occur.
  
  
  Incorrect Configuration: The configuration settings for the document types in the Financial Accounting (FI) module may not be set up correctly, leading to restrictions on certain operations.
  
  
  Transaction Code Issues: The transaction code being used may not be appropriate for the type of document or operation you are trying to perform.
  
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for document types in the SAP system (Transaction Code: OBA7).
  Ensure that the document type you are using allows for reversals and new postings.
  
  
  
  Verify Posting Period:
  
  Check if the posting period is open for the document type you are trying to reverse or post. You can do this in the transaction code OB52.
  If the period is closed, you may need to open it or use a different document type that is allowed for the current period.
  
  
  
  Use Correct Transaction Codes:
  
  Ensure that you are using the correct transaction codes for the operations you are trying to perform. For example, use FB08 for document reversal and FB50 for general ledger postings.
  
  
  
  Consult with SAP Support:
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues related to this error message.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error message. SAP frequently releases updates that may address known issues.
  Documentation: Review the SAP documentation for Financial Accounting to understand the configuration and operational guidelines for document types and postings.
  User Forums: Engage with SAP user forums or communities where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.