Understanding the Costing Exceptions Report

Before you run a cost simulation, run the Costing Exceptions report (R30801). Costing exceptions are problems that are associated with an item and result in error messages.

The report uses the error messages from the Costing Exceptions Error Messages UDC table (30/EM). The error messages are hard-coded; therefore, you cannot add or change these error messages. You can define the severity level for each error message as appropriate for the company, using the Description 02 field in the UDC table. For example, if having labor costs of zero is an important exception in the company, you could assign that error message a high severity level. You can indicate in the processing options the minimum level of error messages that you want included in the report.

This table identifies the changeable, default severity setting for each of the hard-coded error messages:

Severity Level	Description
Severity level 10	No accounting lot size for setup. Setup hours are zero. Machine hours are zero. Labor hours are zero.
Severity level 20	Purchase part with bill of material. Bill of material components with no quantity.
Severity level 30	No cost component - material cost. No work center - labor rate. No work center - setup labor rate. No work center - labor variable overhead rate. No work center - labor fixed overhead rate. No work center - machine run rate. No work center - machine variable overhead rate. No work center - machine fixed overhead rate. Purchased item without purchased cost.
Severity level 40	No rates for work center.
Severity level 50	Manufactured item with no bill of material. Manufactured item with no routing.

You should correct the problems and run the Costing Exceptions report again before you create a simulated rollup.

(Release 9.2 Update) The Costing Exception program uses the master routing for the item from the Routing Master table if all of these conditions are met:

• The Master Routing field in the Manufacturing Constants form is set to Y for the branch

• You have defined a cross-reference item for the parent item on the master routing.

  You must define the cross-reference item with a cross-reference type of MR. The Address field must be blank.

• You have defined an item routing for the cross-reference item.

• You have specified a branch/plant value for the parent item.

• The parent item and the cross-reference item must exist in the same branch/plant.

The system checks for a cross-reference for an item in the branch/plant. If it finds a cross-reference, the program uses master routing. If it does not find a cross-reference, the system uses the routing defined for the parent item and checks the next item in the branch/plant for a cross-reference. The absence of any cross-reference items in the same branch as the parent items implies that master routing does not exist for the selected branch/plant.