|
xTuple ERP Reference Guide |
|
|
xTuple ERP Reference Guide |
| 12.3.2. Planner Codes | ||
|---|---|---|
 | 12.3. Master Information |  |
Planner codes are used to identify items that fall under the jurisdiction of planners—that is, employees responsible for planning, scheduling, or procurement. Here are some tips for creating and managing your planner codes:
Create your planner codes using a logical, hierarchical structure. This will make it easier to retrieve planner code information in the future.
If you want requirements to be created for planned work orders, the option Automatically Explode Planned Orders must be selected. If not selected, planned work orders will not be exploded. This means that planned orders for lower level material requirements will not be generated when MRP is run.
If you are running MRP by planner code, the explosion level setting may not make a difference—depending on how your planner codes are assigned. For example, if all your items fall within the same planner code, planned orders will be generated for all levels of requirements—regardless of whether single or multiple level explosion is set. The same does not hold true when running MRP by item.
To access the master list of planner codes, go to . The following screen will appear:
The Planner Codes screen displays information on all existing planner codes, including planner code and planner code description.
To create a new planner code, select the button. The following screen will appear:
When creating a new planner code, you are presented with the following options:
Enter a code to identify the planner code.
Enter a brief description of the planner code.
This option only applies if you are using the MRP exceptions feature set for planning purposes. If selected, unreleased work orders and purchase orders will be automatically rescheduled based on any existing MRP exceptions when MRP is run. If you are using MRP exceptions and would prefer to reschedule orders manually, do not select this option.
This option only applies if you are using the MRP exceptions feature set for planning purposes. If selected, unreleased work orders and purchase orders will be automatically deleted based on any existing MRP exceptions when MRP is run. If you are using MRP exceptions and would prefer to delete orders manually, do not select this option.
Select one of the following if you want planned work orders to be exploded automatically:
This option specifies that when planned work orders are exploded, requirements should be created for the parent planned work order only.
This option specifies that requirements should be created for both parent and child planned work orders.
| |  | |
| 12.3.1. Characteristics |  | 12.3.3. Reason Codes |
