Do you have any question about this error?
Message type: E = Error
Message class: CURTO1 - PDS Generation (ERP system)
Message number: 017
Message text: No BOMs found for the selection criteria
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
CURTO1017
- No BOMs found for the selection criteria ?The SAP error message CURTO1017, which states "No BOMs found for the selection criteria," typically occurs when a user attempts to retrieve Bill of Materials (BOM) data but the system cannot find any BOMs that match the specified selection criteria. This can happen in various transactions related to BOMs, such as when creating or displaying BOMs.
Causes:
- Incorrect Selection Criteria: The most common cause is that the selection criteria entered (such as material number, plant, or BOM usage) do not match any existing BOMs in the system.
- BOM Not Created: The BOM for the specified material or plant may not have been created yet.
- BOM Status: The BOM may be inactive or not released, which can prevent it from being found.
- Authorization Issues: The user may not have the necessary authorizations to view the BOMs for the specified criteria.
- Data Consistency Issues: There may be inconsistencies in the data, such as missing entries in the BOM master data.
Solutions:
- Check Selection Criteria: Verify that the selection criteria you are using are correct. Ensure that you are entering the correct material number, plant, and other relevant fields.
- Create BOM: If no BOM exists for the material, you may need to create one using the appropriate transaction (e.g., CS01 for creating a BOM).
- Check BOM Status: Ensure that the BOM is active and released. You can check the status in the BOM master data.
- Authorization Check: Confirm that you have the necessary authorizations to view the BOMs. If not, contact your SAP security administrator.
- Data Consistency: If you suspect data issues, you may need to run consistency checks or consult with your SAP support team to resolve any underlying data problems.
Related Information:
If the issue persists after checking these aspects, it may be beneficial to consult with your SAP support team or refer to SAP community forums for further assistance.
Get instant SAP help. Start your 7-day free trial now.
CURTO1016
Test mode only supported as of APO 4.0
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CURTO1015
Recipe integration with PP/DS PDS only possible as of APO 4.0
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CURTO1018
An active integration model does not exist for &1 &2 &3 &4
What causes this issue? An active integration model of the type 'BOM' must exist for the transfer of BOMs to production data structures usi...
CURTO1019
No errors for PP/DS PDS for material &1, plant &2
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.