How To Fix AU075 - Asset balance sheet values not completely posted

SAP Error Message - Details

• Message type: E = Error

• Message class: AU - FI-AA utility program error messages

• Message number: 075

• Message text: Asset balance sheet values not completely posted

What causes this issue?

In company code &V1&, which is to be closed, APC values have not been
posted to Financial Accounting for all relevant depreciation areas.
Depreciation area &V2&, at least, is set up for periodic posting of APC
values.
The year-end closing checks if documents were posted that have an entry
date after the last run of the program for periodic posting of APC
values. If such documents are found, the system issues this message.

How to fix this error?

Check which depreciation areas are supposed to post APC values
periodically to Financial Accounting according to their Customizing
definitions (indicator: "Post assets periodically in General Ledger")
See the <DS:SIMG.ORFA_MIT_BEREICH>Define How Depreciation Areas Post to
General Ledger</> IMG activity.
Start the program for posting APC values. In the Asset Accounting main
menu, choose <LS>Periodic processing</>. Start this program in update
mode, regardless of whether or not documents are displayed in test
mode, or if a message appears stating that there are no documents to be
posted.
<DS:TRAN.ASKB>Start APC Posting Program</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AU075 - Asset balance sheet values not completely posted ?

  The SAP error message AU075, which states "Asset balance sheet values not completely posted," typically occurs in the context of asset accounting when there are discrepancies in the posting of asset values. This error can arise during various processes, such as asset acquisition, transfer, or retirement.
  Causes:
  
  Incomplete Posting: The asset values may not have been fully posted to the balance sheet accounts. This can happen if there are missing entries or if the posting was interrupted.
  Configuration Issues: Incorrect configuration in the asset accounting settings can lead to issues with how values are posted.
  Document Errors: There may be errors in the accounting documents related to the asset, such as missing or incorrect entries.
  Posting Period Issues: The posting period may be closed, preventing further postings to the asset accounts.
  Currency Differences: If there are currency conversion issues, it may lead to discrepancies in the asset values.
  
  Solutions:
  
  Check Posting Documents: Review the relevant accounting documents for the asset to ensure that all necessary postings have been made. Look for any missing entries or errors.
  Repost Missing Values: If you identify any missing postings, you may need to repost the values to ensure that the asset balance sheet values are complete.
  Review Configuration: Check the configuration settings in the Asset Accounting module to ensure that they are set up correctly. This includes verifying the account determination settings.
  Open Posting Period: If the posting period is closed, you may need to open it temporarily to allow for the necessary postings.
  Run Asset Reports: Use asset accounting reports (such as the Asset History Sheet) to identify discrepancies and understand where the issue lies.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS01 (Create Asset), AS02 (Change Asset), and AS03 (Display Asset) to manage asset postings.
  Asset Accounting Configuration: Understanding the configuration of asset accounting in SAP can help prevent future issues. This includes settings for asset classes, account determination, and depreciation areas.
  SAP Support: If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who specializes in Asset Accounting.
  
  By following these steps, you should be able to identify the cause of the AU075 error and implement a solution to resolve it.