Do you have any question about this error?
Message type: E = Error
Message class: FINS_FI_MPROJ - Mass Data Project
Message number: 073
Message text: No organizational units were locked when project &1 was started
When you start a project, all organizational units are locked and cannot
be accessed by other projects with the same project type.
When you complete this project, or reset it, these organizational units
are unlocked.
No organizational units were locked.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check if there are organizational units assigned to this project.
If organizational units are assigned, check whether you have made
changes to the project settings.
Error message extract from SAP system. Copyright SAP SE.
FINS_FI_MPROJ073
- No organizational units were locked when project &1 was started ?The SAP error message FINS_FI_MPROJ073 indicates that when a project (identified by the project number &1) was started, no organizational units were locked. This typically occurs in the context of project management and financial accounting within SAP, particularly when dealing with project-related transactions.
Cause:
The error usually arises due to one of the following reasons:
Missing Locking Mechanism: The system expects certain organizational units (like cost centers, profit centers, or internal orders) to be locked before a project can be started. If these units are not locked, the system cannot proceed with the project initialization.
Configuration Issues: There may be configuration settings in the project management or controlling modules that are not set up correctly, leading to the inability to lock the necessary organizational units.
User Authorizations: The user may not have the necessary authorizations to lock the organizational units, which can prevent the project from being started.
Project Settings: The project itself may not have been set up correctly, or the required organizational units may not have been defined in the project settings.
Solution:
To resolve the error, you can take the following steps:
Check Organizational Units: Ensure that the necessary organizational units (cost centers, profit centers, etc.) are defined and available for locking. You may need to review the project settings to confirm that the correct units are associated with the project.
Lock Organizational Units: Manually lock the required organizational units before starting the project. This can typically be done through the relevant transaction codes in SAP (e.g., using transaction codes like KSV1 for cost centers).
Review Configuration: Check the configuration settings in the project management and controlling modules to ensure that they are set up correctly. This may involve consulting with your SAP configuration team or reviewing the project management documentation.
User Authorizations: Verify that the user attempting to start the project has the necessary authorizations to lock the organizational units. If not, you may need to request additional permissions from your SAP security team.
Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the project management module and the locking mechanism for organizational units.
SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to successfully start the project.
Get instant SAP help. Start your 7-day free trial now.
FINS_FI_MPROJ072
Conflicting project &1 of type &2 (&3) is currently active
What causes this issue? Project &V1& is active at the same time as project &V4&. Project &V1& is of type &V2& (&V...
FINS_FI_MPROJ071
Project &1 does not have the required project type
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_FI_MPROJ074
Run data for project &1 has been deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_FI_MPROJ075
Event '&1' is only for manual activities. &2 is not a manual activity
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.