How To Fix GJ574 - Company High Has Invalid Period.

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 574

• Message text: Company High Has Invalid Period.

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 GJ574 - Company High Has Invalid Period. ?

  The SAP error message GJ574 ("Company High Has Invalid Period") typically occurs in the context of financial or controlling modules, particularly when dealing with periods in the system that are not valid for the company code or controlling area in question. This error can arise during various processes, such as posting transactions, running reports, or executing month-end closing activities.
  Cause:
  
  Invalid Posting Period: The posting period you are trying to use is not open for the specified company code. This can happen if the period is closed or if the fiscal year variant settings do not allow postings in that period.
  Configuration Issues: There may be configuration issues in the fiscal year variant or the period control settings for the company code.
  Incorrect Company Code: The company code specified in the transaction may not be set up correctly or may not correspond to the fiscal year variant being used.
  Period Locking: The period may be locked for certain types of transactions, preventing postings.
  
  Solution:
  
  
  Check Posting Periods:
  
  Go to the transaction code OB52 (Change View "Open and Close Posting Periods") to check the open and closed periods for the relevant company code.
  Ensure that the period you are trying to post to is open.
  
  
  
  Review Fiscal Year Variant:
  
  Check the fiscal year variant assigned to the company code in transaction code OB37. Ensure that the periods are correctly defined and that the fiscal year variant is properly assigned to the company code.
  
  
  
  Adjust Period Control Settings:
  
  If necessary, adjust the period control settings to allow postings in the required periods.
  
  
  
  Check for Locks:
  
  Ensure that there are no locks on the period for the type of transaction you are trying to execute. This can be checked in the relevant transaction or configuration settings.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the settings or if changes are needed, consult with your finance or controlling team to ensure that the correct periods are open for posting.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB52: Open and Close Posting Periods
  OB37: Fiscal Year Variant
  FBL1N/FBL3N/FBL5N: To check vendor/customer/GL account line items, which may help in understanding the context of the error.
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on fiscal year variants and posting periods.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  
  By following these steps, you should be able to identify the cause of the GJ574 error and implement the necessary solutions to resolve it.