Manufacturing Data

Enter a user-defined code from UDC table (H41/OP) that specifies the rules for inventory reordering in the JD Edwards EnterpriseOne Requirements Planning system and the JD Edwards EnterpriseOne Procurement system. The hard-coded values are:

0: Reorder point [not planned by Master Production Schedule (MPS), Material Requirements Planning (MRP), or Distribution Requirements Planning (DRP)].

1: Lot-for-lot or as required.

2: Fixed order quantity.

3: Economic order quantity (EOQ).

4: Periods of supply.

5: Rate scheduled item.

Enter a hard-coded order policy code. Values are:

2: Fixed order quantity.

4: Periods of supply. This value represents the number of days of net requirements that the system uses to determine order size.

5: Rate scheduled item. This value represents the desired inventory level. When the ending available quantity is less than the desired inventory level, the system then issues an increase rate to message. When the ending available quantity is greater than the desired inventory level, the system then issues a decrease rate to message.

Note: If you enter a order policy code other than 2,4, or 5, the value has no significance in MRP.

Enter a user-defined code from UDC table (H41/MP) that indicates how MPS, MRP, or DRP processes this item. The hard coded values are:

0: Not planned by MPS, MRP, or DRP.

1: Planned by MPS or DRP.

2: Planned by MRP.

3: Planned by MRP with additional independent forecast.

4: Planned by MPS, Parent in Planning Bill.

5: Planned by MPS, Component in Planning Bill.

Enter a user-defined code from UDC table (34/TF) that the system uses in conjunction with the Planning Time Fence Days field to determine how forecast demand or actual customer demand is used. Values are:

C: Customer demand before, greater of forecast or customer demand after.

F: Forecast before, forecast plus customer demand after.

G: Greater of forecast or customer demand before, forecast after.

S: Customer demand before, forecast after.

1: Zero before, forecast after.

3: Zero before, forecast plus customer demand after.

For example, if you enter 5 in the Planning Time Fence Days field and S in this field, then the system uses only customer demand for the regeneration for the first 5 days. After 5 days, the system uses the forecast for the regeneration.

Enter the number of days that the system uses in conjunction with the time fence rule to determine how the forecast is used. Enter the number of days after the start date when the time fence rule changes from the first rule to the second rule.

For example, if the planning fence rule is S, the generation start date is 01/03/05, and the planning time fence is three days, the system plans using customer demand through 01/06/05. Beginning on 01/07/05, the system plans using the forecast.

Note: The system does not count the generation start date; that is, the day after the generation start date is day 1.For manufactured items, the system counts working days, as defined in the calendar in the JD Edwards EnterpriseOne Shop Floor Management system. For purchased items, the system counts calendar days.

Enter the number of days from the generation start date within which the system does not generate action messages.

For example, if the generation start date is 01/03/05, and the freeze time fence is three days, the planning system does not generate messages with required dates that are before or equal to 01/06/05.

Note: The system does not count the generation start date; that is, the day after the generation start date is day one.For manufactured items, the system counts working days, as defined in the calendar in the JD Edwards EnterpriseOne Shop Floor Management system.For purchased items, the system counts calendar days.

Enter the number of days after the generation start date within which the system should display order messages.

For example, if the generation start date is 01/01/05, and the message time fence is 30 days, the system displays messages with dates before or equal to 01/31/05. The system does not display messages with dates of 02/01/05 or later. However, the planning horizon for orders continues past this date and is reflected in available-to-promise totals.

Note: The system does not count the generation start date; that is, the day after the generation start date is day one.For manufactured items, the system counts working days, as defined in the calendar in the JD Edwards EnterpriseOne Shop Floor Management system.For purchased items, the system counts calendar days.

Specify whether you want the system to suppress MRP messages. You can specify 0 or 1, regardless of whether the item is defined as MRP or Demand Flow. Values are:

0: Suppress MRP messages.

1: Do not suppress MRP messages.

Specify a user-defined code from UDC table (43/IR) that indicates whether an item is received at the time of inventory issues or whether the system uses the Receipt Routing Movement and Disposition program (P43250). Values are:

0: The system does not perform any actions.

1: The system receives an item when an inventory issue occurs.

2: The system uses the P43250 program when an inventory issue occurs.

Enter the time that is required before a consuming location has a replacement kanban available from its supplying location.

This value is used only for kanban card processing in the JD Edwards EnterpriseOne Shop Floor Management system.

Enter the quantity that determines the leadtime level for a manufactured item. Each of the routing steps for the item are extended by this quantity. For the system to calculate the leadtime level, the quantity in this field must be a value other than zero.

Enter a value that represents the leadtime for an item at its assigned level in the production process, as defined on Plant Manufacturing Data. The system uses this value to calculate the start dates for work orders using fixed leadtimes. Level leadtime is different for purchased and manufactured items:

Purchased: The number of calendar days that are required for the item to arrive at the branch/plant after the supplier receives the purchase order.

Manufactured: The number of workdays that are required to complete the fabrication or assembly of an item after all the components are available.

You can enter level leadtime manually on the Plant Manufacturing tab of the Additional System Information form, or you can use the Leadtime Roll up program to calculate it. To calculate level leadtime using the Leadtime Roll up program, you must first enter a quantity in the Manufacturing Leadtime Quantity field in the F4102 table.

Enter the total number of days that are required to build an item from its lowest level components to the final assembly. This value is the total of the level leadtimes for all manufactured items, plus the highest manufacturing leadtime for all its components.

If all components are purchased, the manufacturing leadtime equals the item's level leadtime. Purchased item leadtimes are not included in the calculation of manufacturing leadtimes.

You can enter the manufacturing leadtime manually, or you can have the system calculate it when you run the Leadtime Roll up program.

Enter the total number of hours that are required to build one unit as specified on the routing. This value is factored by the time basis code.

You can enter this value manually or you can have the system calculate it when you run the Leadtime Roll up program. The system overwrites this value when you run the Leadtime Roll up program.

The system uses this field to calculate start dates for work orders when you use variable leadtimes.

Enter the total number of days that are required to build an item from its lowest level components to the final assembly. The system calculates the value differently for manufactured and purchased items.

Manufactured: The total of all level leadtimes for all manufactured items, plus the highest cumulative leadtime of all its components.

Purchased: The item's level leadtime. Purchased item leadtimes are included in the calculation of cumulative leadtimes.

You can enter this value manually, or you can have the system calculate it when you run the Leadtime Roll up program.

Enter a user-defined code from UDC table (H41/MS) that determines whether the system uses fixed or variable leadtimes. This value works in conjunction with the value from either the Level Leadtime field or the Leadtime Per Unit field. Values are:

F: The system calculates work order start dates using the value from the Leadtime Level field.

V: The system calculates work order start dates using the value from the Leadtime Per Unit field.

Enter a code that represents the engineering drawing size. For example:

A: A-size drawing

D: D-size drawing

Enter a subset to the drawing number. The subset provides an additional description of the drawing and is useful if the system uses an engineering drawing as a reference for this item.

Enter an engineering drawing number. This number might be the same as the part or item number.