Message type: E = Error
Message class: REMPT - Message Class for REM Planning Table (Rel. 99)
Message number: 312
Message text: Scheduling not executed for plnd orders of material &1, version &2
The planned order was not scheduled.
This may be due to one of the following reasons, for example:
The scheduling level (detailed or rate-based planning) you used to
access the planning table and the one used for scheduling are not the
same.
No suitable routing could be found.
One possibility of finding out what is causing the problem is:
To access the planned order from the detailed dialog box in the table
via "Change" and reschedule the planned order. Check the scheduling log
by choosing "Goto --> Scheduling log". More information is displayed in
the log's warning or error messages.
You define the scheduling levels for the various types of planned
orders in Customizing.
<DS:TRAN.OPU5>Proceed with function</>
You must enter the routings in the production version in the material
master record (MRP 4 screen) according to the scheduling level settings
in Customizing (determine scheduling and capacity requirements via
detailed or rate-based planning).
<DS:TRAN.MM02>Proceed with function</>
If you have made any changes, you have to restart the planning table to
activate the changes.
Error message extract from SAP system. Copyright SAP SE.
REMPT312
- Scheduling not executed for plnd orders of material &1, version &2 ?The SAP error message REMPT312 indicates that scheduling was not executed for planned orders of a specific material and version. This error typically arises in the context of production planning and scheduling within the SAP system.
Cause: The error can be caused by several factors, including: Missing or Incorrect Master Data: The material master or the routing for the planned order may not be set up correctly. This includes missing production versions or incorrect settings in the material master. Scheduling Parameters: The scheduling parameters for the planned order may not be defined correctly, leading to the inability to execute scheduling. Order Status: The planned order may be in a status that does not allow scheduling (e.g., it may be locked or not released). Capacity Constraints: If there are capacity constraints in the production resources, scheduling may not be possible. Version Control: The version specified in the planned order may not be valid or may not exist in
Get instant SAP help. Sign up for our Free Essentials Plan.
REMPT311
Problems occurred when scheduling plnd ord. for mat. &1, version &2
What causes this issue? Problems occurred when scheduling the planned order. This may be due to one of the following reasons, for example: The schedu...
REMPT310
Scheduling error: &
What causes this issue? A problem occurred when determining the column in which the planned order is to be created.How to fix this error? This probl...
REMPT313
Scheduling levels not maintained in Customizing
What causes this issue? Problems occurred when scheduling the planned order. This may be as a result of the following: You have not maintained Custom...
REMPT314
No capacity requirements were determined (see Customizing)
What causes this issue? No capacity requirements were created for the planned order. This may be as a result of the following: It is set in Customizi...
Click on this link to search all SAP messages.