How To Fix GJ779 - Company & Does not Have Same Period Variant as Company &

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 779

• Message text: Company & Does not Have Same Period Variant as Company &

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 GJ779 - Company & Does not Have Same Period Variant as Company & ?

  The SAP error message GJ779 indicates that there is a mismatch in the period variants assigned to different company codes in the system. This typically occurs when you are trying to execute a transaction that involves multiple company codes, and those company codes have different fiscal year variants or period variants configured.
  Cause:
  
  Different Period Variants: The company codes involved in the transaction have different period variants assigned. Each company code can have its own fiscal year variant, which defines the number of periods in a fiscal year and how they are structured.
  Configuration Issues: There may be a configuration issue where the period variant for one company code does not match the period variant of another company code involved in the transaction.
  Transaction Type: The transaction you are trying to execute may require that all company codes involved share the same period variant.
  
  Solution:
  
  
  Check Period Variants:
  
  Go to the transaction code OB29 (Maintain Fiscal Year Variant) to check the period variants assigned to the company codes involved.
  Ensure that the period variants for the company codes are the same.
  
  
  
  Change Period Variant:
  
  If the period variants are different and you need them to be the same, you can change the period variant for one of the company codes. This can be done in the same transaction (OB29) by assigning the desired period variant to the company code.
  
  
  
  Consult with Configuration Team:
  
  If you are unsure about changing the period variant, consult with your SAP configuration team or a functional consultant to understand the implications of changing the period variant for a company code.
  
  
  
  Transaction Review:
  
  Review the transaction you are trying to execute to ensure that it is appropriate for the company codes involved. If necessary, split the transaction to handle each company code separately.
  
  
  
  Related Information:
  
  Fiscal Year Variant: This defines how the fiscal year is structured, including the number of periods and special periods.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB29 (Maintain Fiscal Year Variant) and OBA7 (Define Company Code).
  Documentation: Refer to SAP documentation or help files for more detailed information on fiscal year variants and period variants.
  
  By ensuring that the company codes involved in your transaction have the same period variant, you should be able to resolve the GJ779 error message.