How To Fix FN518 - Customer & company code &, no postings exist within time interval

SAP Error Message - Details

• Message type: E = Error

• Message class: FN - BAPI Messages

• Message number: 518

• Message text: Customer & company code &, no postings exist within time interval

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 FN518 - Customer & company code &, no postings exist within time interval ?

  The SAP error message FN518 ("Customer & company code &, no postings exist within time interval") typically occurs in the context of financial transactions, particularly when dealing with customer accounts and their associated company codes. This error indicates that there are no postings (transactions) found for the specified customer and company code within the defined time interval.
  Cause:
  
  No Transactions: The most straightforward cause is that there are indeed no transactions recorded for the specified customer and company code within the selected date range.
  Incorrect Date Range: The date range specified in the report or transaction might not cover the period during which transactions were made.
  Data Entry Errors: There may be a typo or incorrect entry in the customer number or company code.
  Posting Periods: The posting periods may be closed, preventing any transactions from being recorded in the specified timeframe.
  Selection Criteria: The selection criteria used in the report or transaction might be too restrictive, filtering out existing transactions.
  
  Solution:
  
  Check Transactions: Verify if there are any transactions for the specified customer and company code. You can do this by checking the customer account balance or transaction history.
  Adjust Date Range: Modify the date range in the report or transaction to ensure it encompasses the period when transactions were made.
  Verify Customer and Company Code: Double-check the customer number and company code for any errors or typos.
  Review Posting Periods: Ensure that the posting periods are open for the dates you are trying to access. If they are closed, you may need to open them or adjust your date range.
  Broaden Selection Criteria: If applicable, broaden the selection criteria to include more transactions or remove unnecessary filters.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like FBL5N (Customer Line Item Display) or FD10N (Customer Account Balance) to check for existing transactions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to view the customer account and related transactions.
  Consult Documentation: Refer to SAP documentation or help files for more detailed information on customer account management and reporting.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in financial accounting within SAP.