How To Fix AA356 - Posting not possible in current document with this trans.type

SAP Error Message - Details

• Message type: E = Error

• Message class: AA - Messages for Asset Accounting

• Message number: 356

• Message text: Posting not possible in current document with this trans.type

What causes this issue?

This transaction type does not manage proportional values, contrary to
the transaction types which have already been used for posting to the
asset in the current document.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Close document, post transaction using another document.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AA356 - Posting not possible in current document with this trans.type ?

  The SAP error message AA356 ("Posting not possible in current document with this transaction type") typically occurs in the context of Asset Accounting (FI-AA) when there is an issue with the transaction type being used for posting an asset transaction. This error can arise due to several reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  Transaction Type Configuration: The transaction type being used may not be configured correctly in the system. This could include settings related to the posting period, document type, or asset class.
  
  
  Posting Period Issues: The posting period may be closed or not open for the transaction type you are trying to use. This is common at the end of a fiscal year or period.
  
  
  Document Type Restrictions: The document type associated with the transaction type may have restrictions that prevent posting under certain conditions.
  
  
  Asset Class Settings: The asset class may not allow the type of transaction you are trying to perform. For example, certain asset classes may be restricted from certain types of postings.
  
  
  Authorization Issues: The user may not have the necessary authorizations to perform the transaction with the specified transaction type.
  
  
  Solutions:
  
  
  Check Transaction Type Configuration:
  
  Go to the configuration settings for Asset Accounting (Transaction code: OAOA) and verify the settings for the transaction type you are using. Ensure that it is set up correctly for the type of posting you are attempting.
  
  
  
  Verify Posting Period:
  
  Check the posting period settings (Transaction code: OB52) to ensure that the period is open for the transaction type you are trying to post. If the period is closed, you may need to open it or post in a different period.
  
  
  
  Review Document Type Settings:
  
  Check the document type settings (Transaction code: OBA7) to ensure that the document type associated with your transaction type allows for the posting you are attempting.
  
  
  
  Inspect Asset Class Configuration:
  
  Review the asset class settings (Transaction code: OAOA) to ensure that the asset class allows the type of transaction you are trying to perform.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to perform the transaction. This may involve checking roles and authorizations in the user profile.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that may address this specific error message or provide additional guidance on resolving it.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OAOA (Asset Transaction Types), OB52 (Open/Close Posting Periods), and OBA7 (Document Types).
  SAP Documentation: Refer to SAP Help documentation for Asset Accounting for detailed information on transaction types and their configurations.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the AA356 error and implement the appropriate solution.