Do you have any question about this error?
Message type: E = Error
Message class: RM - Messages for Repetitive Manufacturing
Message number: 736
Message text: No planned order found for document log number &
When backflushing with separate goods issue, the system creates
references to the reduced planned orders in table BLPR. These
references are not deleted until the goods issue is actually carried
out and must still be available when reversing the backflush before the
GI has been carried out.
The reference to assigned planned orders is missing for the specified
document log number.
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.
RM736
- No planned order found for document log number & ?The SAP error message RM736 "No planned order found for document log number &" typically occurs in the context of production planning and control when the system is unable to find a planned order associated with a specific document log number. This can happen for various reasons, and understanding the cause and potential solutions can help resolve the issue.
Causes:
- Incorrect Document Log Number: The document log number provided may be incorrect or does not exist in the system.
- Planned Order Deletion: The planned order associated with the document log number may have been deleted or not created.
- Data Synchronization Issues: There may be issues with data synchronization between different modules or systems, leading to missing planned orders.
- Authorization Issues: The user may not have the necessary authorizations to view or access the planned order.
- Configuration Issues: There may be configuration issues in the production planning module that prevent the planned order from being generated or displayed.
Solutions:
- Verify Document Log Number: Check the document log number for accuracy. Ensure that it corresponds to an existing planned order.
- Check for Planned Order Creation: Use transaction codes like MD04 (Stock/Requirements List) or CO03 (Display Production Order) to see if the planned order was created. If not, investigate why it was not generated.
- Review Deletion Logs: If the planned order was deleted, check the deletion logs to understand when and why it was removed.
- Check Authorizations: Ensure that the user has the necessary authorizations to access the planned order. This may involve checking user roles and permissions.
- Consult with IT Support: If the issue persists, consult with your IT support team or SAP Basis team to check for any underlying system issues or configuration problems.
- Recreate Planned Order: If the planned order is missing and cannot be found, you may need to recreate it based on the requirements.
Related Information:
By following these steps, you should be able to identify the cause of the RM736 error and implement a suitable solution. If the problem continues, consider reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
RM735
Error reading Customizing entry for LIS
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
RM734
In case of final conf. w. qties on line, subprocesses are posted immed.
What causes this issue? The situation is as follows: optional reporting points no automatic GR separation of backflushing processes there are reporti...
RM737
No planned order found for key 'plnum = &'
What causes this issue? When backflushing with separate goods issue, the system creates references to the reduced planned orders in table BLPR. The s...
RM738
GR quantity for confirmation & > total GR quantity for planned order &
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.