Do you have any question about this error?
Message type: E = Error
Message class: MD - Material Requirements Planning (MRP)
Message number: 106
Message text: Planned ind. reqmts version & has already been assigned
You cannot allocate a version number twice.
When you allocate a version to a scenario, you define which versions
are planned in long-term planning. If you heve created several versions
for your materials, you can stipulate that only one or several specific
versions are planned in long-term planning.
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.
MD106
- Planned ind. reqmts version & has already been assigned ?The SAP error message MD106 indicates that there is an issue with the planned independent requirements (PIR) version in the system. Specifically, it means that the planned independent requirements version you are trying to use has already been assigned to a different planning area or is already in use, which prevents you from assigning it again.
Cause:
- Duplicate Assignment: The planned independent requirements version you are trying to assign is already assigned to another planning area or is in use.
- Configuration Issues: There may be configuration settings in the planning area that restrict the assignment of the PIR version.
- Data Integrity Issues: There could be inconsistencies in the data that lead to this error.
Solution:
Check Existing Assignments:
- Go to the transaction code
MD61
(Create Planned Independent Requirements) orMD62
(Change Planned Independent Requirements) and check if the version is already assigned to another planning area.- Use transaction
MDM1
to check the configuration of the planning area and see if the version is already in use.Change Version Assignment:
- If the version is indeed assigned to another planning area, you may need to either:
- Use a different version that is not currently assigned.
- Remove the assignment from the other planning area if it is no longer needed.
Review Configuration:
- Check the configuration settings in the planning area to ensure that the version assignment rules are set correctly.
- You can do this through the transaction
SPRO
(SAP Reference IMG) and navigate to the relevant sections for planning area configuration.Data Consistency Check:
- Run consistency checks to ensure that there are no data integrity issues in the planning area. This can often be done through specific reports or transactions related to planning.
Consult Documentation:
- Review SAP documentation or notes related to the error message MD106 for any specific guidance or updates that may apply to your version of SAP.
Related Information:
Transaction Codes:
MD61
: Create Planned Independent RequirementsMD62
: Change Planned Independent RequirementsMDM1
: Maintain Master DataSPRO
: SAP Reference IMG for configurationSAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
Support: If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
By following these steps, you should be able to resolve the MD106 error and successfully manage your planned independent requirements in SAP.
Get instant SAP help. Start your 7-day free trial now.
MD105
Planning scenario & exists already
System Response The planning scenario cannot be created twice under the same name. The system issues an error message and will not allow you to conti...
MD104
Planning scenario & was saved
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MD107
Simulation version is same as the version to be replaced
What causes this issue? The planned independent requirements version for long-term planning is to be replaced by itself. A version can only be replac...
MD108
Finish date lies before the start date
What causes this issue? The end date of the validity period lies before the start date.System Response The system issues an error message and will n...
Click on this link to search all SAP messages.