How To Fix FICO1339 - Repetition period of calc./due date is not a multiple of the use period

SAP Error Message - Details

• Message type: E = Error

• Message class: FICO1 -

• Message number: 339

• Message text: Repetition period of calc./due date is not a multiple of the use 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 FICO1339 - Repetition period of calc./due date is not a multiple of the use period ?

  The SAP error message FICO1339, which states "Repetition period of calc./due date is not a multiple of the use period," typically occurs in the context of financial transactions, particularly when dealing with payment terms, billing cycles, or installment plans in the SAP FICO (Financial Accounting and Controlling) module.
  Cause:
  This error arises when there is a mismatch between the repetition period of a calculation or due date and the use period defined in the system. Specifically, it indicates that the frequency at which a payment or calculation is expected to occur does not align with the defined usage period. For example, if the repetition period is set to 10 days, but the use period is set to 7 days, the system will throw this error because 10 is not a multiple of 7.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Payment Terms: Review the payment terms associated with the transaction. Ensure that the repetition period (e.g., payment frequency) is a multiple of the use period (e.g., billing cycle).
  
  
  Adjust Repetition and Use Periods:
  
  Navigate to the relevant configuration settings in SAP.
  Adjust either the repetition period or the use period so that one is a multiple of the other. For example, if the use period is 7 days, you might change the repetition period to 14 days (which is a multiple of 7).
  
  
  
  Review Configuration Settings: 
  
  Go to the configuration settings in the SAP system (usually found in SPRO under Financial Accounting).
  Check the settings for payment terms, installment plans, or any other relevant configurations that might be causing the mismatch.
  
  
  
  Test the Changes: After making adjustments, test the transaction again to ensure that the error no longer appears.
  
  
  Consult Documentation: If you are unsure about the correct settings, refer to SAP documentation or consult with your SAP functional consultant for guidance on the appropriate configuration.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBB8 (for payment terms) or F110 (for automatic payment transactions) to access and modify the relevant settings.
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error message, as there may be known issues or additional guidance provided by SAP.
  User Roles: Ensure that you have the necessary permissions to make changes to financial configurations in SAP.
  
  By following these steps, you should be able to resolve the FICO1339 error and ensure that your payment terms and billing cycles are correctly aligned.