Do you have any question about this error?
Message type: E = Error
Message class: LQ - Proposal Pool Management
Message number: 390
Message text: Usage counters have not been refreshed up till now
The proposal pool use counters have not been refreshed.
Entries which are now used may be deleted, so only the count can be
calculated (test mode).
Schedule a where-used counter refresh using transaction STMA ->
Organization -> Where-used list.
You can delete no longer used entries.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
LQ390
- Usage counters have not been refreshed up till now ?The SAP error message LQ390 indicates that the usage counters for a particular material or product have not been refreshed. This can occur in the context of SAP's Logistics Execution (LE) or Warehouse Management (WM) modules, where usage counters are used to track the consumption or movement of materials.
Cause:
The error can be caused by several factors, including:
- Configuration Issues: The system may not be configured correctly to refresh usage counters automatically.
- Batch Jobs: The background jobs responsible for updating the usage counters may not have run or may have failed.
- Data Consistency: There may be inconsistencies in the data that prevent the counters from being updated.
- User Authorizations: The user may not have the necessary authorizations to refresh the usage counters.
- System Performance: High system load or performance issues may prevent timely updates of the counters.
Solution:
To resolve the LQ390 error, you can take the following steps:
Check Configuration:
- Ensure that the configuration settings for usage counter updates are correctly set in the system. This may involve checking the relevant customizing settings in SPRO.
Run Background Jobs:
- Check if the background jobs responsible for refreshing usage counters (like the job for updating inventory or usage statistics) are scheduled and running correctly. You can use transaction SM37 to monitor job status.
Manual Refresh:
- If necessary, you can manually refresh the usage counters using transaction LX02 (for warehouse management) or other relevant transactions, depending on your specific setup.
Check for Errors:
- Look for any error logs or messages in transaction SLG1 (Application Log) that might provide more context on why the counters are not being updated.
Data Consistency Check:
- Perform a data consistency check to ensure that there are no issues with the material master or inventory data that could be causing the problem.
User Authorizations:
- Verify that the user has the necessary authorizations to perform the actions required to refresh the usage counters.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
Contact SAP Support:
- If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the LQ390 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
LQ389
Maximum number of sessions reached; close an application
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LQ388
Result list is formatted in new session
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LQ391
Security creation date set to date of last refresh
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LQ392
No run information was found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.