How To Fix AM356 - Marker table could not be initialized

SAP Error Message - Details

• Message type: E = Error

• Message class: AM - Business Address Services

• Message number: 356

• Message text: Marker table could not be initialized

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 AM356 - Marker table could not be initialized ?

  The SAP error message AM356, which states "Marker table could not be initialized," typically occurs in the context of Asset Accounting (FI-AA) when the system is unable to initialize the marker table for asset transactions. This can happen due to various reasons, including configuration issues, data inconsistencies, or system errors.
  Causes:
  
  Configuration Issues: Incorrect settings in the Asset Accounting configuration can lead to this error. This includes issues with the chart of depreciation or asset classes.
  Data Inconsistencies: If there are inconsistencies in the asset master data or transaction data, it may prevent the marker table from being initialized.
  Authorization Issues: Lack of proper authorizations for the user trying to perform the transaction can also lead to this error.
  System Errors: Bugs or issues in the SAP system itself, especially if you are on an older version or have not applied the latest patches.
  
  Solutions:
  
  
  Check Configuration: Review the configuration settings for Asset Accounting. Ensure that the chart of depreciation and asset classes are correctly set up.
  
  Transaction Code: OADP (Define Depreciation Areas)
  Transaction Code: OAOA (Define Asset Classes)
  
  
  
  Review Asset Master Data: Check the asset master data for any inconsistencies or missing information. Ensure that all required fields are filled out correctly.
  
  Transaction Code: AS02 (Change Asset)
  
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the transaction. You can check this using transaction SU53 to see if there are any authorization failures.
  
  
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal. There may be specific notes addressing this error, especially if it is a known issue with a particular version of SAP.
  
  
  Consult SAP Support: If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They can provide more detailed troubleshooting steps based on your specific system configuration.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for Asset Accounting, such as AS01 (Create Asset), AS02 (Change Asset), and AS03 (Display Asset).
  Documentation: Review SAP documentation related to Asset Accounting for best practices and configuration guidelines.
  Community Forums: Check SAP Community forums or other user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the AM356 error and implement a solution.