How To Fix >4679 - Period with key &1 is after period with key &2

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 679

• Message text: Period with key &1 is after period with key &2

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 >4679 - Period with key &1 is after period with key &2 ?

  The SAP error message 4679 indicates that there is a problem with the period keys being used in a transaction. Specifically, it means that the period with key &1 is after the period with key &2. This typically occurs in financial transactions, such as posting documents or running reports, where the system expects the periods to be in a certain chronological order.
  Cause:
  
  Incorrect Period Selection: The user may have selected a posting period that is later than the period that is currently being processed.
  Configuration Issues: The fiscal year variant or period settings in the configuration may not be set up correctly, leading to inconsistencies.
  Data Entry Errors: Manual entry errors when specifying periods can lead to this issue.
  
  Solution:
  
  Check Period Selection: Review the periods you are trying to use in your transaction. Ensure that the period with key &1 is not later than the period with key &2.
  Adjust Posting Periods: If you are trying to post to a future period, ensure that the system allows postings to that period. You may need to change the settings in the configuration to allow postings to future periods if that is appropriate for your business process.
  Review Configuration: Check the configuration of your fiscal year variant and ensure that the periods are defined correctly. You can do this in the SAP configuration under:
  
  SPRO ? Financial Accounting ? Financial Accounting Global Settings ? Fiscal Year ? Define Fiscal Year Variant.
  
  
  Consult with Your SAP Administrator: If you are unsure about the settings or how to resolve the issue, consult with your SAP administrator or a functional consultant who can provide guidance based on your specific configuration and business processes.
  
  Related Information:
  
  Transaction Codes: You may encounter this error in various transaction codes related to financial postings, such as FB01 (Post Document), F-02 (General Posting), or during month-end closing activities.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling period-related issues.
  Documentation: Review SAP documentation related to fiscal year variants and period control to better understand how periods are managed within the system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.