MSDyn365FO: Delivery schedule

You might be aware of the Delivery schedule feature available on the sales orders. But what I would like to consider today is the back side of this functionality. Don’t underestimate the importance of knowing about the background of this feature since it might affect your future development/customizations regarding sales order lines and its inventory transactions.

Understanding of this approach may come in handy when you review the inventory transactions for each sales order line.

You probably already know that there are some of the options that affect the appearance the inventory transactions.

For instance,

• When sales order type is Journal -> Inventory transactions will not be created
• When Inventory model of the item is not Stocked product -> Inventory transactions will not be created

What you might not know, there is an additional case, when Inventory transactions are not created.

Imagine the following scenario.  Your customer asked you to deliver 100 units of speakers. But insisted on delivering 30 speakers this week, and 70 speakers next week.

Imagine another scenario:  Your customer asked you to deliver 100 units of speakers. Your company doesn’t have those speakers available on stock. Vendor of the speakers pointed out that he can deliver only 60 units of speakers per month. You disagreed on waiting for the full number of speakers to be delivered by that vendor. Customer and you came to an agreement and decided against shipping the full quantity at the same time, instead of this, to ship only 60 to-be-available-soon speakers at once.  It means that we will have a partial shipment in this case.

All in all, we are going to split our shipment. In this case, you will also need to pay attention to discounts. Due to the rules configured in AX, the customer might lose the discounts, because we are going to split our shipment and discount for that quantity might not be applied.

Walkthrough:

Create a sales order and sales order line.

Add an item and set the Quantity equal to 100 units.

Click Sales order line -> Delivery schedule

Click the New button and type in the quantity.

In the Remaining quantity field, you will see the remaining quantity that you have not distributed yet.

Setting this up, we are saying that our Products will be shipped over 2 weeks.

If the quantity entered in the Delivery schedule form is not equal to the Quantity of the sales order line, the system updates the sales order quantity based on the quantity entered into the delivery schedule form once you click OK in the Confirmation dialog box.

Let’s distribute the full quantity.

Once you have split the lines, you will see:

Line 1: Original quantity (for the simplification of explanation, lets’ call it Parent line)

Line 2…Line N: Split quantity based on the delivery schedule (for the simplification of explanation, lets’ call it Child line)

If you review the Type field, you will notice:

Type of the Line 1 = Order line with multiple deliveries

Type of the Line 2..Line N = Delivery type

However, when you don’t use this feature, the type of the line would be Order line with single delivery.

An important part of this observation:

Inventory transactions are not created for the sales order line with the Type = Order line with multiple deliveries, because such sales order lines will never be shipped.

Additional considerations:

If you remove the Parent line, the related child lines will be removed automatically.

Original line will not be selected to the Sales order posting forms (like Sales order confirmation, Picking list, Packing slip, Invoice).

In the Line quantity form Parent line will be displayed.

And the moral of the story? 

That said, when you do some customization, think of the Order line with multiple deliveries type. Because such lines should not be included into posting of the documents.  My takeaway: if you need to retrieve the list of sales order line to be shipped or processed, sales lines where salesLine.LineDeliveryType = LineDeliveryType::OrderLineWithMultipleDeliveries should be excluded.

That’s it!