Do you have any question about this error?
Message type: E = Error
Message class: H1 - Messages Used in HR Funds and Position Management
Message number: 736
Message text: Planned, submitted or approved records detected for &1 &2 &3
&v1& &v2& &v3& has infotypes that have not been activated/rejected.
Unable to change budget status.
Activate or reject these changes before you change the budget status.
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.
H1736
- Planned, submitted or approved records detected for &1 &2 &3 ?The SAP error message H1736 ("Planned, submitted or approved records detected for &1 &2 &3") typically occurs in the context of project management or resource planning within SAP. This error indicates that there are existing records in the system that are either planned, submitted, or approved, which are preventing the user from performing a certain action (like deleting or modifying a record).
Cause:
The error is usually caused by one of the following scenarios:
- Existing Records: There are existing planned, submitted, or approved records associated with the object (e.g., project, task, or resource) you are trying to modify or delete.
- Data Integrity: SAP enforces data integrity rules to ensure that changes do not disrupt the workflow or project management processes. If there are dependencies or linked records, the system will prevent changes to maintain consistency.
Solution:
To resolve this error, you can take the following steps:
Check Existing Records:
- Review the records associated with the object in question. You can use transaction codes like
CJ20N
(Project Builder) orCJI3
(Project Actual Line Items) to check for any planned, submitted, or approved records.Modify or Delete Records:
- If you find records that are no longer needed, you may need to modify or delete them. Ensure that you have the necessary authorizations to perform these actions.
- If the records are still relevant, consider adjusting your approach to accommodate them.
Consult with Stakeholders:
- If the records are part of an ongoing process, consult with project managers or relevant stakeholders to understand the implications of modifying or deleting these records.
Use Transaction Codes:
- Use transaction codes like
CJ02
(Change Project) orCJ03
(Display Project) to manage project-related records effectively.Check for Dependencies:
- Investigate if there are any dependencies or linked records that might be causing the issue. You may need to resolve these dependencies before proceeding.
System Configuration:
- In some cases, the error may be related to system configuration or settings. Consult with your SAP Basis or technical team to ensure that the system is configured correctly.
Related Information:
By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
H1735
Select a message
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
H1734
No default value maintained for the classification of &1 &2 &3
What causes this issue? No valid <DS:GLOS.35A1CDEBCD926F24E10000009B38F9B7>Default value</> defined for the pay scale classification of &...
H1740
Funds Precommitment was transferred for financing
What causes this issue? The amounts reserved for the position in the form of a funds precommitment are used to finance the person. In order to make t...
H1741
Financing remains as a funds precommitment in the position
What causes this issue? You have deleted the indirect financing of a person through a position. The corresponding funds commitment will be deleted. T...
Click on this link to search all SAP messages.