How To Fix FAA_MD138 - Asset &1, subnumber &2 was created in company code &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FAA_MD - Fixed Asset Master

• Message number: 138

• Message text: Asset &1, subnumber &2 was created in company code &3

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_MD138 - Asset &1, subnumber &2 was created in company code &3 ?

  The SAP error message FAA_MD138 indicates that an asset with a specific subnumber has been created in a particular company code. This error typically arises in the context of asset accounting when there is an attempt to perform an operation (like posting or changing an asset) that is not allowed due to the asset's status or configuration.
  Cause:
  
  Asset Already Exists: The asset with the specified subnumber already exists in the specified company code, and the operation you are trying to perform is not valid for existing assets.
  Incorrect Configuration: There may be configuration issues in the asset accounting settings that prevent the operation from being completed.
  Authorization Issues: The user may not have the necessary authorizations to perform actions on the specified asset.
  Data Inconsistencies: There may be inconsistencies in the asset master data that need to be resolved.
  
  Solution:
  
  Check Asset Existence: Verify if the asset with the specified subnumber already exists in the system. You can do this by using transaction code AS03 (Display Asset) to check the asset details.
  Review Asset Status: Ensure that the asset is in a status that allows the operation you are trying to perform. For example, if the asset is retired or in a locked status, you may need to unlock it or change its status.
  Correct Configuration: If there are configuration issues, consult with your SAP FI/CO consultant to review the asset accounting settings and make necessary adjustments.
  Check Authorizations: Ensure that the user has the appropriate authorizations to perform the action on the asset. This may involve checking user roles and permissions.
  Data Consistency Check: Run any necessary reports or transactions to check for data inconsistencies in the asset master data and resolve them.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  AS01: Create Asset
  AS02: Change Asset
  AS03: Display Asset
  AS11: Create Asset Master Record
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to Asset Accounting for best practices and guidelines on managing assets.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.