How To Fix GJ780 - Company & Has Different Period Variant - Not Processed.

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 780

• Message text: Company & Has Different Period Variant - Not Processed.

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 GJ780 - Company & Has Different Period Variant - Not Processed. ?

  The SAP error message GJ780 ("Company & has different period variant - Not Processed") typically occurs in the context of financial or controlling transactions when there is a mismatch between the period variant settings of the company code and the transaction being processed. This can happen in various modules, including General Ledger (FI) and Controlling (CO).
  Cause:
  
  Different Period Variants: The company code is configured with a specific period variant that does not match the period variant of the transaction or the controlling area.
  Configuration Issues: The period variant settings in the configuration may not be aligned, leading to discrepancies.
  Transaction Timing: The transaction may be attempted in a period that is not open for posting in the specified period variant.
  
  Solution:
  
  
  Check Period Variant Settings:
  
  Go to the configuration settings for the company code and the controlling area.
  Verify the period variant assigned to the company code (Transaction Code: OBBP for FI or OKEQ for CO).
  Ensure that the period variant assigned to the transaction matches the one assigned to the company code.
  
  
  
  Adjust Period Variants:
  
  If necessary, change the period variant for the company code or the controlling area to ensure they are consistent.
  You can also create a new period variant if needed.
  
  
  
  Open Posting Periods:
  
  Check if the posting period for the transaction is open. You can do this by navigating to the transaction code OB52 (for FI) or OKEQ (for CO) to review the open and closed periods.
  If the period is closed, you may need to open it for posting or adjust the transaction date.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP Basis or configuration team for specific guidance on period variants and their implications.
  
  
  
  Testing:
  
  After making changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Period Variants: These are used in SAP to define the fiscal periods for posting transactions. Each company code can have its own period variant.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBBP (for company code settings), OB52 (for posting periods), and OKEQ (for controlling area settings).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult SAP's support portal for further assistance.