How To Fix /SAPSLL/CON_LMGM036 - Depreciation: Requested quantity not passed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPSLL/CON_LMGM -

• Message number: 036

• Message text: Depreciation: Requested quantity 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_LMGM036 - Depreciation: Requested quantity not passed ?

  The SAP error message /SAPSLL/CON_LMGM036 with the description "Depreciation: Requested quantity not passed" typically occurs in the context of logistics and inventory management, particularly when dealing with the handling of goods movements and inventory valuation.
  Cause:
  This error usually arises when there is a mismatch or an issue with the quantity of goods being processed in relation to the depreciation calculation. Some common causes include:
  
  Missing Quantity Information: The system expects a quantity to be specified for the transaction, but it is either missing or not passed correctly.
  Incorrect Configuration: There may be configuration issues in the system related to the handling of depreciation for the specific material or transaction type.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data that prevent the system from calculating depreciation correctly.
  Transaction Type Issues: The transaction type being used may not be set up to handle depreciation correctly.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Check the Transaction: Review the transaction that triggered the error. Ensure that all required fields, especially the quantity, are filled in correctly.
  Review Material Master Data: Check the material master data for the item involved in the transaction. Ensure that all relevant fields related to depreciation and inventory valuation are correctly maintained.
  Configuration Settings: Verify the configuration settings in the SAP system related to depreciation and inventory management. This may involve checking the settings in the relevant customizing transactions (e.g., SPRO).
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as this may resolve known issues related to this error.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or known issues.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as MB1A (Goods Withdrawal), MB1B (Transfer Posting), or MB1C (Other Goods Receipts).
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal, as they may provide specific fixes or workarounds.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.