Description | Default Value | How Used |
---|---|---|
Enables the calculated safety stock value to go below -1. • When set to false the safety stock is floored at -1 • When set to true the safety stock is calculated by subtracting the rounded value of the pipeline forecast from the ROP | false |
Description | Default Value | How Used |
---|---|---|
Determines if users with the Dealer role have restricted access to the following: • The Minimum and Maximum field entries are not visible when creating or modifying a SKU Override on all pages where SKU Overrides can be managed. • The Pre-Optimization fields on the Create/Edit SKU Override page are not available. • Filters created on the Configurable Filters page cannot be shared. A user will only have access to modify and use filters that they have saved. When set to true, the access rights are restricted. When set to false, the access rights are not restricted. | false |
Description | This controls when the Emergency Order values are populated for both Production and calculated Scenarios on the Scenario Summary, Location Summary, Part Summary, and Segment Summary pages: • When set to true, the Emergency Order values are populated on the summary records. • When set to false, the Emergency Order values are not populated on the summary records. The fields that are affected by this global setting are: • Emergency Period Forecast (Optimized) • Primary Emergency Fill Rate • Primary Emergency Fill Rate (Optimized) • Secondary Emergency Fill Rate • Secondary Emergency Fill Rate (Optimized) |
Default Value | false |
How Used |
Description | Default Value | How Used |
---|---|---|
This is the month that the fiscal year begins. Valid entries are 1 - 12. | 1 |
Description | Default Value | How Used |
---|---|---|
This specifies the number of days after a SKU Override has expired before it is purged from the system. SKU Overrides with an End Date older than today minus the number of days specified by IO_OVERRIDE_CLEANUP_EXPIRED_RECORDS_DAYS are purged when the Synchronize Database AutoPilot process is run. For example, when IO_OVERRIDE_CLEANUP_EXPIRED_RECORDS_DAYS is set to the default value of 180 days, and today is February 11, 2022, any SKU Override with an End Date that is prior to August 15, 2021 are purged when the Synchronize Database AutoPilot process is run. • When this value is greater than 0, the SKU Overrides are evaluated and purged when the Synchronize Database AutoPilot process runs • When this value is 0 or -1. SKU Overrides are never purged. | 180 |
Description | Default Value | How Used | ||
---|---|---|---|---|
This controls the tracking of the Inventory Optimization scenarios that served Stock Levels to Production. Valid settings are: • Global Setting = 0 No records are inserted to the IPCS_MEO_PROD_SKU table. Therefore, no production SKU counts are greater than zero (0), and there are no scenarios that will have a State of Promoted to Production. • Global Setting = 1 Records for the current period are inserted to the IPCS_MEO_PROD_SKU table. Therefore, the production SKU counts in subsequent periods are zero (0), and scenarios can have a State of Promoted to Production
• Global Setting = 2 Records for all periods are inserted to the IPCS_MEO_PROD_SKU table. Therefore, the production SKU counts and the production SKU counts in subsequent periods are greater than zero (0), and scenarios can have a State of Promoted to Production | 2 | Controls what is displayed in the Production SKUs field. |
Description | Default Value | How Used |
---|---|---|
This determines the method used to build the production scenario SKU table (PM+ScenarioID) during the Make Production process and improves performance. Valid settings are: • A value of 1, uses a create table query based on the approved promoted scenario SKU, followed by an append query for any other SKU already in production. • A value of 2 uses a create table query based on the union of approved promoted scenario SKU and any other SKU already in production. | 1 | Improves the performance of the Make Production process. |
Description | Default Value | How Used |
---|---|---|
This determines how many days are included in an interval for converting EOQ (slices) to quantity. • When set to true then 30 for monthly or 7 for weekly is used as the number of days in the interval to convert EOQ (slices) to a quantity. • When set to false the actual number of days in the interval is used to convert EOQ (slices) to a quantity. | false |
Description | Default Value | How Used |
---|---|---|
This is used to calculate the default setting of the End Date when a SKU override is created • When this global setting is set to 0, the End Date is not populated • When this global setting is > 0, the value is added to the Begin Date and the End Date is populated with the last date of that period Examples for monthly processing: • Global Setting = 1 Begin Date = Jan 15 End Date = Jan 31 • Global Setting = 2 Begin Date = Feb 15 End Date = Mar 31 • Global Setting = 3 Begin Date = Apr 15 End Date = Jun 30 | 0 |
Description | Default Value | How Used |
---|---|---|
This is the value that triggers a notification that the maximum suggested override limit was exceeded. An override above this amount requires a confirmation from the user before the override can be saved. • When this global setting is set to 0, there is no maximum limit in place and the override is automatically accepted • When this global setting is > 0 and the override entered is greater than the value, the user must confirm the override before it can be saved | 0 |
Description | Default Value | How Used |
---|---|---|
This global setting controls the default level that is displayed when a new SKU Override is entered on the Create/Edit SKU Override dialog box. The value of this global setting can be any Override Type. | ROP |
Description | Default Value | How Used |
---|---|---|
Defines the label of the Space Constraints tab on the Create/Edit Service Group Parameter page. The value of this global setting will be displayed in columns and fields as follows: • Service Group Parameters Add/Edit tab — “<gs value> Constraint” • Parts and SKU pages — “<gs value> per Unit” • Scenario Summary, Location Summary, Part Summary, SKU Summary and Service Group Results — <gs value> Required | Cubic Meter |