Entering Additional System Information

Access the Additional System Information form.

You must complete the fields on this form to specify the rules by which the system plans for, orders, and issues parts.

Order Policy Code

Enter a value from UDC H41/OP (Order Policy Code) that specifies the rules for inventory reordering in the Requirements Planning and Procurement systems. Values are:

0: Reorder point (Not planned by MPS/MRP/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.

Note:

These values are hard-coded.

You should enter a 1 in this field.

Issue Type Code

Enter a value from UDC 41/IT (Issue Type Code) that indicates how the system issues each component in the bill of material from stock.

In Shop Floor Management, the issue type code indicates how the system issues a part to a work order. Values are:

Blank: Shippable end item.

I: Manual issue.

F: Floor stock (there is no issue).

B: Backflush (when the part is reported as complete).

P: Preflush (when the parts list is generated).

U: Super backflush (at the pay-point operation).

S: Subcontract item (send to supplier).

You can issue a component in more than one way within a specific branch/plant by using different codes on the bill of material and the work order parts list. The bill of material code overrides the branch/plant value.

Note: With the exception of floor stock items, such as small hardware, fasteners, and so on, you should enter an I in this field to indicate a manual issue for maintenance parts.

Planning Fence Rule

Enter a value from UDC 34/TF (Time Fence Rule) that the system uses in conjunction with the Planning Time Fence Days field to determine how forecast demand or actual customer demand is used. For example, you can enter these values:

S: Tells the system to plan using customer demand before the time fence and forecast after the time fence.

F: Tells the system to plan using forecast before the time fence and forecast plus customer demand after the time fence.

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 five days. After five days, the system uses the forecast for the regeneration.

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.

Planning Fence

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 time fence rule is S (customer demand before the time fence, forecast after the time fence), the generation start date is January 03, and the planning time fence is 3 days, the system plans using customer demand through January 06. Beginning on January 07, the system plans using the forecast.

Note:

Notice that 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 Shop Floor Calendar form.

For purchased items, the system counts calendar days.

Freeze Fence

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 January 03, and the freeze time fence is 3 days, the JD Edwards EnterpriseOne Requirements Planning system does not generate messages with required dates that are less than or equal to January 06.

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 Shop Floor Calendar form.

For purchased items, the system counts calendar days.