Resource Explosion

Toolbar and menu

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.
Print	Select this to print the information currently displayed in the Report pane.
Save Form Values	This option is only enabled in Design mode (Automation Design). Your selections are saved and applied when the program is run in automated mode. Form values and defaults are applied at operator level. They are not saved at role or group level.

Information

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 files 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).

Report

This pane displays the results of the processing function you selected once processing is complete (unless you selected the option to close the application from the After processing completed section).

Processing sequence

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

Processing Build schedule 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 option (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.

Processing Forecast file

This phase is performed only if you enabled the option: Forecasts at the Include in requirements calculation option (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 option (Requirements Planning Setup) then only non-MPS items are processed during this phase.

Processing Sales order file

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 option (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. Sales orders in D - Draft status are not processed, as a Draft order carries no committed demand until it is released on an active status.

For stocked items, the resource parent code (if defined) is extracted from the inventory master table. For non-stocked items, the stock code entered on the sales order line is used as the resource parent.

Notes and warnings

Prerequisites

• If you assigned a default resource parent to stock items (Stock Codes) 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.

Exclusions

• All items on Sales orders and Purchase orders excluded from the MRP calculation at Order Header level are ignored by this program (irrespective of their inclusion at line level).

  Individual Sales order and Purchase order lines excluded from the MRP calculation at line level are ignored by this program for orders included at Order Header level.

• Sales orders in D - Draft status are excluded from resource load. A Draft order commits no demand until it is released to an active status (for example, 1 - Open order line), so it does not contribute to resource load profiles.

eSignature considerations

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 eSignature Setup program.

eSignature Transaction	Description
MRP Resource explosion	Controls access to the Start Processing function in the Resource Explosion program.

Coding considerations

• The resource load file is only as up to date as the last run of this program, which can be run as often as required.