How To Fix VDM_FND_DATEFUNCTION358 - DateFunction &1 is locked in request &2 by user &3

SAP Error Message - Details

• Message type: E = Error

• Message class: VDM_FND_DATEFUNCTION - Date Function Message Class

• Message number: 358

• Message text: DateFunction &1 is locked in request &2 by user &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 VDM_FND_DATEFUNCTION358 - DateFunction &1 is locked in request &2 by user &3 ?

  The SAP error message VDM_FND_DATEFUNCTION358 indicates that a specific date function (identified by &1) is locked in a request (identified by &2) by a user (identified by &3). This typically occurs in the context of date calculations or functions that are being accessed or modified in a concurrent environment.
  Cause:
  
  Concurrent Access: The error usually arises when multiple users or processes are trying to access or modify the same date function simultaneously. This can happen in scenarios where a long-running transaction is holding a lock on the date function.
  User Lock: The user identified in the error message has a lock on the date function, which prevents other users from accessing it until the lock is released.
  System Configuration: There may be specific configurations or settings in the SAP system that lead to locking behavior for certain date functions.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Locking User: Use transaction codes like SM12 (to view and manage locks) to identify the user who is holding the lock. You can check the lock entries and see if the user is still active.
  Contact the User: If possible, contact the user who is holding the lock to see if they can release it or if they are done with their transaction.
  Terminate the Lock: If the locking user is no longer active or if the lock is stale, you may need to delete the lock entry using transaction SM12. However, this should be done with caution and typically requires appropriate authorizations.
  Review System Performance: If this issue occurs frequently, it may be worth reviewing the system performance and transaction design to minimize locking conflicts. Consider optimizing long-running transactions or implementing better concurrency control.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (for lock entries), SM21 (for system logs), and ST22 (for dumps) to diagnose issues further.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific date function or locking behavior.
  Documentation: Review SAP documentation regarding date functions and locking mechanisms to understand how they work and best practices for avoiding conflicts.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.