Landed costs – orders

This topic explains how landed costs are used in combination with purchase orders and warehouse transfer orders.

Landed costs - purchase orders and warehouse transfer orders

To link landed costs to purchase orders and warehouse transfer orders, the following steps are completed:

Step 1. Search for order header landed costs

When an order header is created and saved, LN searches for active landed costs sets in the Scenarios by Landed Costs Set (tclct1105m100) session, based on:

Step 2. Link landed costs to order header

When a landed costs set is found, the landed costs are stored in the Landed Cost Lines (tclct2100m000) session. This session is linked to the purchase order header in the Purchase Orders (tdpur4100m000) session or the warehouse transfer order header in the Warehousing Orders (whinh2100m000) session. The Landed Cost Line Origin reads Master Data for these header landed cost lines.

Step 3. Update landed cost lines

If required, users can manually update the retrieved landed cost lines and add or delete lines.

Step 4. Search for, link, and update order line landed costs

When purchase or transfer order lines are created, steps similar to steps 1–3 apply.

Step 5. Copy order header landed costs to order lines

The header landed costs, if available, are distributed across the lines.

  • To accomplish this, these methods exist:

    • Apportioning
      If the Calculation Method field is Fixed Amount and the Fixed Amount Level is Order Header, Shipment Notice, or Receipt Header in the Landed Cost Lines (tclct2100m000) session, the header landed costs are apportioned to the lines. For more information, refer to Landed costs – fixed amounts.
    • Synchronization
      If the Fixed Amount Level is Order Line or Receipt Line in the Landed Cost Lines (tclct2100m000) session, the header landed costs are synchronized with the lines based on the Calculation Method.

    After apportioning or synchronizing, the landed costs are stored in the Landed Cost Lines (tclct2100m000) session, which is linked to the order line. The Landed Cost Line Origin is Order Header for these line landed cost lines.

Note

Various landed cost lines can be automatically linked to the same purchase order line or transfer order line.

These are the landed cost lines that:

  • Originate from the header and contain a synchronized or apportioned landed cost amount.
  • Are newly generated based on a master data cost set.
Maintaining landed costs

If a change is made to an order header or a line search field, and depending on the Recalculate Landed Costs setting in the Landed Costs Parameters (tclct0100m000) session, LN can search for a new landed costs set. If found, the cost lines with the Master Data origin are deleted and the new cost lines are added.

You can use the Landed Cost Lines by Purchase Order (tclct2100m300) and Landed Cost Lines by Warehouse Order (tclct2100m500) sessions to manually change, add, cancel, or delete landed cost lines for a specific purchase order or warehouse transfer order.

You can manually change, cancel, delete, or add landed cost lines if the following are applicable:

  • Order header
    No receipt or advance shipment notice is linked to any of the order lines.
  • Order line
    No receipt or advance shipment notice is linked to the order line.

If you change or cancel landed cost lines in the Landed Cost Lines by Purchase Order (tclct2100m300) or Landed Cost Lines by Warehouse Order (tclct2100m500) sessions and on the appropriate menu you click Apply to all, the changes made to the line are also processed to all other lines of the order with the same combination of Landed Costs Code, Landed Cost Type, and Buy-from Business Partner. This also applies if you add a line. When a new landed cost line is added for an order line, you can automatically add this landed cost line to all other order lines for which the landed cost line is not linked yet and, therefore, for which the combination of Landed Costs Code, Landed Cost Type, and Buy-from Business Partner does not exist.

Landed costs and commingling

Before approval, purchase orders and order lines can be commingled into one purchase order. Landed cost lines can be linked to purchase orders or order lines only during the commingling process. Orders and order lines with the For Commingling check box selected cannot have linked landed cost lines.

Landed costs and purchase order approval

If a purchase order is automatically approved, the landed costs are recalculated based on the Recalculate Landed Costs parameter in the Landed Costs Parameters (tclct0100m000) session.

If you manually approve a purchase order and you want to recalculate the landed costs during approval, select the Recalculate Landed Costs check box in the Approve Purchase Orders (tdpur4210m100) session.

If the purchase order must be validated against approval rules in the Approval Rules (tdpur0191m000) session, the landed cost amount is also included in the checked amount.

Landed costs and backorders

Backorder lines are handled as normal order lines. Therefore, LN searches for an active landed costs set for the backorder line. No interaction exists between the parent order line and the backorder line.

Order-header-based fixed amounts are not reapportioned to the backorder lines, because reapportioning is no longer applicable if a receipt is linked to at least one order line. Fixed amounts at receipt level can still be applicable.

Processing landed cost lines

If all steps are carried out for the order procedure, purchase order lines can be processed in the Process Delivered Purchase Orders (tdpur4223m000) session. The landed cost lines that are linked to the actual receipts for the order line are also processed.

In the Landed Cost Lines (tclct2100m000) session, for a processed landed cost line the following applies:

If, in the Landed Cost Lines (tclct2100m000) session, the Update Status of Actual Purchase Costs field is Actual Costs Updated and the Invoicing Status is All Approved, the landed cost line is finished and can be deleted in the Delete Purchase Orders (tdpur4224m000) session.