Sales plan


This is a feature that registers sales plans for a specified period and automatically generates sales orders.
Users may specify the accuracy of sales plans in 4 levels (company forecast; sales forecast; customer forecast; firm orders) and register items by customer.


How to use sales plan

There are two kinds of sales plan: aggregate sales plan and daily sales plan. Their usage will be determined according to how sales plans are determined.

When creating an annual sales plan

In the aggregate sales plan, specify item, customer, quantity and time period.
By executing the "Explode sales plan" command, daily sales plans will be automatically generated, to be followed by daily leveling and generation of sales orders.


When creating monthly plans in series (monthly quantity only)

In daily sales plans, specify item, customer, quantity and time period. The quantity should be specified for each month.
By executing the "Explode sales plan" command, daily leveling and generation of sales orders will take place.
The aggregate sales plan will not be used.


When creating monthly plans in series (with daily quantity)

In daily sales plans, specify item, customer, quantity and time period. The quantity should be specified for each month.
By executing the "Explode sales plan" command, sales orders based on daily quantities will be generated.
The aggregate sales plan will not be used.


When creating a plan for an irregular period (without daily quantity)

In the aggregate sales plan, specify item, customer, quantity and time period. For time period, select "expression" from options and specify a period expression (10 days in the example below.)
By executing the "Explode sales plan" command, daily sales plans will be automatically generated, to be followed by daily leveling and generation of sales orders.


When creating a plan for an irregular period (with daily quantity)

In daily sales plans, specify item, customer, quantity and time period. The quantity should be specified for each day.
By executing the "Explode sales plan" command, sales orders based on daily quantities will be generated.
The aggregate sales plan will not be used.


Calendar resource and daily leveling

When a value is specified for "Quantity" in the sales plan, the quantity will be leveled on a daily basis.

When leveling on a daily basis, refer to the working time of the resource specified for the "calendar resource" property. The daily quantity values cannot be calculated for those dates that have no working time.

As shown in the example below, 7/2 are 7/9 are holidays. When you execute the "Explode sales plan" command, these two dates will remain blank.


Calculation of daily quantity values will be determined by working time and resource quantity of the calendar resource on the corresponding dates. The quantity will be proportionally divided according the ratio between the value achieved by adding up the resource quantity for continuous working time within a day and the value achieved by adding up the said value for one month.

As shown in the example below, the quantity is 600, and the resource quantity is set as: "3" for 6/1, "2" for 6/2 and "1" for 6/3. The results of daily quantity value calculation will be: 300 for 6/1; 200 for 6/2; and 100 for 6/3.


In another example, the quantity is 600, and the number of continuous working time from 6/1 to 6/3 is set as 1, 2 and 3 respectively, with the resource quantity of 1 each. The results of daily quantity value calculation will be: 100 for 6/1, 200 for 6/2 and 300 for 6/3.


If the "Recalculate daily qty" property is set to "First time only," daily quantity values will not be calculated when daily values are already entered for each date. If the said property is set to "Every time," daily quantity values will be calculated every time the sales plan is exploded, overwriting the results for each date.
If you would like to manually revise daily values for individual dates, set the "Recalculate daily qty" property to "First time only."

In case that there is no resource specified in "Calendar resource" property, the "Factory calendar resource" property (settings tab) on project settings dialog of resource is considered. If both "Calendar resource" and "Factory calendar resource" properties are not specified, it will be time-wise load levelling daily by 24 hours.


Treatment fot the date not in the sales plan (From Ver.7.2.0)

In the sales plan, the not-exist date can be input.

If the not-exist date is imported from external source, the color of the cell would be red for the error.
And there would not be generated the sales order.

 


Generating sales orders

There are 4 types of sales plan: "company forecast"; "sales forecast"; "customer forecast"; and "firm orders." As far as the daily quantity values used for generating sales orders are concerned, priority is higher for "sales forecast" than "company forecast." Similarly, "customer forecast" has a higher priority than "sales forecast," and "firm orders" will be given a higher priority over "customer forecast."

For example, values are entered for both company forecast and customer forecast from 1st to 3rd. As customer forecast should be given preference, sales orders will be generated according to the values specified for customer forecast.
If you look at the working time of the calendar resource, the number of continuous working time remains the same from 1st to 3rd ("1"). Therefore, the number of sales orders to be generated for each day will be 1 order per day. The class of the generated sales orders will be replenishment orders, and the order code will be made by the "sales order code expression" in the project settings.

You may have multiple sales orders generated for one day. For further details, refer to Truck deliveries.


Generated sales order

The order class of generated sales order is "Replenishment order". The order code is created according to "Auto-generated sales order code expression" property in project settings dialog.

Generated sales order in order table is shared with "Sales plan (Aggregate)" object. If the "Sales plan (Aggregate)" object is deleted, then the generated orders will be deleted when executing "Explode sales plan " next time. If you want to keep the generated sales orders even the "Sales plan (Aggregate)" object is deleted, please change the order class to "Registered order".


The "Due date" of the generated sales order is based on the "Day demarcation time" property on the project settings dialog.

 

Customer and assignment resource

Customer

If the customer property in sales plan is specified, the the generated sales order will be specified with the customer name.

For example, the customer property in sales plan is specified with "CustomerA", the the generated sales order will be specified with "CustomerA" as follows.


In addition, if there are two customers, CustomerA and CustomerB, specified for one item, sales orders can be generated for every customer. The "Customer" property of the generated sales orders is based on the "Customer" property value specified in sales plan table.

 

Assignment resource

If the "Assignment resource" property in sales plan table is specified, the "Customer" property of generated sales order is specified with the "Assignment resource" property value.

For example, the "Assignment resource" propety is specified with "AssignA" and "AssignB", the "Customer" property of generated sales order is specified with "AssignA" and "AssignB".

 

Jump from sales plan table. (From Ver.8.0.4. Ver.9 restricted feature.)

Select the cell in sales plan table, right click and select the "Jump" in the popup menu. Then it can jump to related sales order, pegged order, pegged chart or table.



Jump/Order gantt chart:Pegging order

Jump to the order gantt chart on which the generated order related with selected cell and the pegging order are displayed.

Jump/Order gantt chart:Sales order

Jump to the order gantt chart on which only the generated order related with selected cell is displayed.

Jump/Pegging order

Jump to the order table on which the generated order related with selected cell and the pegged order are displayed.

Jump/Sales order

Jump to the order table on which only the generated order related with selected cell is displayed.


In case that several cells are selected, the sales orders related with selected cells are considered.

Jump functions are used for four types sales order, which are "Company forecast", "Sales forecast", "Customer forecast" and "Firm orders".

In case that several cells are selected on the same day, the "Jump" functions are only available for the cell which the "Type" accuracy is the most highest. For example, a "Company forecast" cell, a "Customer forecast" cell and a "Firm orders" cell are select on 6/2, the "Jump" functions are only available for the "Firm orders" cell, because the accuracy of "Firm orders" is the most highest. A "Company forecast" cell and a "Customer forecast" cell are selected on 6/3, the "Jump" functions are only available for the "Customer forecast" cell, because the accuracy of "Customer forecast" is higher than the one of "Company forecast".


The "Jump" functions are not available for the cell which the "Type" accuracy is "Production" or "Remaining".

 

Production and remaining

Production and remaining in sales paln table are updated in the "Generate schedule summary" command based on "Production plan" table.


Production

The production quantity on this day.

Remaining

It is the remaining of sales order. It is calculated as follwed expression.

In case that there is not "Company forecast", "Sales forecast", "Customer forecast", "Firm orders" or "Results", "Production" and "Remaining" will be deleted.

In case that a resource filter or a period filter is specified in the "Generate schedule summary" command, the production and remaining related with filtered result will be updated.


Inventory valid period and Remaining

Although the Inventory valid period property is specified, the inventory quantity in "Remainding" row of Sales Plan table is not decreased after the specified time.

 

Results

When you specify values in the "Results" column of the sales plan, they will be reflected in the results of the pegged sales orders as the "Explode sales plan" command is executed.
Specify in the "Results" column the sum of the shipped quantities for the day.

For example, suppose that values are entered in the "Results" of the sales plan as shown below.
* It is necessary to set the "customer" field if it has been set in the unofficial sales plan.


When you execute the "Explode sales plan" command, the results are reflected in the sales orders as follows:


If the sales orders for the same day are divided into multiple orders (i.e., using truck deliveries), as in orders from S000000 to S000002, the reported quantity will be allocated to respective sales orders.
If the reported quantity in the sales plan is either less than or above the sum of the quantities of sales orders, as in orders from S000003 to S000008, it will be balanced out by the final sales order.


Time stamp

The main objective for using time stamp is to serve as a guide when deleting a sales plan object.
Time stamp will be automatically specified when the data is

imported by DBIO

input and generated from GUI

automatically generated from the aggregate sales plan

However, time stamp will not be specified if it has already been specified.
Therefore, if you import data by specifying time stamp at an external database, Asprova will not update the data by the imported date.

If the sales plan contains the sales plan for the same item and the same customer, the values to be used may be decided according to the date of time stamp.
For further details on the rules concerning the values to be used, refer to "Note" below.


Relation between aggregate sales plan and daily sales plan

The relation between aggregate sales plan and daily sales plan can be described as follows:

1. For a daily sales plan added on its own by a user, its "Relation to aggregate sales plan" property will be specified as "No."
In such a case, there will be no relation between aggregate sales plan and daily sales plan.

2. For a daily sales plan generated from the aggregate sales plan, its "Relation to aggregate sales plan" property will be specified as "Yes."
In this case, aggregate sales plan and daily sales plan are related in the following ways:

* If the aggregate sales plan is deleted, daily sales plans will be deleted when the sales plan is exploded next time.

* As the sales plan is exploded, the aggregate sales plan will confirm the existence of daily sales plans to which it is related and determines whether or not to create a new daily sales plan. Also, when the aggregate sales plan has its time period shortened, it will delete any daily sales plan object to which it is related.

* Daily sales plans will be affected by changes in the properties of the aggregate sales plan. For example, time period, customer and quantity.

* The "Assignment resource" property value in daily sales plans is copied to aggregate sales plan. If the "Recalculate daily qty" property is "First time", then it is copied at the first time. If the "Recalculate daily qty" property is "Every time", then it is copied every time.

Because of the above-described relation between aggregate sales plan and daily sales plan, the sales plan may be used in the following ways:

Example 1

Those who only want to manage the aggregate sales plan need to make additions to / revise / delete the aggregate sales plan alone.
As daily sales plans are all generated from the aggregate sales plan, their "Relation to aggregate sales plan" will always be "Yes," and by deleting the aggregate sales plan, daily sales plans will be deleted as well.

Example 2

Those who only want to manage daily sales plans do not need to manage (use) the aggregate sales plan, as all the daily sales plans' "Relation to aggregate sales plan" be "No."


Remarks

When the sales plan contains the sales plan for the same item and the same customer, the following rules will apply:

Example 1

Suppose that the aggregate sales plan is specified as follows:

CodeTypeItemCustomerPeriodTime stamp
Aggregate sales plan ACustomer forecastProduct ACustomer Xfrom 1st to 10th2006/9/1
Aggregate sales plan BCustomer forecastProduct ACustomer Xfrom 11th to 20th2006/9/10

Respective daily sales plan objects are generated for these two aggregate sales plan objects by the "Explode sales plan" command; on the sales plan (daily sales plan), they will be shown in two lines.

ItemType8th9th10th11th12th13thTime stamp
Product ACustomer forecast444   2006/9/1
 Customer forecast   5552006/9/10

Quantity to be used

ItemType8th9th10th11th12th13th
Product ACustomer forecast444555

As the two daily sales plans do not have time constraints, the value for each date will be used as it is.

Example 2

Suppose that the aggregate sales plan is specified as follows:

CodeTypeItemCustomerPeriodTime stamp
Aggregate sales plan ACustomer forecastProduct ACustomer Xfrom 1st to 10th2006/9/1
Aggregate sales plan BCustomer forecastProduct ACustomer Xfrom 9th to 20th2006/9/10

Respective daily sales plan objects are generated for these two aggregate sales plan objects by the "Explode sales plan" command; on the sales plan (daily sales plan), they will be shown in two lines.

ItemType8th9th10th11th12th13thTime stamp
Product ACustomer forecast444   2006/9/1
 Customer forecast 555552006/9/10

Quantity to be used

ItemType8th9th10th11th12th13th
Product ACustomer forecast455555

Comparing the two daily sales plans, there are time constraints on 9th and 10th. In these cases, the value whose time stamp is more recent (2006/9/10) will be used.
If there is no time constraint, the value for that particular date will be used as it is.
If time stamp happens to be the same, which value should be used is yet to be decided.


Explode sales plan command

The "Explode sales plan" command performs the following:

Automatic generation of daily sales plan objects from aggregate sales plan objects.

Daily leveling of quantities.

Generation of sales orders from daily quantity values.

Therefore, you need to execute the "Explode sales plan" command when using the sales plan.

As the "Explode sales plan" command is incorporated in the scheduling parameter "Default sales plan explosion parameter," you only need to execute this parameter, which is a standard feature.

By incorporating the "Explode sales plan" command into the scheduling parameter, you may execute from sales plan explosion to assignment by a single parameter.
To add the "Explode sales plan" command, insert the command prior to assignment, as shown below.



HelpNo.:706300
© 2016 Asprova Corporation, All rights reserved.