Landed costs – purchase schedule receipts

How landed costs are linked to receipts, depends on where the item receipt must be recorded.

To receive non-inventory items, you must create receipts in the Purchase Schedule - Receipts (tdpur3115m200) session. The landed costs of the schedule line or ASN-line are automatically copied to the purchase schedule receipt. For pull and push schedules, receipts are linked at schedule-line-level.

The landed cost lines are stored in the Landed Cost Lines (tclct2100m000) session, which is linked to the Purchase Schedule - Receipts (tdpur3115m200) session.

You can add, modify, cancel, and delete landed cost lines in the Landed Cost Lines by Receipt (tclct2100m100) session. Unlike warehouse receipts, purchase receipts do not have a receipt header. Therefore, receipt-header-based fixed amounts are not applicable for purchase receipts. If a manually added landed cost line contains a fixed amount, the fixed amount level must be Receipt Line.

For partial receipts, fixed amounts are apportioned to the receipt lines. In case of under-receipt or over-receipt, the remaining amount is linked to the final receipt.

You cannot correct or inspect purchase receipts.

Warehouse receipts for pull schedules are linked to schedule lines.

Order-header and order-line based fixed amounts are not applicable for purchase schedules. Receipt-header-based fixed amounts are retrieved from the landed costs master data at the moment of receipt header creation. The origin is Master Data for these landed cost lines. Other landed cost lines are copied from the purchase schedule line to the receipt line. The Landed Cost Line Origin is Schedule Line for these landed cost lines. However, if an advance shipment notice is linked to the purchase schedule line, a receipt can be generated from this ASN. In this case, the landed costs for the receipt header and lines are retrieved from the ASN. For more information, refer to Landed costs – advance shipment notices.

When the receipt is confirmed, the landed costs are copied from the warehouse receipt line to the Purchase Schedule - Receipts (tdpur3115m200) session. After confirmation, you can still add, modify, cancel, or delete landed costs at warehouse receipt (line) level in the Landed Cost Lines by Receipt (tclct2100m100) session. These changes are synchronized to the landed costs of the linked purchase schedule receipt.

Warehouse receipts for push schedules are linked to the schedule header. Therefore, the landed costs cannot be retrieved from the schedule line. Based on the actual receipt date, landed costs are retrieved from the landed costs Master Data when the receipt header and lines are generated. However, if an advance shipment notice is linked to the purchase schedule, a receipt can be generated from this ASN. In this case, the landed costs for the receipt header and lines are retrieved from the ASN. For more information, refer to Landed costs – advance shipment notices.

Because purchase schedule receipts must be linked again at schedule-line level, multiple purchase schedule receipts can exist for one warehouse receipt. The landed costs of the warehouse receipt are divided across the purchase schedule receipt lines based on the received quantity. The prices and landed costs are not retrieved from the purchase schedule, but from the linked purchase contract and the landed costs master data.

Purchase schedule receipt lines are created in the Purchase Schedule - Receipts (tdpur3115m200) session when the warehouse receipt is confirmed. After confirmation, you can still add, modify, cancel, or delete landed costs at warehouse receipt level in the Landed Cost Lines by Receipt (tclct2100m100) session.

If, on purchase schedule receipts, quantities are updated after a warehouse inspection or correction, the landed costs are redetermined.

Before and after confirmation of a receipt (line), you can use the Landed Cost Lines by Receipt (tclct2100m100) session to manually change, add, cancel, or delete landed cost lines. This is applicable only for landed cost lines that are not yet matched in Financials.