Do you have any question about this error?
Message type: E = Error
Message class: KM - Error messages for Profit Center Accounting
Message number: 694
Message text: Comp. code &1, version &2, fiscal year &3, profit ctr &4 currently locked
The data in company code &V1&, version &V2&, fiscal year &V3&, profit
center &V4& is currently locked by another transaction.
Processing is terminated.
Try to carry out the transaction again later.
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.
KM694
- Comp. code &1, version &2, fiscal year &3, profit ctr &4 currently locked ?The SAP error message KM694 indicates that a specific combination of company code, version, fiscal year, and profit center is currently locked. This typically occurs in the context of financial planning or controlling processes, where certain data entries or adjustments are restricted to prevent inconsistencies or errors during processing.
Cause:
Data Locking: The data for the specified combination is locked due to ongoing processes such as:
- A user is currently editing or processing data for that combination.
- A batch job or background process is running that locks the data.
- The data is locked due to a previous error or incomplete transaction.
Authorization Issues: The user may not have the necessary authorizations to access or modify the locked data.
Configuration Settings: Certain configuration settings in the system may enforce locks on specific data to maintain data integrity.
Solution:
Check for Active Sessions:
- Use transaction code
SM12
to check for any active locks on the specified combination. If you find a lock that is no longer needed, you can delete it (if you have the necessary authorizations).Wait for Process Completion: If the lock is due to a background job or another user, you may need to wait until the process is completed. You can check the status of background jobs using transaction code
SM37
.Review Authorizations: Ensure that the user attempting to access the data has the necessary authorizations. You can check this using transaction code
SU53
after the error occurs.Consult with IT Support: If you are unable to resolve the issue, it may be necessary to consult with your SAP Basis or IT support team to investigate further. They can check for any system-level issues or configurations that may be causing the lock.
Check Configuration: Review the configuration settings related to the controlling module to ensure that there are no settings that are inadvertently causing locks.
Related Information:
Transaction Codes:
SM12
: To view and manage locks.SM37
: To monitor background jobs.SU53
: To check authorization issues.Documentation: Refer to SAP Help documentation for more details on data locking mechanisms and how they work within the SAP system.
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
By following these steps, you should be able to identify the cause of the KM694 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
KM693
Incorrect plan values for balance sheet accounts must be converted
What causes this issue? Balance sheet account &V1&, version &V2& for fiscal year &V3& contains plan data with the incorrect b...
KM692
Balance sheet accounts should be copied for the entire year if possible
What causes this issue? Balance sheet account balances are posted as deltas in the database and aggregated over periods for display in planning or re...
KM695
Account &1 does not exist in chart of accounts &2
What causes this issue? You have entered account &V1& in the table of allowed revenue and stock change accounts in planning. However, account...
KM696
The dummy profit center is not assigned correctly. Cleanup by saving.
What causes this issue? Not all company codes are assigned to the dummy profit center.System Response The system issues an error message and will no...
Click on this link to search all SAP messages.