Delivery notes
A delivery note is a transport document that provides information on a consignment contained in one
truck (or other vehicle) and refers to an order or a set of orders for one consignee at a delivery address.
If the truck load contains shipments for various business partners, the load includes more than one
delivery note. The information on a delivery note includes the delivery date and address, the customer’s
name, the contents of the consignment, and so on. In Italy, a delivery note is a legally required document,
where it used to be called BAM (Bolla Accompagnamento Merci). Currently it is called DDT (Documento
di Trasporto). In Portugal and Spain delivery notes are also used, but there they do not have the same
legal status as in Italy.
ERP Baan5.0c
In ERP Baan5.0c, delivery notes were not included in the shipping documents that you can print for
goods leaving the warehouse.
New in Infor ERP LN 6.1
In ERP LN 6.1, the delivery notes funcionality is implemented in Warehouse Management. For more
information, refer to Delivery notes.
Due to implementation of the delivery notes functionality, the motive of transport and delivery code fields
are added to the following sessions in Order Management:
▪ Sales Order – Lines (tdsls4100m900)
▪ Sales Order Lines (tdsls4101m000) ▪ Sales Order Delivery Lines (tdsls4101m100) ▪ Sales Schedules (tdsls3111m000)
After the shipment lines are confirmed in Warehouse Management, the new Delivery Note, Gross
Weight, and Weight Unit fields are defaulted from Warehouse Management in the Sales Order Actual
Delivery Lines (tdsls4106m000) and the Schedule Shipment Details/Corrections (tdsls3140m000)
session.
In case of a purchase return order, the new Delivery Note field can also be filled in the Purchase Receipts
(tdpur4106m000) session.
Delivery types
This topic explains how the settings for the different types of delivery has changed in ERP LN 6.1
compared to ERP Baan5.0c.
Delivery types in ERP Baan5.0c
In ERP Baan5.0c, the following types of deliveries exist:
▪ Direct deliveries. For these type of deliveries, the Direct Delivery check box is selected on
the sales order line. ▪ Non-direct deliveries.
Delivery types in ERP LN 6.1
Changed in Infor ERP LN 6.1
In ERP LN 6.1, you can select a delivery type in the new Delivery Type field of the Sales Order Lines
(tdsls4101m000)/ Delivery Lines (tdsls4101m100) session.
The following delivery types are available:
▪ Sales
The sales order (delivery) line must be delivered by the Sales Control module. As a result,
you must maintain the deliveries in the Maintain Deliveries Sales Order Lines (tdsls4101m200)
session.
▪ Work Center
The sales order (delivery) line must be released to Warehouse Management, but instead of
a warehouse, a work center is communicated to Warehouse Management. Delivery takes
places from work center to business partner. This applies to generic items that are assembled
by means of the Assembly Planning module.
▪ Invoicing
The sales order (delivery) line must be invoiced only, no physical delivery takes place. For
example, this is applicable in case of consignment invoicing, and retrobilling.
▪ Not Applicable
No delivery type is applicable, because the order line is of the Order Line type. Lines of this
type are split up in several sequences (delivery lines) and only display totaled quantities and
amounts.
▪ Direct Delivery
The sales order (delivery) line is a direct delivery.
This value can be selected as follows in the Delivery Type field of the Sales Order Lines
(tdsls4101m000) session or the Delivery Lines (tdsls4101m100) session:
▪ Automatically, if the ordered quantity is equal to or greater than the quantity defined in the
Direct Delivery from Quantity field in the Item – Sales (tdisa0101s000) session.
▪ Manually, by selecting Direct Delivery.
▪ By selecting Generate Direct Delivery from the shortage menu that appears when an
inventory shortage exists for the item.
For more information, refer to Direct delivery.
▪ Cross-docking
The sales order (delivery) line must be cross-docked.
This value can be selected as follows in the Delivery Type field of the Sales Order Lines
(tdsls4101m000) session or the Delivery Lines (tdsls4101m100) session:
▪ Manually, by selecting Cross-docking.
▪ By selecting Generate Purchase Order Advice from the shortage menu that appears
when an inventory shortage exists for the item.
▪ After you run the Generate Purchase Order Advice for Sales Order (tdsls4240m000)
session with the Type of Line set to All Lines for sales order (delivery) lines with the
Delivery Type field set to Warehouse.
For more information, refer to Purchase orders for non-direct deliveries (p. 143) .
▪ Warehouse
The sales order (delivery) line is delivered by Warehouse Management.
For direct deliveries or cross-docking orders, you must generate a purchase order advice in the Generate
Purchase Order Advice for Sales Order (tdsls4240m000) session, which was called a planned purchase
order in ERP Baan5.0c.
Note
▪ For a direct delivery, a one-to-one relationship exists between the sales order line and the
purchase order line. As a result, updates to a number of fields on the sales order line reflect
in the linked purchase order line. For a cross-docking order, however, several purchase order
line details can be linked to one sales order line, or several sales order delivery lines can be
linked to one purchase order line. As a result, if you make changes to the sales order line, the
link with the purchase order line (detail)(s) can be broken. See also: Relation between
cross-docking and splitting deliveries.
▪ A sales order line is linked to Purchase Control if one of the following fields is filled in the
Linked Order Line Data (tdsls4102s200) session:
▪ Planned Purchase Advice Number
▪ Purchase Order
After deliveries are executed for a delivery type, delivery information is reported back to Sales Control.
You can view delivery information centrally in the following sessions:
▪ Sales Order Lines Monitor (tdsls4510m000)
▪ Sales Order Actual Delivery Lines (tdsls4106m000)
Effectivity units
An effectivity unit is a reference number on a sales order line or a sales quotation line that is used to
model deviations for a unit effective item, or to peg purchase orders or production orders to a specific
sales order line.
New in Infor ERP LN 6.1
In ERP LN 6.1, you can define effectivity units in the new Unit Effectivity (UEF) module of Common
Data, after which you can enter these units in sales quotations, sales orders, and sales contracts.
Effectivity units are used as follows:
▪ For pegging purposes. For more information, refer to Overview of unit effectivity.
▪ To control exceptions for an end item according to the series approach. For more information,
refer to Unit effectivity procedure 1 – series approach.
▪ To control exceptions for an end item according to the sales order approach. For more
information, refer to Unit effectivity procedure 2: Sales approach.
If you use unit effectivity to configure an item:
▪ The new Configuration Date (UEF) field in the Sales Parameters (tdsls0100s000) session
determines the date on which an effectivity unit must be configured for a sales order/quotation.
▪ For every requirement that you select for an effectivity unit in the Requirements
(tcuef0106m000) session, you can define an upgrade price. In case special components or
accessories are used, it is common practice that a sold-to business partner must pay an
additional (upgrade) price for these components or accessories. The requirement’s upgrade
price is added to the effectivity unit’s sales price.
As a result, in each session in which sales order/quotation lines prices are used or displayed, upgrade
prices are added to, or included in the sales price for unit effective items.
For more information about how to configure an effectivity unit, refer to:
▪ To configure effectivity units
▪ Unit effectivity as a lean configurator in Sales Control
Equate balance of receipts with inventory level
New in Infor ERP LN 6.1
In the Purchase Order Parameters (tdpur0100m400) session, you can use the Method of Calculating
Average Purchase Price field to determine how the average purchase price is calculated.
You can select the following:
▪ Current Inventory
The average purchase price is calculated based on the average price of the current inventory.
▪ Purchases (Cum)
The average purchase price is calculated based on the average price of the cumulated
purchases up to the time of the new receipt.
If you select Purchases (Cum), and the value of the cumulative receipts is high, the influence of the
order price on the average purchase price is very small. If this influence becomes too small, you must
decrease the value of the cumulative receipts by equating the value with the inventory on hand.
In ERP LN 6.1, you can use the new Equate Balance of Receipts with Inventory Level (tdipu0201m000)
session to decrease the value of the cumulative receipts. You must run this session periodically to ensure
that realistic average purchase prices for the items are calculated.
Invoicing commissions and rebates
This topic explains how the commissions and rebates invoicing procedure has changed in ERP LN 6.1
compared to ERP Baan5.0c.
Invoicing in ERP Baan5.0c
In ERP Baan5.0c, if a link with Financials exists for commissions and rebates, invoices are created
directly in the Commission Control System (CMS) module. When processing the commissions and
rebates in the Process Commission/Rebate (tdcms2201m000) session, they are posted to the General
Ledger (GLD) module of Financials.
Invoicing in ERP LN 6.1
In ERP LN 6.1, if a link with Financials exists for commissions and rebates:
▪ Commissions are released to the Accounts Payable (ACP) module of Financials. As a result,
ERP LN 6.1 creates an open entry in the Accounts Payable module.
▪ Rebates are released to Central Invoicing. After processing in Central Invoicing, the rebates
are sent to the customers in the form of sales invoices or credit notes, and posted to Financials
as open entries in the Accounts Receivable module.
Note
This functionality has changed to support:
▪ The use of the standard invoicing functionality offered through Central Invoicing. For more
information, refer to Invoicing.
▪ The generation of invoices that combine both rebate requests and other invoice requests for
a specific sold-to business partner.
▪ A lean integration between commissions and the Accounts Payable module of Financials.
Changed in Infor ERP LN 6.1
Because of the new invoicing functionality, a number of changes are made to the Commission Control
System module of ERP LN 6.1.
Unreserved commissions and rebates
Print Approved Commissions/Rebates (tdcms2402m000)
In ERP Baan5.0c, this session was called the Print Commission/Rebate Invoices (tdcms2402m000)
session.
The following fields are removed from this session, because the invoicing functionality is moved to
Financials:
▪ Final Invoices ▪ Invoice Date
This session prints the approved unreserved commissions or rebates for commissions and rebates that
apply to the same relation or order.
Because the invoicing functionality is removed from this session, its purpose is now to change the status
of the commission/rebate from Approved to Ready. The Ready status is necessary to release the
commission/rebate to invoicing in the Release Commissions/Rebates to Invoicing (tdcms2201m000)
session. If the Link with Finance check box is cleared in the Commissions/Rebates Parameters
(tdcms0100s000) session, the status changes to Closed.
Reserved commissions and rebates (with a link to Finance)
Reservation and Approval of Reserved Commissions/Rebates (tdcms2202m000)
In ERP Baan5.0c, this session was called the Global Approval of Reserved Commissions/Rebates
(tdcms2202m000) session.
The following field is added to this session:
▪ Approve Reserved Commissions/Rebates
You can use this session to do the following:
▪ Set the status to Reserved for the commissions and rebates that:
▪ Are approved in the Global Approval of Commissions/Rebates (tdcms0250m000) session.
▪ Have the Reserve check box selected in the Global Approval of Commissions/Rebates
(tdcms0250m000) session.
▪ Set the status to Reservation Approved for the commissions and rebates with the Reserved
status.
Print Reserved Commissions/Rebates (tdcms2403m000)
In ERP Baan5.0c, this session was called the Invoice Reserved Commissions/Rebates (tdcms2403m000)
session.
The following fields are removed from this session:
▪ Final Invoices ▪ Invoice Date
This session prints the approved reserved commissions or rebates for commissions and rebates that
apply to the same relation or order.
Because the invoicing functionality is removed from this session, the purpose of this functionality is now
to change the status of the commission/rebate from Reservation Approved to Ready, if the Link with
Finance check box is selected in the Commissions/Rebates Parameters (tdcms0100s000) session.
The Ready status is required to release the commission/rebate to invoicing in the Release
Commissions/Rebates to Invoicing (tdcms2201m000) session. If the Link with Finance check box is
cleared in the Commissions/Rebates Parameters (tdcms0100s000) session, the purpose of this
functionality is to change the status of the commission/rebate from Approved to Closed.
Reserved and unreserved commissions and rebates
Commissions/Rebates Parameters (tdcms0100s000)
The following fields are removed from the Commissions/Rebates Parameters (tdcms0100s000) session:
▪ Tax Code for Commission Invoice
▪ Tax Code for Rebate Invoice
▪ Commission Calculation Method
▪ Rebate Calculation Method
These fields are transferred to the Relations (tdcms0110s000) session, because they must be
maintainable by relation.
Relations (tdcms0110s000)
The following fields are added to the Relations (tdcms0110s000) session:
▪ Purchase Type. For more information, refer to To set up control accounts.
▪ Sales Type. For more information, refer to To set up control accounts.
▪ Tax Code. This field is moved from the Maintain Commission Parameters (tdcms0100m000)
and Maintain Rebate Parameters (tdcms1100m000) sessions, to the Relations (tdcms0110s000)
session in ERP LN 6.1, because the tax codes must be maintainable by country.
▪ Currency for Invoicing
▪ Calculation Method. This field is moved from the Commissions/Rebates Parameters
(tdcms0100s000) session.
▪ Rate used for Calculating/Invoicing
▪ Exchange Rate Type
▪ Exchange Rate Type Used
For more information, refer to Commission and rebate currencies (p. 126) .
Release Commissions/Rebates to Invoicing (tdcms2201m000)
In ERP Baan5.0c, this session was called the Process Commission/Rebate (tdcms2201m000) session.
The following fields are added to this session:
▪ Commissions to Accounts Payable ▪ Rebates to Central Invoicing
In this session, both the reserved and unreserved commissions and rebates with the Ready status can
be released to invoicing.
For more information, refer to online help of the Release Commissions/Rebates to Invoicing
(tdcms2201m000) session.
Print List of Reserved Commissions/Rebates (tdcms2404m000)
In ERP LN 6.1, you can use this session to do the following:
▪ Print a list of the reserved commissions or rebates. If you select this option from the Menu
Browser, ERP LN 6.1 starts the Print List of Reserved Commissions/Rebates (tdcms2404m000)
session.
▪ Print relations by invoice. ERP LN 6.1 starts the Relations by Invoice (tdcms2404m000) session
if you click the printing button in the Relations by Invoice (tdcms2502m000) session.
The Also print Rebates released to SLI, but not yet Invoiced check box is added to this session.
Relations by Invoice (tdcms2502m000)
Although this session already existed in ERP Baan5.0c, it was never used.
In ERP LN 6.1, the following field is added to this session:
▪ Released to SLI(Rebate)
For more information, refer to the online help of the Relations by Invoice (tdcms2502m000) session.
Note
After a rebate is released to Central Invoicing and the invoice status is Confirmed or On Hold in Central
Invoicing, you can still update the rebate invoice data in the Rebates Calculated by Order
(tdcms2150s000), or the Rebates Calculated by Relation (tdcms3150s000) sessions. For more
information, refer to To change sales data after release to Central Invoicing.
Link between Purchase Control and Freight Management
This topic explains how the Purchase Control module is linked to the new Freight Management package
in ERP LN 6.1.
Freight Management in ERP LN 6.1
The purpose of the Freight Management package is to plan and/or to subcontract the transportation of
inbound and outbound goods, which helps you select the most cost-effective way to get goods in and
out of the site at the correct times.
For infomation on the setup and use of the Freight Management package, refer to Freight Management.
Link with Freight Management
If Purchase Control is responsible for the transportation of goods and must consequently collect goods
from a supplier, you can generate a freight order from the purchase order. If the transportation of goods
is not the supplier’s responsibility, but the responsibility of Purchase Control, the supplier must know on
what date the goods must be ready. As a result, you must consider the planned load date in the purchase
order as the shipment date: when to pick up the goods from the supplier.
The following links exist:
▪ Between Freight Order Control and Purchase Control
During the planning and execution of a freight order, its status often changes. If Purchase
Control is responsible for creating the freight order, the progress of the shipment and loads
can be exchanged and information can be shared between Freight Order Control and Purchase
Control. For more information, refer to Integration Freight Order Control and Purchase Control.
▪ Between freight invoicing and purchase invoicing
The freight rate that you must pay to the carrier, is called freight costs. You can invoice your
business partner for the freight costs, based on:
▪ Freight Costs.
▪ Freight Costs (Update Allowed).
▪ Client Rates.
For more information, refer to Integration Freight Invoicing and Purchase Invoicing