How To Fix FAA_ARCH012 - No assets to be processed by preprocessing run for company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FAA_ARCH - Data Archiving Fixed Asset Accounting S/4

• Message number: 012

• Message text: No assets to be processed by preprocessing run for company code &1

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 FAA_ARCH012 - No assets to be processed by preprocessing run for company code &1 ?

  The SAP error message FAA_ARCH012 indicates that there are no assets available to be processed during the preprocessing run for a specified company code. This error typically occurs in the context of archiving asset accounting data.
  Cause:
  
  No Assets Available: The primary reason for this error is that there are no assets in the specified company code that meet the criteria for archiving.
  Selection Criteria: The selection criteria defined for the archiving run may not match any existing assets. This could be due to filters applied based on asset status, date ranges, or other parameters.
  Data Already Archived: If the assets have already been archived in a previous run, there will be no assets left to process.
  Incorrect Company Code: The company code specified in the run may not have any assets assigned to it.
  
  Solution:
  
  Check Asset Existence: Verify that there are assets in the specified company code. You can do this by using transaction code AS03 (Display Asset) to check if any assets exist.
  Review Selection Criteria: Review the selection criteria used in the archiving run. Ensure that the criteria are set correctly to include the assets you intend to archive.
  Check Archive Status: If assets have been archived previously, check the archive status to confirm that there are indeed assets available for archiving.
  Change Company Code: If you are running the archiving process for the wrong company code, correct it to the appropriate one that contains assets.
  Consult Documentation: Refer to SAP documentation or notes related to asset archiving for any specific requirements or configurations that may need to be addressed.
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  S_ALR_87012082: Asset History Sheet
  AS01/AS02: Create/Change Asset
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to asset archiving.
  Archiving Process: Familiarize yourself with the overall archiving process in SAP, including the prerequisites and steps involved in archiving asset data.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis or functional team for further investigation.