Follow

Sales & Operation Planning Settings

The following settings apply to the Sales and Operations Planning Module

The following settings are only applicable when the S&OP add-on is enabled.

Fiscal Year Start: Sets the day your companies fiscal year starts. The year is not critical to keep up to date in this setting.

Monthly Grouping Type: Sets the basis of how monthly sales are aggregated. Options are Calendar month, 4-4-5 fiscal calendar, and 5-4-4 fiscal calendar.

Use Product Class for product parent level in File Upload: Allows users to automatically create a hierarchical level in the demand plan using the item product category value. Learn more in the article Creating an S&OP Planning Hierarchy by uploading or via automation

S&OP Customer Level Pareto Percentage: The pareto is a method of focusing the demand planning process on the most significant customers, items, and categories. It is based on the pareto principle, which states that 80% of the demand comes from 20% of the customers. The user can adjust the Customer pareto value from 100% to forecast every customer or lower.

S&OP Item Level Pareto Percentage: The user can adjust the item pareto value within the customer from 100% or lower.

Calculate Pareto Based on All Customers (if levels above): If checked, this option will base the pareto on the customer level only if there is a hierarchical level above the customer level. If left unchecked, the pareto will start at the highest level above the customer and run a pareto at each level below.

Show Members of Other Group in S&OP Report: When downloading S&OP related reports, this option downloads all the values in the "other" category forecast grouping.

Months Forward to Lock Demand Plan Editing: A user defined number of months forward where demand plans edits are not allowed. Setting a value of 1 locks the current month.

Recalculate SOP Actual History After Upload: With each upload the SOP demand plan and supply plan tables are populated with up-to-date sales and backlog information.

Sop Actual History Recalculate Months: If a value is entered, the value entered is how far in the past the S&OP history table is updated.

Use IQ algorithm: It is a forecast cleansing algorithm applied in S&OP demand planning process. When enabled, the algorithm is applied to all items when applicable. To learn more read the article What is the IQ Algorithm

MAPE calculation time frame: The number of rolling backward months to use to calculate MAPE, WMAPE, and VAF.

Pricing Type: Option to use customer specific pricing (if available) or average sales price (ASP) pricing if customer specific pricing is not available.

ASP calculation interval (in months): Sets the amount of history to use when calculating average selling price in the demand plan. To apply the change, the user must run a new Pareto Analysis and then a Demand Plan. DemandCaster calculates ASP using a weighted method that takes into account the quantity sold at a given price. This is especially important in situations where there are setup charges included in the pricing. Users may opt for pricing tables to set specific pricing for customer / item relationships.

Planning time horizon: Two years generates a statistical forecast for the current year and all of next fiscal year. Three years does the same but adds an additional year beyond the next fiscal year.

Show 4-P row in demand plan: Option to show the 4-P demand plan values in the Demand Plan views.

Enable sales input row in demand plan: Enables a row to upload a reference demand plan at the item level.

Enable revised budget in demand plan: Adds a second budget line that is updated throughout the year versus the starting budget that is established at the beginning of the and managed per the article How to Upload the S&OP Budget file

Enable POS orders: If point of sales data is available. Adds a line to the demand plan graphs and tables.

POS order period: Select how much POS history to load in demand plan view. 1, 2, or 3 years.

Redistribute Forecast: If a user defined forecast value cannot be applied to a specific bucket for any reason ( birth / discontinue date, do not forecast … ) then if this setting is switched on DemandCaster redistributes the unapplied component of the forecast to the other nodes at the same level. For example, if there are 2 items - A and B and they have a common parent P, and they have pareto percentage distribution for a bucket i.e. A is 60% and B is 40%. If item B becomes discontinued and parent P receives 100 as a user defined forecast, the logic will not be able to distribute 40 to B because it is discontinued thus the whole 100 will go to item A (in case the setting is on, otherwise only 60 go to A and the rest 40 are reported as not being able to be distributed in the UI and automatically the parent P edit becomes 60 instead of a 100). Learn more by reading the article Editing Demand Plans

Monthly to weekly forecast split: An automated approach to splitting a monthly demand plan to weekly buckets during the demand translation process. The default approach is even distribution where a monthly forecast is evenly split in weekly buckets. System Calculated calculates the weekly distribution within the months to split the forecast based on a historical seasonal distribution. An example of this is when shipments follow a hockey stick approach.

Monthly to weekly distribution calculation level: The level where the monthly to weekly split is calculated.

Delete prior UDF forecast with each new UDF file upload: This setting removes the prior UDF if the customer / item line is not included in the file. The value will default to the statistical forecast.

Interval waterfall snapshot: Options are months or weeks. Determines the basis of how the waterfall is presented when weekly bucketed forecasting is enabled.

Supply plan additional target: By default the supply plan target is set as a rolling 12 month target. The user may select an interim target such as end of fiscal year to allow the S&OP planning calculations to be fixed against a specific point in time.

Default supply location: Sets the default supply location for all items if no such supply location exists for the item.

Level load: Provides the option to level load the supply relative to demand, or to chase demand (increase supply with rising demand or decrease supply with falling demand). This option is available at the item level to make the setting item specific.

Level load safety stock tolerance: % to allow an items supply plan projected on hand to move into the safety stock quantity before triggering an adjustment. Only applicable when level loading is enabled.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk