Scenario Processes
These are the processes that can be run on a scenario from the Scenarios page.
|
Process
|
Results
|
||
|---|---|---|---|
|
Apply SKU Overrides Locally To Production
|
The Apply SKU Overrides Locally To Production process is an extension to running Apply Overrides To Production daily.
• Any valid overrides that were added are applied.
• Any valid changes to overrides are updated.
• The job runs on current and future Production scenarios.
The process does not do the following:
• Remove override values in production when the override is deleted.
• Remove override values in product when the override is expired.
• Update the scenario, part, location, and service group summary values with changes made by the process.
• Copy production values into a new period.
• Recompute on order mean (backorder allocation).
• Apply EOQ overrides.
|
||
|
Apply Overrides
|
The Apply Overrides process can be run on a scenario that has a state of Complete or Promoted To Production.
• Overrides are reapplied to the scenario. This allows new or changed overrides to be recognized and deleted overrides to no longer be applied.
• For all overrides the Apply Post Optimization flag is ignored and all overrides are applied as post optimization.
• Summary values for the scenario are recalculated.
|
||
|
Apply Overrides To Production
|
The Apply Overrides To Production process can only be run on the scenario that is in a Production state.
• All Overrides are reapplied to the Production scenario. This allow new or changed overrides to be recognized and deleted overrides to no longer be applied.
• Overrides are recognized and applied even if they would not be recognized by any of the scenarios segments.
• The Apply Post Optimization flag is ignored for all overrides. All overrides are applied post optimization.
• Summary values for the scenario are recalculated.
• The production tables are updated.
|
||
|
Approve All Holds
|
The Approve All Holds process updates all SKU records for the scenario that has a Production Status of Pending and a Production Status of Approved.
|
||
|
Approve All Overrides
|
The Approve All Overrides process updates all SKU records for the scenario that have the following conditions met:
• An override record for the SKU and the override has an Override Status of Pending.
• The SKU override’s Override Status is Approved.
|
||
|
Calculate
|
The Calculate process either calculates or recalculates all time periods (slices) for the selected scenario.
• All prior results for the scenario are deleted.
• To retain prior results, make a copy of the scenario first and then run the Calculate process on either the copy or the original scenario.
|
||
|
Clear Optimized Production Values
|
Running the Clear Optimized Production Values process performs the following actions:
• The Production scenario and associated summary data is removed. Therefore, the Production scenario is no longer visible on any Inventory Optimization pages.
• The production order plan stock level records for future periods are deleted. The historical or current period order plan stock levels are not deleted.
|
||
|
Copy
|
The Copy process creates a new scenario with the same parameters as the selected scenario.
Select the row to be copied, click the Run button and then select Copy. Enter the name of the new scenario in the text box and click OK.
|
||
|
Delete
|
The Delete process removes all data associated with the selected scenario.
|
||
|
Evaluate Exception Criteria
|
The Evaluate Exception Criteria process can be run on a scenario that has a state of Complete or Promoted To Production.
• This job should be run when production values have been updated and it is desirable to see how the current production values impact the records that have exceptions.
|
||
|
Generate External Production Reporting Data
|
The Generate External Production Reporting Data process moves SKU data from the calculation tables to the legacy IO tables for the Production scenario. This process should be run after a scenario is made production.
|
||
|
Generate External Reporting Data
|
The Generate External Reporting Data process moves SKU data from the calculation tables to the legacy Inventory Optimization tables. This process should be run after a scenario is calculated or overrides are applied.
|
||
|
Generate Summary Data for Production
|
The Generate Summary Data for Production process inserts and updates the summary data of the Production scenario records for the following pages:
• Scenario Summary
• Location Summary
• Part Summary
The IO_CREATE_PROD_SUMMARY_IN_STANDALONE_JOB_ONLY global setting controls when this process is enabled.
• When set to false (the default value), this process is not enabled
The summary data is automatically generated as part of the Make Production and Apply Overrides To Production processes.
• When set to true the Make Production and Apply Overrides To Production processes do not run the summary steps.
◦ For the Make Production process, the summary data of the Production scenario is blank on the Scenario Summary, Location Summary, and Part Summary pages
◦ For the Apply Overrides To Production process, the summary data of the Production scenario is not updated on the Scenario Summary, Location Summary, and Part Summary pages
◦ After running Make Production or Apply Overrides To Production, other critical processes such as Order Plan, can be started. Then, this summary job can be run to populate the summary data.
|
||
|
Make Production
|
Making a scenario Production enables orders to be generated against the stocking levels. The Make Production process can be run on a scenario that has a state of Complete or Promoted To Production. All SKUs for the Scenario that have a Production Approval Type that is not Pending or Disapproved is uploaded to the production tables.
• Only one scenario can be selected at a time. However, multiple scenarios in production are supported, so it is possible to see more than one scenario with a state of Production.
• When a scenario has a pending SKU, a message is displayed that warns the user that the pending SKU will not be moved to production.
• When a scenario has no approved SKU values, a message is displayed that warns the user that the scenario will not be made production.
• If another scenario was production, the state of that scenario is changed to Complete when the new scenario is made production. The results can be viewed in the Scenario Summary page.
• The Respect Override value on the scenario must be set to Yes to run the Make Production process on that scenario.
These global settings are related to the Make Production process:
• IO_EVALUATE_EMERGENCY_BACKUP_VALUES — This global setting controls when the Emergency Order values are populated on the summary records for both Production and calculated Scenarios.
◦ When set to false the EO values are not populated on the summary records
◦ When set to true the EO values are populated on the summary records
• IO_EVALUATE_OVERRIDE_COUNT — This global setting controls when the override count values are populated on the summary records for both Production and calculated Scenarios.
◦ When set to false the override count values are not populated on the summary records
◦ When set to true the override count values are populated on the summary records
• IO_EVALUATE_PRODUCTION_PART_SUMMARY — This global setting controls when the part summary information is populated for the Production scenario
◦ When set to false the part summary information is not populated for the Production scenario
◦ When set to true the part summary information is populated for the Production scenario
The Make Production process deletes future-period order plan net forecast stock level records for the same part and location being uploaded for a given period. If you Make Production for multiple periods and then make a different scenario production for a shorter horizon, the future order plan net forecast stock level records that are not being uploaded will not have the later records deleted. One such situation is a SKU with production stock levels changing over time, and a new Production scenario with the same level in the current time period. Make Production will not upload the unchanged record in the current period, and that will not delete the future records. This is a different result than if you only made the single period scenario production, because the static value would cascade into the future.
For example:
• Make a scenario production with levels over time of 5, 7, and 9.
• Make another scenario production for the first period only, with a level of 5
The result will still be order plan net forecast stock levels of 5, 7, and 9. If you make another scenario production with a level of 6 then the result will be a single order plan net forecast stock level record of 6 because the presence of the uploaded record will delete the later period records.
|
||
|
Start Collaboration
|
The Start Collaboration process enables the Inventory Collaboration process for the selected scenario.
• The In Collaboration field displays Yes when this job was run for the scenario.
• The scenario is available for selection on the Inventory Collaboration page.
|
