Store orders - planning and due dates

The current article describes the purpose and usage of the planning and due dates in the store order headers - Planned Release date, Planned Completion date and Due date attributes.

Planned release date

The date specifies when, by plan, the execution of the store order should start. I.e. by plan on this date the first store transaction for the current store order should be released (if the store order is fulfilled at once, it would be the only store transaction).

Planned completion date

This is the date when, by plan, the execution of the store order should end. If can be considered as the date when the last store transaction for the current store order is released. But it would be more precise to say that this is the date when the last non-completed store transaction is completed, since the releasing of the store transaction does not guarantee that the process of execution of the store order is completed and the quantities and/or the costs may be modified by corrective documents to the released store transaction.

Due date

This is the end term for completion of the store order execution. The meaningful store order suggests the following to be true: Planned Release date =< Planned Completion date =< Due date. This still allows us to have different due dates and planned completion dates.

For example, if we have the following dates:

Planned release date = 2020/10/01
Planned completion date = 2020/10/05
Due date = 2020/10/08

It would mean that we plan to execute the order from 1th October to 5th October but the due date allows us a three days delay. This could happen if the execution plan is scheduled for this period (1th-5th October) because of purchase or production orders (because of resource optimisation, for example) but the due date is defined by another module (for example - by the delivery date to the customer).

Thus, the planned release date and planned completion date are used because of the production and procurement plan while the Due date is because of other modules which generate Store orders and it is used for control of the deadline. Planned release date is essential for the available to promise calculation and the projected available balance. Thus, by the planning dates the user is able to define more precisely the information about when a specified quantity of a product is expected to be produced or delivered.

For example, if a delivery of a large quantity of a product is expected but the delivery would be executed partially and not at once - several deliveries, so separated store orders could be created and each store order would define the different periods for each delivery stage. The advantage in this case is that the users would have more detailed information on when exactly the products are expected to be placed in the store. If we create one store order and the planned release date is the start of the first delivery, then the users would know that the whole quantity would be available at the first stage of the delivery.

For more information, see available to promise.

How are the attributes filled in by generation procedures?

Here we explain how the planning and due dates are filled in when the store order is generated by another document. For more precise information about the specific generation procedure Wiki should be referred to.

When generated by sales order

All generation procedures from sales orders define the planning and due dates in the store orders as follows:

Due date = Required Delivery date;
Planned Release date = Required Delivery date;
Planned Completion date = Required Delivery date.

Required Delivery date is found in the sales order lines or in the sales order header (if the lines have no value).

When generated by transfer orders

For receipt store orders the dates are filled in as follows:

Due date = Default Due date in;
Planned Release date = Default Due date in;
Planned Completion date = Default Due date in.

For issue store orders the dates are filled in as follows:

Due date = Default Due date out;
Planned Release Date = Default Due date out;
Planned Completion Date = Default Due date out.

Default Due date in and Default Due date out are found in the transfer order lines.

When generated by shipment orders

Here, the planning and Due dates are filled in as follows:

Due date = Required Delivery date;
Planned Release Date = Required Delivery date;
Planned Completion date = Required Delivery date.

Required Delivery date is found in the Shipment order header.

When generated by shipments

Here, the planning and Due dates are filled in as follows:

Due date = if the largest Required Delivery date has value - this is the date, if not - the Document date;
Planned Release date = if the largest Required Delivery date has value - this is the date, if not - the Document date;
Planned Completion date = if the largest Required Delivery Date has value - this is the date, if not - the Document date.

The largest Required Delivery date is the largest Required Delivery date from the Shipments headers and the line Required Delivery date from the Shipment lines.

When generated by consumption orders

When issuing store orders are generated, the dates are filled in as follows:

Due date - if the cheduled Date Time attribute from the Consumption order line has value - this is the date, else - the date of the first release of the consumption order;
Planned Release date - Scheduled Date Time;
Planned Completion date - Scheduled Date Time.

Scheduled Date Time is found in the Consumption Order lines.

When generated by output orders

When receiving store orders are generated, the dates are filled in as follows:

Due date - Due date from the work order;
Planned Release date - Release date from the work order;
Planned Completion date - Due date from the work order.

For each output order line, the Due date and the Release date from the work order are the dates of the work order selected in the output order line.

When generated by receiving order

All generation procedures of store order from receiving order fill the planning and Due dates as follows:

Due date - today's date;
Planned Release date - Planned Release date from the receiving order;
Planned Completion date - Planned Delivery date from the receiving order.

Planned Release date and Planned Delivery date from the Receiving order are attributes of the Receiving order header.

When generated by service activity