How To Fix FB466 - No periodic account statements were requested

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 466

• Message text: No periodic account statements were requested

What causes this issue?

You started the report for creating periodic account statements.

System Response

Customers were selected but no correspondence requests were set into
the trigger table.

How to fix this error?

Contact your system administrator.
Check whether the table BKORM is active.
A record already existed in the trigger table, possibly with the
identical key. However, this is very improbable. Please check the
entries in the table BKORM using the general table display. The key
of a created BKORM record for an account statement has, for example
here, the following appearance:
Client Adj. Posting Account Account Doc.no. Bus. USNAM DATE
Time of day
------------------------------------------------------------------------
000 SAP06 0001 D 0000012300 0000 LIEBOLD 14.05.1993
17:24:08
Start the report RFKORK00 again with the limits you entered. If no
correspondence requests are created again, inform your consultant.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FB466 - No periodic account statements were requested ?

  The SAP error message FB466 ("No periodic account statements were requested") typically occurs when you attempt to generate or process periodic account statements in the SAP system, but the necessary settings or data are not configured correctly. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Configuration: The periodic account statement may not be configured in the system for the specific account or customer/vendor.
  No Selection Criteria: The selection criteria for generating the statement may not have been defined, leading to no data being available for processing.
  Incorrect Account Type: The account type you are trying to generate a statement for may not support periodic statements.
  Authorization Issues: The user may not have the necessary authorizations to access or generate periodic account statements.
  
  Solutions:
  
  
  Check Configuration:
  
  Ensure that the periodic account statement is configured for the relevant accounts. This can be done in the configuration settings under Financial Accounting (FI) -> Accounts Receivable or Accounts Payable -> Periodic Account Statements.
  Verify that the necessary parameters for generating periodic statements are set up correctly.
  
  
  
  Define Selection Criteria:
  
  When generating the statement, ensure that you have defined the selection criteria properly. This includes specifying the correct date range, account number, and other relevant parameters.
  
  
  
  Review Account Type:
  
  Confirm that the account type (customer or vendor) you are working with is set up to allow periodic statements. You may need to check the account settings in the master data.
  
  
  
  Check User Authorizations:
  
  Ensure that the user attempting to generate the statement has the necessary authorizations. This can be checked in the user roles and profiles assigned to the user.
  
  
  
  Run the Report in Background:
  
  Sometimes, running the report in the background can help if there are performance issues or if the system is busy.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help files for specific details on how to configure and generate periodic account statements.
  
  
  
  Related Information:
  
  Transaction Codes: The error may occur in transactions such as F.27 (Periodic Account Statement) or F.28 (Account Statement).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or bugs related to periodic account statements.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the FB466 error and implement the necessary solutions to resolve it.