How To Fix FY055 - For settlement run &, no settled items were found

SAP Error Message - Details

• Message type: E = Error

• Message class: FY - Payment Cards

• Message number: 055

• Message text: For settlement run &, no settled items were found

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 FY055 - For settlement run &, no settled items were found ?

  The SAP error message FY055, which states "For settlement run &, no settled items were found," typically occurs during the settlement process in SAP, particularly in the context of Asset Accounting (FI-AA) or Project System (PS). This error indicates that the system did not find any items eligible for settlement in the specified settlement run.
  Causes:
  
  No Eligible Items: There may be no costs or revenues that are eligible for settlement in the specified period or for the specified object (e.g., internal order, project).
  Incorrect Selection Criteria: The selection criteria used in the settlement run may not match any existing settled items.
  Settlement Not Required: The items may have already been settled in a previous run, or they may not require settlement at all.
  Incorrect Configuration: The configuration settings for the settlement process may not be set up correctly, leading to no items being identified for settlement.
  Posting Period Issues: The posting period may be closed, preventing any new settlements from being processed.
  
  Solutions:
  
  Check Eligibility: Verify that there are indeed items that should be settled. Check the relevant internal orders, projects, or assets to ensure they have costs that need to be settled.
  Review Selection Criteria: Ensure that the selection criteria used in the settlement run are correct. This includes checking the settlement period, object types, and any other filters applied.
  Check Previous Settlements: Look into previous settlement runs to confirm whether the items have already been settled. If they have, no further action is needed.
  Configuration Review: Review the configuration settings for the settlement process in the relevant module (FI-AA or PS) to ensure they are set up correctly.
  Open Posting Period: Ensure that the posting period for the settlement run is open. If it is closed, you may need to open it or adjust the settlement run to a period that is open.
  Run a Test Settlement: If applicable, run a test settlement with a smaller selection of items to see if the issue persists.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like KO88 (for internal orders) or CJ88 (for project settlements) to perform the settlement runs.
  SAP Notes: Check SAP Notes for any known issues or patches related to the FY055 error message.
  Documentation: Refer to SAP documentation for detailed guidance on the settlement process in the relevant module (FI-AA or PS).
  User Exits and BAdIs: If custom logic is involved in the settlement process, check for any user exits or BAdIs that might affect the selection of items for settlement.
  
  By following these steps, you should be able to identify the cause of the FY055 error and take appropriate action to resolve it.