Do you have any question about this error?
Stop Googling SAP errors. Use our Free Essentials plan instead - instant AI help, no credit card needed. Start Now →
Message type: E = Error
Message class: IW - Order Processing
Message number: 136
Message text: No purchase requisition exists for component &2 operation &1
You want to display the <GL:purchase_requisition>purchase requisition</>
for <GL:component>component</> &V2& in <GL:operation>operation</> &V1&.
However, no purchase requisition exists for this component, since it
does not need to be <GL:external_procurement>procured externally</>.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE 'KEINE-FUNKTION' OBJECT DOKU ID TX LANGUAGE E
Error message extract from SAP system. Copyright SAP SE.
IW136
- No purchase requisition exists for component &2 operation &1 ?The SAP error message IW136 "No purchase requisition exists for component &2 operation &1" typically occurs in the context of maintenance orders or production orders when the system is unable to find a corresponding purchase requisition for a specific component associated with an operation. Here’s a breakdown of the cause, potential solutions, and related information:
Cause:
- Missing Purchase Requisition: The most straightforward cause is that there is no purchase requisition created for the specified component in the operation.
- Incorrect Configuration: The configuration of the material or the order may not be set up correctly, leading to the absence of a purchase requisition.
- Data Entry Errors: There may be errors in the data entry for the maintenance or production order, such as incorrect component assignment.
- Status of the Order: The order may be in a status that does not allow for the creation of purchase requisitions.
- Component Not Defined: The component may not be defined in the bill of materials (BOM) or may not be linked correctly to the operation.
Solutions:
- Create Purchase Requisition: If the purchase requisition is genuinely missing, you can create it manually. This can be done through transaction codes like ME51N (Create Purchase Requisition).
- Check BOM and Routing: Ensure that the component is correctly defined in the BOM and that it is linked to the correct operation in the routing.
- Review Order Status: Check the status of the maintenance or production order. If it is not in a status that allows for purchase requisitions, you may need to change the status or take appropriate actions to allow for requisition creation.
- Verify Component Assignment: Ensure that the component is correctly assigned to the operation in the order. You can do this by reviewing the order details in transaction IW32 (Change Order) or CO02 (Change Production Order).
- Check Configuration Settings: Review the configuration settings related to purchasing and materials management to ensure that everything is set up correctly.
- Consult Documentation: If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the IW136 error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
IW135
The relationships for the operations selected will be deleted
What causes this issue? You selected certain operations of a <GL:maintenance_task_list>task list</> to copy them to the <GL:maintenanc...
IW134
No purchase requisition exists for operation &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
IW137
No relationships possible for sub-operations
What causes this issue? You are trying to maintain <GL:relationship>relationships</> for one or more sub-operations. The system issues an...
IW138
No relationships exist for the operation
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.