How To Fix GJ684 - Posting Keys and SE Indicators Do not Exist.

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 684

• Message text: Posting Keys and SE Indicators Do not Exist.

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 GJ684 - Posting Keys and SE Indicators Do not Exist. ?

  The SAP error message GJ684, which states "Posting Keys and SE Indicators Do not Exist," typically occurs in the context of the SAP General Ledger (G/L) accounting module. This error indicates that the system is unable to find the necessary posting keys and special indicators (SE indicators) for the transaction you are trying to execute. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Configuration: The posting keys or special indicators required for the transaction have not been configured in the system.
  Incorrect Transaction Type: The transaction type you are trying to use may not be supported or may not have the necessary posting keys assigned.
  Custom Development: If there are custom developments or modifications in the system, they may not have been properly set up to handle the required posting keys.
  Transport Issues: If the configuration was recently transported from another system, it may not have been fully or correctly transported.
  
  Solution:
  
  
  Check Posting Keys:
  
  Go to the SAP configuration (SPRO) and navigate to the path: Financial Accounting (New) > General Ledger Accounting (New) > Document > Document Entry > Define Posting Keys.
  Ensure that the required posting keys for the transaction are defined and active.
  
  
  
  Check Special Indicators:
  
  Similarly, check the special indicators in the configuration settings. You can find this under: Financial Accounting (New) > General Ledger Accounting (New) > Document > Document Entry > Define Special G/L Indicators.
  Ensure that the special G/L indicators are correctly defined and linked to the appropriate posting keys.
  
  
  
  Review Transaction Type:
  
  Verify that the transaction type you are using is valid and that it has the necessary posting keys assigned to it.
  
  
  
  Check User Authorizations:
  
  Ensure that the user executing the transaction has the necessary authorizations to use the posting keys and special indicators.
  
  
  
  Consult Documentation:
  
  Review any relevant documentation or notes from SAP regarding the specific transaction you are trying to execute. There may be specific requirements or configurations needed.
  
  
  
  Transport Requests:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported correctly.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the program flow to identify where the error is being triggered.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for GJ684 in the SAP Support Portal.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB01 (Post Document), F-02 (General Posting), and others that may be related to the error.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify and resolve the issue related to the GJ684 error message in SAP. If the problem persists, it may be beneficial to consult with your SAP support team or a consultant for further assistance.