Error exception messages
Error exception messages are item exception messages that indicate errors occurring during a planning run.
Some errors are relatively easy to solve, for example, by supplying a default value or parameter where expects one. In other cases, however, the error can be of a more serious nature, and can lead to failure of the planning as a whole.
Fatal Error
An error has occurred that LN cannot recover from. The exception message is given to specify the fatal error. Examples of a fatal error:
- The program is running out of memory
- An internal sort failed
In most cases the session that started the exception message generation will be aborted. If any planning was generated, it might not be valid.
This exception message is not related to a specific item.
RPT Planning Failure
While trying to generate orders for repetitive items, no default order quantity could be found.
The default order quantity for repetitive items is calculated in Manufacturing, on the basis of:
- The basic capacity of the bottleneck work center for the repetitive item in question, as specified in the Item - Routings (tirou1101m000) session.
- The basic capacity by resource unit for this bottleneck work center, as specified in the Work Centers (tirou0101m000) session.
No Supplying Relationship
While trying to generate a planned distribution order, LN could not find any supplying relationships for the item involved. As a result, no planned distribution order is generated.
You can define supplying relationships for a plan item in the Supplying Relationships (cprpd7130m000) session.
No Supplying Business Partner
While trying to generate a planned purchase order, LN could not find any suppliers for the item involved. However, the planned purchase order is still generated.
You can define suppliers for a plan item in the Item - Purchase session.
Item Error
An item-specific error occurred. The nature of the error is specified in the exception message. In most cases the error is such that the planning for the specified item has failed and cannot be trusted.
Item planned after last allowed order date
The finish date of a planned order falls after the last allowed order date.
You can define a general value for the last allowed order date in the Last allowed Order Date field in the Items - Ordering (tcibd2100m000) session.
You can also specify a warehouse-specific value in the Item Data by Warehouse (whwmd2510m000) session that applies if the item is delivered from that warehouse.
No Items for Plan Unit
A particular plan unit is empty, that is, no plan items have been assigned to it.
To assign a plan item to a plan unit in the Items - Planning (cprpd1100m000) session, you can specify the plan unit in the Master Plan Unit field.
This type of exception message is not related to a specific item.
No WLC Parameters Defined
A particular item is assigned to a plan unit for which the Master Planning Method is Workload Control, but the plan unit's WLC parameters have not been defined.
You can define the WLC parameters in the Work Load Control Parameters (cpwlc2101m000) session.
Insufficient Capacity
The production plan is decreased due to insufficient free capacity on one of the resources defined in the bill of critical capacities. This type of exception message is generated in the workload control (WLC) planning engine.
Insufficient Materials
The production plan is decreased due to a lack of one of the components specified in the bill of critical materials for a certain plan item. This type of exception message is generated in the workload control (WLC) planning engine.
Planning Failed
Planning has failed because the required quantity could not be planned. The nature of the error is specified in the exception message.
Project
The Generate Order Planning (Item) (cprrp1220m000) session can only handle PCS Project with the status Active or Simulated. When executing Generate Order Planning (Item) for customized items that belong to a PCS project that is not Active or Simulated, this exception message is logged.
Specification
During the generation of the order planning the application detects an incorrect setting in Terms and Conditions. The nature of the error is specified in the exception message.