How To Fix C5705 - Resource & does not exist in plant &. Operation & was copied w/o resource

C5705 - Overview

• Message type: E = Error

• Message class: C5 - Master Recipe

• Message number: 705

• Message text: Resource & does not exist in plant &. Operation & was copied w/o resource

What causes this issue?

The template you want to copy contains resource &V1& as the primary
resource for operation &V3&. However, this resource does not exist in
plant &V2& of the new recipe.
Operation &V3& along with its phases are created without a primary
resource in the new recipe.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If you want to use a different primary resource in plant &V2&:
Go to the operation overview of the new recipe and assign the resource
to operation &V3&.
If you want to copy the entire template to plant &V2&:
RESET N2
Exit the recipe without saving.
Create resource &V1& in plant &V2&.
<DS:TRAN.CRC1>Create Resource</>
Start the copy function again.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message C5705 - Resource & does not exist in plant &. Operation & was copied w/o resource ?

  The SAP error message C5705 indicates that a resource (such as a machine, labor, or tool) does not exist in the specified plant for the operation being processed. This error typically occurs in the context of production planning or scheduling when trying to create or modify a production order, routing, or work center.
  
  Cause:
  
  
  Missing Resource: The resource specified in the operation does not exist in the plant you are working with. This could be due to:
  
  The resource was never created in the system.
  The resource was deleted or marked as inactive.
  The resource is not assigned to the specified plant.
  
  
  
  Incorrect Configuration: The configuration of the routing or work center may not be set up correctly, leading to the system not recognizing the resource.
  
  
  Data Inconsistency: There may be inconsistencies in the master data, such as the resource being assigned to a different plant or not being properly linked to the operation.
  
  
  
  Solution:
  
  
  Check Resource Existence:
  
  Go to