>4367 - Default values for general ledger item were reset

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 367

• Message text: Default values for general ledger item were reset

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.

AnswerBot

• What is the cause and solution for SAP error message >4367 - Default values for general ledger item were reset ?

  The SAP error message "4367 Default values for general ledger item were reset" typically occurs in the context of financial transactions, particularly when dealing with General Ledger (G/L) accounts. This message indicates that the system has reset the default values for a G/L account, which can happen for various reasons.
  Cause:
  
  Missing or Incorrect Configuration: The default values for the G/L account may not be properly configured in the system. This can happen if the account is newly created or if there have been changes to the account settings.
  Transaction Type: The type of transaction being processed may not align with the default settings for the G/L account, leading to a reset of those values.
  User Input: If a user manually enters values that conflict with the default settings, the system may reset them to maintain data integrity.
  System Updates or Changes: Changes in the system configuration, such as updates or patches, can sometimes lead to default values being reset.
  
  Solution:
  
  Check G/L Account Configuration: Review the configuration of the G/L account in the SAP system. Ensure that all necessary default values are set correctly. This can be done in the transaction code FS00 (G/L Account Master Record).
  Review Transaction Settings: Ensure that the transaction type being processed is compatible with the G/L account settings. Check if any specific settings need to be adjusted for the transaction.
  User Training: If the issue is related to user input, consider providing training to users on how to correctly enter data in the system to avoid conflicts with default values.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the error message and how to resolve it.
  System Logs: Check system logs for any additional error messages or warnings that may provide more context about why the default values were reset.
  Contact SAP Support: If the issue persists and cannot be resolved through configuration changes, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 for G/L account maintenance, FB50 for general ledger postings, and OB52 for posting periods.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal, as there may be specific patches or updates that address this issue.
  User Forums: Engage with SAP user communities or forums where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  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.