SAP LE Shipping

You are an SAP Logistics Execution (LE) specialist. The user wants to process shipping with transportation planning and freight cost calculation in SAP.

What to check first

• Verify SAP LE module is installed: Run transaction SPRO → SAP Reference IMG → Logistics Execution and confirm LE customizing is loaded
• Check shipper master data exists: Transaction VN01 (Create Shipper) or VN02 (Change Shipper)
• Confirm transportation planning profile is active: Transaction TPTC (Customizing for Transportation Planning)
• Verify freight agreement exists: Transaction VSKM (Freight Agreements & Scales)

Steps

1. Create a shipment document using transaction VT01N (Create Shipment) and assign delivery documents to the shipment
2. Run transportation planning via transaction TP01 (Plan Shipments) to assign shipments to transportation legs and generate proposals
3. Confirm the proposed plan in transaction TP09 (Confirm Plan) to create transportation orders and cost assignments
4. Calculate freight costs using transaction TPCF (Transportation Planning & Freight Cost) with cost module TPVS for cost object creation
5. Maintain freight agreement scales in transaction VSKM with condition type TRCK (transportation costs) tied to shipper/carrier rates
6. Execute transaction VT01 to create pickup/delivery shipments and link to transportation legs with carrier assignments
7. Generate billing documents via transaction VF01 (Create Billing Document) to invoice freight costs from VKONT (shipment contracts)
8. Monitor costing results in transaction TPVS (Shipment Costs) to verify weight-based, distance-based, or fixed-cost calculations

Code

*&---------------------------------------------------------------------*
*& Report: ZR_SHIPPING_LE_PROCESS
*& Purpose: Process shipping with transportation planning & freight costs
*&---------------------------------------------------------------------*

REPORT zr_shipping_le_process.

TABLES: likp,    " Shipment Header
        lips,    " Shipment Item
        tprt,    " Transportation Route
        tpak,    " Shipment Cost
        konp.    " Pricing Condition

DATA: lt_shipments TYPE TABLE OF likp,
      lt_costs     TYPE TABLE OF tpak,
      ls_shipment  TYPE likp,
      ls_cost      TYPE tpak,
      lv_shpmnt_no TYPE shipment_number,
      lv_weight    DECIMAL(13,3),
      lv_freight   DECIMAL(13,2).

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE 'Shipment Selection'.
SELECT-OPTIONS: s_shpnum FOR likp-shipnum,
                s_carr   FOR likp-carrid.
SELECTION-SCREEN END OF BLOCK b1.

START-OF-

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change