Datamodel question regarding Deliveryplans

Hello Novulo Community,

I am trying to understand how deliveries work within Novulo, and I have a question regarding the concepts.

So far I have understood that there are Expected Deliveries and Deliveries, which are linked to each other and the sales lines, to indicate expectations of, and the deliveries themselves. After attempting to use these concepts, I learned that Deliveries are based off of a DeliveryPlan, which can also use an existing template. However, when navigating the concepts in the concept manager I found additional concepts which seem to serve a similar role. So far I have found the following concepts confusing:

  • DeliveryPlan
  • DeliverySchedule
  • DeliveryScheduleTemplate
  • LeveringsSchemaSjabloon
    Does anyone know the distinction between these concepts?

Hello Steffen!

The Delivery plans and the linked templates, deliveries, delivery lines and the expected deliveries and lines are the core of the Novulo Delivery system for delivery planning and inbound and outbound logistics.

It consists out of a few components that also make a link between sales, purchases and intercompany logistics.

Delivery Plans are records to describe how a product or service is planned to be delivered, inbound or outbound. Examples of settings in Delivery plans are ‘one time delivery’, ‘monthly recurring’, ‘on request’, ‘digital delivery’, but also ‘delivery to address’.

Delivery Plans are based on a Delivery Plan Template, which in turn are connected to the Sales price list item (product). This is, because typically the product determines how it can potentially be delivered.

To explain the concept and data model, it’s easiest to explain it on how it’s linked to a sales order

Explanation: Delivery plan for Sales

When you create a Sales order, you register how you need to deliver or fulfil this sales.

In typical retail or wholesale orders you will register the contact and address where you need to deliver to. In the Novulo setup, this is stored at the delivery plan.

It starts with adding sales, with one or more sales lines. Sales lines are based on a Sales price list item. (which relates to a product).

Sales Sales SalesLines SalesLines SalesLines->Sales 1..n SalesPriceListItems SalesPriceListItems SalesLines->SalesPriceListItems based on

The Sales Price List Item has the link to the Delivery Plan Template. When adding a Sales line to a Sales, you select the Delivery Plan Template you want to use. This is pre-filled with the default setting.

Then, the application will ensure that a Delivery Plan is made, for that sales, linked to that sales line.

Sales Sales SalesLines SalesLines SalesLines->Sales SalesPriceListItems SalesPriceListItems SalesLines->SalesPriceListItems DeliveryPlan DeliveryPlan SalesLines->DeliveryPlan linked to DeliveryPlanTemplate DeliveryPlanTemplate SalesPriceListItems->DeliveryPlanTemplate has default DeliveryPlan->Sales linked to DeliveryPlan->DeliveryPlanTemplate based on

From your question:

  • DeliveryPlan and DeliverySchedule are the same.
  • DeliveryScheduleTemplate and LeveringsSchemaSjabloon are the same, as is DeliveryPlanTemplate

Can you show where you found the different names, so we can harmonize them?

1 Like

Thank you for the clarification! Especially the relation between SalesPriceListItems and DeliveryPlanTemplate is clearer to me now.

As for the different names, I was exploring component M3323 (r768) and my confusion arose from the DeliveryPlan page (N_DeliverySchedule):

I had assumed they were the same as you explained, but I was not certain.

1 Like

Thanks for the clear explanation @Joost !

@SteffenBeu Across multiple components these names have changed a few times and now, unfortunately, the labeling/naming is out of sync in some places. It is an ongoing effort to harmonize the names to the names in that are defined in the Novulo reference architecture

N_DeliverySchedule

Variants: DeliveryPlan, DP, DeliverySchedule, Leveringsschema, Leveringsplan, Leverplan

The delivery schedule stores all “head” information required to plan and execute a delivery. For example, the sender, the receiver, the date and the related sales/purchase. This is an example of a delivery schedule:

As explained by Joost, you can link one or more sales lines to the same delivery template. Or you can link a single sales line to another delivery template if a part of the sales/purchase should be sent to a deviating address, for example.

N_DeliveryScheduleTemplate

Variants: DeliveryScheduleTemplate OR LeveringsSchemaSjabloon

The features of the delivery schedule are for some part defined by the linked delivery schedule template, as explained by Joost. They hold more generic settings that have a broader scope than a single delivery so that users do not have to (re)define the basic delivery behavior for each new delivery schedule.