How To Fix FVER108 - ID number of 'old stock' is missing

SAP Error Message - Details

• Message type: E = Error

• Message class: FVER - Message Class for Executable Security Rights

• Message number: 108

• Message text: ID number of 'old stock' is missing

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 FVER108 - ID number of 'old stock' is missing ?

  The SAP error message FVER108, which states that the "ID number of 'old stock' is missing," typically occurs in the context of inventory management and stock valuation. This error is often related to the handling of stock that has been marked as "old stock" or "blocked stock" in the system.
  Cause:
  
  Missing ID Number: The error indicates that the system is expecting an ID number for the old stock, but it is not available. This can happen if the stock was not properly identified or if there was an issue during the stock transfer or posting process.
  Configuration Issues: There may be configuration settings in the system that are not set up correctly, leading to the inability to recognize or process old stock.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data related to the stock, such as missing or incorrect entries in the material master or stock overview.
  
  Solution:
  
  Check Material Master Data: Ensure that the material master data is complete and correctly configured. Verify that the old stock is properly defined and that all necessary fields are filled out.
  Review Stock Overview: Use transaction codes like MMBE to check the stock overview for the material in question. Look for any discrepancies or missing information related to the old stock.
  Update Stock Information: If the ID number is genuinely missing, you may need to update the stock information manually or through a batch job to ensure that the ID number is assigned correctly.
  Check Configuration Settings: Review the configuration settings in the SAP system related to inventory management and stock handling. Ensure that all necessary settings for handling old stock are correctly configured.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  Contact 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 based on your specific system configuration and version.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MMBE (Stock Overview), MB1A (Goods Withdrawal), and MB1B (Transfer Posting) to help diagnose and resolve stock-related issues.
  Documentation: Review SAP documentation related to inventory management and stock handling for best practices and guidelines.
  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 cause of the FVER108 error and implement a solution to resolve it.