WILLIAMS PLT BEL REQUIREMENTS PLANNING 5/16/95
DSP01 REQUIREMENTS PLANNING GENERATION REQUEST DETAIL
ACTUAL
Submit Request
Planning Mode S
Generation Days 100
Print Planning Action Report Y Select Daily MS Parts N
RP Generation Run Date 051695 Select RP Parts Y
Run CONBON Analysis N Select Service Parts N
Sum Flow Reqmnts N Forecast Consumption Period 1
Printer Location QPRINT Multi-Level Selective Mode Y
MRP Firm Horizon Date or Days 051695 JIT Firm Horizon Date or Days
051695
Default Comm Code Print Options:
Plan JIT Plan Prt Excep Prt Beyond Planned Order Re-Sched Re-Sched
Fact Days Only Horizon Exception Early Late
.0 30 N Y Y 0 0
MO Prefix/Number Y 079983 RQ Prefix/Number R 004535 TR Prefix/Number T 000324
F2=Command F3=Exit F4=Prompt F9=Comm Code Prt
F17=New Plant F19=Sim Request
This screen is used to enter the parameters that control the type of generation to be performed and the amount of printed output for the Planning Action Report. The screen is initially displayed with the values entered for the last generation.
PLANT
Required. Used to identify the plant in which maintenance/inquiry will be done. The plant must be valid, and you must be authorized to the manufacturing company/warehouse associated with the plant (Reference File category 409). Defaults to the plant assigned to your user ID, but may be changed by pressing F17.
SUBMIT REQUEST
Optional. Enter an 'X' to submit a request to run MRP for this plant. This 'X' will be displayed until the MRP job is released from the Requirements Planning Processing Menu and is successfully completed. You may cancel the request for this plant by blanking out the 'X' before the MRP job is run.
PLANNING MODE
Required. The valid values are:
F - Full Generation. All requirements planning items will be replanned during the generation process.
N - Net Change Generation. Process only those items which have been flagged for replanning since the last run. Typical causes of replanning include:
- Unexpected changes in demand
- Unexpected changes in supply
- Unplanned inventory activity
- Changes to the standard bill of material
- Changes to item lead time specifications
- Changes in planning policies
S - Selective generation by part, planner, or family.
GENERATION DAYS
Required. Enter a number that is greater than zero. This number is added to the RP Generation Run Date to determine the planning horizon. During the planning horizon, RP analyzes requirements and supply. If requirements exist beyond the planning horizon, RP does not analyze them. Supply beyond the planning horizon will be analyzed only if the projected inventory becomes negative within the planning horizon. Otherwise, RP determines the sum of each supply but does not analyze them.
NOTE: If the Net Change flag is set to 2, which means that RP must replan, the planning horizon is set to the last planned order due date, if the last planned order due date is greater than the planning horizon that was calculated previously. This procedure ensures that all planned orders are replanned.
PRINT PLANNING ACTION REPORT
Required. Valid values are:
Y - Print the Planning Action Report
N - Do not print the Planning Action Report
All planning action information is stored in work files on the system. In order to see the planning action information for a part or group of parts without rerunning the RP Generation, you can select either the planning action detail or summary reports.
SELECT DAILY MASTER SCHEDULED PARTS
Required. Enter a Y (yes) if you wish to have Requirements Planning include any applicable daily master scheduled parts in a full, net change, or selective Requirements Planning Generation. Enter a N (no) if you do not wish to have daily master scheduled parts included in a full, net change, or selective Requirements Planning Generation.
REQUIREMENTS PLANNING GENERATION RUN DATE
Required. Must be either today's or tomorrow's date, specified in the Date Format defined on Reference File category 049.
SELECT REQUIREMENTS PLANNING PARTS
Required. Enter a Y (yes) if you wish to have Requirements Planning include any applicable requirements planning parts in a full, net change, or selective Requirements Planning Generation. Enter a N (no) if you do not wish to have Requirements Planning include any applicable requirements planning parts in a full, net change, or selective Requirements Planning Generation.
RUN CONBON ANALYSIS
Required (if CONBON is installed). Must be either:
Y - Execute CONBON Analysis for this plant.
N - Do not run CONBON Analysis for this plant.
SELECT SERVICE PARTS
Required. Enter a Y (yes) if you wish to have Requirements Planning include any applicable service parts in a full, net change, or selective Requirements Planning Generation. Enter a N (no) if you do not wish to have Requirements Planning include any applicable service parts in a full, net change, or selective Requirements Planning Generation.
SUMMARIZE FLOW REQUIREMENTS
Required (if JIT module is installed). Must be either:
Y - Print on the Planning Action Report one summarized flow requirement per day.
N - Print on the Planning Action Report each flow requirement individually per day.
The purpose of this feature is to reduce the amount of output generated by the Planning Action Report. If the summarize option ('Y') is chosen, the detail for individual flow requirements can still be examined through the Requirements Review option on the Requirements Planning menu.
FORECAST CONSUMPTION PERIOD
Required. This field defines whether forecast will be consumed over weeks, months, days, or user-defined periods. Valid values are:
1 - Weeks
2 - Months
3 - User-defined periods
4 - Days
N - No forecast consumption
If you do not wish to run forecast consumption during Requirements Planning Generation, enter N (no) in this field. Note: target inventory processing will not occur unless forecast consumption is requested. Also, overplanning may result if you do not request the forecast consumption period to be the same as the forecast period for the items being processed.
PRINTER LOCATION
Optional. Enter the printer location (output queue) where the RP Planning Action Report should be printed. It must be a valid system printer which is defined on Reference File category C07 (Printer Locations). If left blank, it will default to the printer location last used when the generation was requested for the given plant.
MULTI-LEVEL SELECTIVE MODE
Required if the Planning Mode is S (Selective). Valid values are Y (yes) or N (no). If you enter Y in this field, the components of the parts that match the selection criteria that you enter on the Selective Requests screen (RP120S01) will also be reanalyzed. If you enter N, the components will not be replanned/reanalyzed unless the replanning of the parent part causes a demand change affecting any component parts.
MRP FIRM HORIZON DATE OR DAYS
Required. Within the firm horizon, Requirements Planning neither generates messages nor creates planned orders. It does, however, determine the supply and subtract requirements from the projected inventory. If the projected inventory becomes negative within the firm horizon, Requirements Planning sends a message on the first day after the end of the firm horizon. It also creates or updates planned orders with a due date equal to the end firm horizon date.
Enter a number in either the Date or Days portion of the field.
The MRP end firm horizon date must:
o be a valid date
o exist on the calendar file
o be less than, equal to, or greater than the requirements planning run date
o be less than the planning horizon
o be less than the last date of the calendar file
If you enter a number in the Days portion of the field, Requirements Planning will add those number of days to the RP Generation Run Date to obtain the Firm Horizon. You may enter a negative number in the Days portion of the field (type the number first and then enter the negative sign). NOTE: If a number was entered in the RP Firm Horizon Days field on Part Master Maintenance, that number takes precedence over the number that you may have entered in the MRP Firm Horizon Date or Days field.
JIT FIRM HORIZON DATE OR DAYS
Required. Within the firm horizon, Requirements Planning neither generates messages nor creates planned flow authorizations. It does, however, determine the supply and subtract requirements from the projected inventory. If the projected inventory becomes negative within the firm horizon, Requirements Planning sends a message on the first day after the end of the firm horizon. It also creates or updates planned flow authorizations with a due date equal to the end firm horizon date.
Enter a number in either the Date or Days portion of the field.
The JIT end firm horizon date must:
o be a valid date
o exist on the calendar file
o be equal to or greater than the requirements planning run date
o be less than the planning horizon
o be less than the last date of the calendar file
If you enter a number in the Days portion of the field, Requirements Planning will add those number of days to the firm horizon. NOTE: If a number was entered in the RP Firm Horizon Days field on Part Master Maintenance (DE100S05), that number takes precedence over the number that you may have entered in the JIT Firm Horizon Date or Days field.
This field appears only if the JIT module is installed.
PLANNING FACTOR DEFAULT
Required. This filter is multiplied by each part's cumulative lead time to establish the order action horizon date which limits the amount of detail printed on the Planning Action Report (RP520B). If zero is entered, all detail is printed. This figure is used only for MRP production type parts without an associated commodity code.
JIT PLANNING DAYS DEFAULT
Required. This filter is added to the RP run date to determine the planning horizon for JIT parts without a commodity code.
PRINT EXCEPTIONS ONLY
Required. Valid values are:
Y - Print only those items which have order action messages on the Planning Action Report.
N - Print all items processed on the Planning Action Report.
This filter is used only for parts without an associated commodity code.
PRINT BEYOND HORIZON
Required. Must be either:
Y - Print beyond the RP Horizon Date.
N - Do not print beyond the RP Horizon Date.
This filter is used only for parts without an associated commodity code.
PLANNED ORDER EXCEPTION
Required. Must be either:
Y - Planned orders are treated as exceptions.
N - Planned orders are not treated as exceptions.
This filter is used only for parts without an associated commodity code.
RE-SCHEDULE EARLY FILTER
Required. Used to suppress action messages for minor changes in schedule. Expedite messages will be printed only if the order should be brought forward by a number of days which is greater than the filter. This filter is used only for parts without an associated commodity code.
RE-SCHEDULE LATE FILTER
Required. Used to suppress action messages for minor changes in schedule. Defer messages will be printed only if the order should be delayed by a number of days which is greater than the filter. This filter is used only for parts without an associated commodity code.
MANUFACTURING ORDERS PREFIX
Display only. Shows the prefix which will be used by MRP when adding planned manufacturing orders to the schedule. The prefix/starting number can be specified and modified through Reference File category 465.
MANUFACTURING ORDERS STARTING NUMBER
Display only. Shows the first order number that will be used when adding planned manufacturing orders to the schedule. The system will automatically track the next available number. The next available MO number is also found on Reference File category 465.
REQUISITIONS PREFIX
Display only. Shows the prefix which will be used by MRP when adding planned purchase requisitions. The prefix/starting number can be specified and modified through the Reference File category 465.
REQUISITIONS STARTING NUMBER
Display only. Shows the first order number that will be used by MRP when adding planned purchase requisitions. The system will automatically track the next available number. The next available RQ number is also found on Reference File category 465.
TRANSFER REQUISITIONS PREFIX
Display only. Shows the prefix which will be used by MRP when adding planned transfer requisitions. The prefix/starting number can be specified and modified through the Reference File category 465.
TRANSFER REQUISITIONS STARTING NUMBER
Display only. Shows the first requisition number that will be used by MRP when adding planned transfer requisitions. The system will automatically track the next available number. The next available TR number is also found on Reference File category 465.
COMMAND KEYS
Enter - Process the generation request.
F2 - Display a window where a fast path option or mnemonic can be entered. Fast path allows the next menu selection to be made directly from this screen. When the window is displayed, pressing F3 will remove it.
F3 - Exit without updating the request.
F4 - Display a list of values for the field where the cursor is positioned. If you select one of the items from the list, it will be returned to the application screen.
F9 - Access Commodity Code Print Parameters (RP115S01) which will allow you to modify the commodity codes on Reference File category D03 bypassing Reference File Maintenance.
F17 - Change the plant for which the RP Generation will be requested.
F19 - This function key allows you to toggle between the actual request for Requirements Planning Generation or the simulation request for Requirements Planning Generation. Note that either the actual or the simulated Requirements Planning Generation can be run for a plant at one time; however, the actual and the simulated Requirements Planning Generation can be run for different plants simultaneously.
|