How To Fix >0682 - Posting date/document date changed to &1/&2 internally

SAP Error Message - Details

• Message type: E = Error

• Message class: >0 - General Basis texts

• Message number: 682

• Message text: Posting date/document date changed to &1/&2 internally

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 >0682 - Posting date/document date changed to &1/&2 internally ?

  The SAP error message 0682 ("Posting date/document date changed to &1/&2 internally") typically occurs when there is a discrepancy between the posting date and the document date in a financial transaction. This message indicates that SAP has automatically adjusted the posting date and/or document date to comply with certain rules or settings in the system.
  Cause:
  
  Date Validation Rules: SAP has built-in validation rules that may prevent certain dates from being used. For example, if the posting date is outside of an open fiscal period or if it falls on a weekend or holiday, SAP may adjust it.
  Document Type Settings: Certain document types may have specific date-related settings that enforce date changes.
  User Authorizations: Users may not have the necessary authorizations to post with the original dates, leading to automatic adjustments.
  Configuration Settings: The system configuration may dictate that certain dates must be adjusted based on business rules or compliance requirements.
  
  Solution:
  
  Check Date Settings: Review the posting date and document date to ensure they are within the allowed range for the fiscal period. Make sure that the dates are valid and do not fall on non-working days.
  Review Document Type Configuration: Check the configuration of the document type being used to see if there are any restrictions or settings that might cause the date to be changed.
  User Authorizations: Ensure that the user has the necessary authorizations to post with the specified dates. If not, consider adjusting the user's roles or permissions.
  Consult with Finance Team: If the dates are being changed due to compliance or business rules, consult with the finance or accounting team to understand the requirements and adjust the transaction accordingly.
  System Configuration: If necessary, review the system configuration settings related to date handling in financial transactions. This may require assistance from an SAP Basis or configuration expert.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. SAP frequently releases notes that address specific error messages and provide guidance on resolution.
  Transaction Codes: Use transaction codes like FB01 (Post Document) or FBL1N (Vendor Line Item Display) to analyze the transactions and understand the context of the error.
  Documentation: Refer to SAP documentation for details on date handling in financial transactions, including fiscal year settings and posting periods.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to prevent it from occurring in the future.