How To Fix /SAPSLL/CON_LMGM035 - Depreciation: Unit of measure not passed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPSLL/CON_LMGM -

• Message number: 035

• Message text: Depreciation: Unit of measure not passed

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 /SAPSLL/CON_LMGM035 - Depreciation: Unit of measure not passed ?

  The SAP error message /SAPSLL/CON_LMGM035 indicates that there is an issue with the unit of measure (UoM) not being passed during a depreciation posting. This error typically arises in the context of logistics and financial transactions where the system expects a unit of measure to be specified but does not receive one.
  Cause:
  
  Missing Unit of Measure: The most common cause is that the unit of measure for the asset or the transaction is not defined or is missing in the relevant master data.
  Configuration Issues: There may be configuration issues in the asset accounting or logistics settings that prevent the unit of measure from being recognized or passed correctly.
  Data Entry Errors: Incorrect or incomplete data entry during the transaction processing can lead to this error.
  Integration Issues: If the transaction involves multiple modules (e.g., Asset Accounting and Materials Management), integration issues may prevent the unit of measure from being transferred correctly.
  
  Solution:
  
  Check Master Data: Verify that the asset master data includes the correct unit of measure. Ensure that the UoM is defined for the asset in question.
  Review Configuration: Check the configuration settings in the Asset Accounting module to ensure that the unit of measure is properly set up. This may involve reviewing the settings in transaction codes like OAOA (for asset classes) or OAYZ (for UoM settings).
  Data Entry Validation: Ensure that all required fields are filled out correctly during the transaction entry. If you are using a custom transaction or program, ensure that it is designed to pass the unit of measure.
  Check Integration Settings: If the transaction involves multiple modules, check the integration settings between those modules to ensure that data is being passed correctly.
  Consult Documentation: Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS01 (Create Asset), AS02 (Change Asset), and AS03 (Display Asset) to check asset details.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal for any known issues or fixes.
  User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  If the problem persists after checking these areas, it may be beneficial to involve your SAP support team or a consultant with expertise in SAP Asset Accounting and logistics integration.