As has been the case with the previous three posts, this one was an issue I faced and managed to resolve.
I wanted to check a particular functionality on a custom module pool screen after changing planned order quantities from MD12. However when i tried saving after making changes, i got the following error.
Moving to the second tab "Assignment" gave me this, and i was thrown out of the transaction - ruthlessly (dramatic enough?)
Determined to find the cause, i made some assumptions which were right on target.
A validation has been performed on the combination of MRP Controller and Plant, when the save button is clicked and hence the error.
However, if there was no link connecting the MRP controller 001 with the plant PT01, how was the planned order created in the first place using transaction MD11?
The logical implication to follow was that the MRP controller initially belonged to plant PT01, and planned orders were created. (Above is the screenshot of transaction OMD0 where the connection between plants and MRP controllers is made). Later on, the controller moves to another plant or is removed from the system. And when attempts are made to change the previously created planned orders, the error is thrown. Savvy?
To ensure that these assumptions do not go wayward, the following was performed. Creation of the MRP controller 001 in the plant PT01 using the OMD0 transaction.
These values go and sit in table T024D which is meant for MRP controllers created in the SAP system.
This in-turn creates a customizing request which can be accessed using SE09/SE10.
I wanted to check a particular functionality on a custom module pool screen after changing planned order quantities from MD12. However when i tried saving after making changes, i got the following error.
A validation has been performed on the combination of MRP Controller and Plant, when the save button is clicked and hence the error.
However, if there was no link connecting the MRP controller 001 with the plant PT01, how was the planned order created in the first place using transaction MD11?
The logical implication to follow was that the MRP controller initially belonged to plant PT01, and planned orders were created. (Above is the screenshot of transaction OMD0 where the connection between plants and MRP controllers is made). Later on, the controller moves to another plant or is removed from the system. And when attempts are made to change the previously created planned orders, the error is thrown. Savvy?
To ensure that these assumptions do not go wayward, the following was performed. Creation of the MRP controller 001 in the plant PT01 using the OMD0 transaction.
These values go and sit in table T024D which is meant for MRP controllers created in the SAP system.
This in-turn creates a customizing request which can be accessed using SE09/SE10.
No comments:
Post a Comment