You use this program to create a resource load profile that you can view using the Resource Planning Query or Resource Planning Schedule programs.
This enables you to assess the load on critical constraints caused by the current MPS (or the direct product demand that exists at this planning level, if you are not using an MPS).
You can create resource loads from forecasts, sales orders and from the build schedule for MPS items.
| Field | Description |
|---|---|
| Close | Select this to exit the program without creating the demand schedules. |
| Start Processing | Select this to create the demand file according to the options selected. |
| Select this to print the information currently displayed in the Report pane. | |
| Save Form Values | This option is only enabled in Design mode (see Automation Design). Your selections are saved and applied when the program is run in automated mode. |
| Field | Description |
|---|---|
| Processing options | |
| Include master production schedule | Select this to extract the demand for MPS items from the build schedule file, as well as any demand for non-MPS items from any other file(s) selected. |
| After processing completed | These options are displayed within programs that can be automated. They enable you to indicate the action you want to perform once processing is complete (see Automation Design). |
The results of the processing function you selected are displayed in this pane once processing is complete (unless you enabled the option to close the application from the After processing completed section). You use this section to print or email this information.
The program optionally runs through the Master Production Schedule file, extracting the resource parent code for each stock code. This is then used to read all the resource components attached to the parent code.
Each resource component encountered is output to the demand file. The demand quantity is calculated by multiplying the production schedule quantity to supply by the quantity per held in the resource structure file.
Parent codes with no resource components are listed as errors (if an error log is required). Any stock code with invalid resource parent codes is ignored.
The Resource Explosion program completes the following phases:
- Processing Build schedule file
- Processing Forecast file
- Processing Sales order file
This phase is performed only if you enabled the option: Include > Master production schedule on the main Resource Explosion screen.
In addition, if you enabled the option: Build schedule at the Include in requirements calculation field (Requirements Planning Setup) then the Master production schedule option is selected by default.
During this phase, the resource parent for each build schedule record is used to extract the demand on its components.
If the item is a planning bill, then the program reads the first level of its structure and extracts details in the above manner, also checking for MPS and non-MPS items.
This phase is performed only if you enabled the option: Forecasts at the Include in requirements calculation field (Requirements Planning Setup).
During this phase the resource parent for each forecast record is used to extract the demand on its components. The record is ignored if its resource parent is blank.
If you enabled the option: Build schedule at the Include in requirements calculation field (Requirements Planning Setup) then only non-MPS items are processed during this phase.
This phase is performed only if you enabled the option: Sales orders at the Include in requirements calculation field (Requirements Planning Setup)
This phase loads the resources for sales order merchandise lines (both stocked and non-stocked).
If you enabled the option: Build schedule at the Include in requirements calculation field (Requirements Planning Setup) then only non-MPS items are processed during this phase.
Sales orders in a status of S, 0, 1, 2, 3, 4 or 8 are processed.
For stocked items, the resource parent code (if defined) is extracted from the inventory master file. For non-stocked items, the stock code entered on the sales order line is used as the resource parent.
-
If you assigned a default resource parent to stock items (Stock Code Maintenance) then, after the addition of a forecast and/or build schedule, you must maintain the build schedule to add the resource to each build schedule line before running this program.
Electronic Signatures provide security access, transaction logging and event triggering. This enables you to increase control over your system changes.
Access to the following eSignature transactions within this program can be restricted at Operator, Group, Role or Company level. You configure this using the Electronic Signatures program.
| eSignature Transaction | Description |
|---|---|
| MRP Resource explosion |
Controls access to the Start Processing function in the Resource Explosion program. |
Inserting Application Help
You would typically follow this procedure to display help for the current program in a customized pane that can be pinned to the program window.
Information includes step-by-step instructions for the various functions available within the program, including a brief overview of what the program does, what setup options are required and how to personalize the program.
-
Open the program for which you want to insert application help into a customized pane.
This functionality is only available for a program that has panes.
-
Right-click any form field.
You can also click the triangle menu icon that appears in the title area of a pane.
-
Select Insert Application Help from the context-sensitive menu.
The application help appears in a pane within your program. You can reposition the pane using the docking stickers or pin it to the program window.
Removing the Application Help pane
If you no longer want to display application help in a pane for your current program, you can simply remove it.
-
Select the Close icon in the right-hand corner of the application help pane.
-
Confirm that you want to delete the pane.