AA560 - Inconsistencies in screen layout of genl. ledger/ subsid. ledger

SAP Error Message - Details

• Message type: E = Error

• Message class: AA - Messages for Asset Accounting

• Message number: 560

• Message text: Inconsistencies in screen layout of genl. ledger/ subsid. ledger

What causes this issue?

Field &v2& is specified as a required entry field in the field status
of general ledger account &v1&. However, it is not possible to enter
values for this field in Asset Accounting using transaction type &v3&.

System Response

The transaction cannot be carried out, based on the current
Customizing settings.

How to fix this error?

If you want to post the asset using transaction type &v3&,
you must change the field status of account &v1&, so that field &v2&
is no longer a required entry. You specify the field status of the
general ledger accounts in table T004F.

Error message extract from SAP system. Copyright SAP SE.

AnswerBot

• What is the cause and solution for SAP error message AA560 - Inconsistencies in screen layout of genl. ledger/ subsid. ledger ?

  The SAP error message AA560 indicates that there are inconsistencies in the screen layout of the general ledger and subsidiary ledger. This error typically arises when there are discrepancies in the configuration or settings between the general ledger (G/L) and the asset accounting (AA) module, particularly in how data is displayed or processed.
  Cause:
  
  Configuration Mismatch: The screen layout settings for the general ledger and asset accounting may not be aligned. This can happen if changes were made to one without corresponding changes to the other.
  Missing Fields: Certain fields that are required in the asset accounting screen layout may not be present in the general ledger layout, or vice versa.
  Customizations: If there are custom screen layouts or modifications in either the G/L or AA, these could lead to inconsistencies.
  Transport Issues: If configurations were transported from one system to another (e.g., from development to production), inconsistencies may arise if not all relevant settings were included.
  
  Solution:
  
  
  Check Screen Layouts: Review the screen layout settings for both the general ledger and asset accounting. Ensure that they are consistent and that all required fields are present in both layouts.
  
  You can access the screen layout settings via the transaction code OAOA for asset accounting and OB52 for general ledger.
  
  
  
  Adjust Configuration: If you find discrepancies, adjust the configuration settings to ensure that both the G/L and AA layouts match. This may involve adding or removing fields or changing the display settings.
  
  
  Review Customizations: If there are customizations in place, review them to ensure they do not conflict with standard settings. You may need to consult with your ABAP team or SAP Basis team if custom code is involved.
  
  
  Transport Requests: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport request. If not, you may need to re-transport the missing configurations.
  
  
  Testing: After making changes, perform thorough testing to ensure that the error is resolved and that both the general ledger and asset accounting functions correctly.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review SAP documentation for both the general ledger and asset accounting modules to understand the expected configurations and settings.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after following these steps, it may be beneficial to consult with SAP support for further assistance.