SAPFree worksheetPDF, Excel, Word exportSAP S/4HANADiscrete Manufacturing

SAP Routing Upload Worksheet (Excel)

Routing data is one of the most error prone parts of an SAP implementation or migration. This worksheet helps you stage operations in Excel format before you load them, with a computed lot time so engineers can sanity check each line.

Download:
MaterialPlantOperationWork centerControl keyOperation textBase qtySetup (min)Machine (min per base qty)Typical lotLot time (min)
170
465
85
70
385
0
Total lot time (min)
1,175
Total lot time (hours)
19.5833
Operations staged
6

Staging layout only. Map columns to your upload method (LSMW, migration cockpit or BAPI_ROUTING_CREATE) and confirm the field names and control keys in your system. Mark external operations with your external processing control key.

Check routing data before the load

Optional: an expert review of how to validate staged routings against legacy data.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Enter one row per operation, grouped by material, with plant, operation number, work center, control key, base quantity and standard values. The Lot time column calculates setup plus machine time for a typical lot. Review the totals with process engineering, then export to Excel or CSV and map columns to your load tool. Use it to find missing work centers, zero run times and wrong base quantities before they reach SAP.

  • Keep operation numbers in steps of 10
  • Use base quantity 1 unless the time is per batch
  • Check external operations have no internal times

Standard values and the lot time formula

In SAP, operation time is the standard value multiplied by the order quantity divided by the base quantity. Setup is charged once per lot, while machine and labor time scale with quantity. The worksheet uses setup plus run time times lot size divided by base quantity. Compare the result to what the shop floor reports. Large differences usually mean the unit of measure or base quantity is wrong.

Fields you must get right

Each operation needs a valid work center in the plant and a control key that matches how you schedule, cost and confirm it. Routing usage and status are set on the header, with production usage and a released status needed for orders to pick up the routing. Group counters distinguish alternative sequences. Missing a control key or work center is a common reason for failed uploads.

Common mistakes

Times entered in the wrong unit, for example hours when the work center expects minutes, inflate capacity load by a factor of 60. Using per piece times with a base quantity of 100 doubles or halves loads. Skipping a status release means order creation finds no usable routing.

  • Confirm the unit of the work center formula
  • Validate a sample of 20 routings against shop reality
  • Load in a test client first

Frequently Asked Questions

Can I upload this file directly into SAP?

Not as is. It is a staging layout. You map the columns to your chosen method, such as LSMW, the S/4HANA migration cockpit or a BAPI based program, and match the exact field names and formats your system expects.

What control key should I use?

Control keys are configured per system. PP01 is commonly delivered as a standard routing control key for internal operations, while an external processing key is used for subcontracting. Confirm the keys in your own configuration.

How are standard values scaled in SAP?

SAP multiplies the standard value by the order quantity and divides by the base quantity. Setup is typically a fixed value per lot while machine and labor values scale with quantity. Formulas on the work center can modify this.

Why does the lot time look wrong?

Check base quantity and units first. A base quantity of 100 with a per piece time overstates the load a hundred fold. Also check that setup is not entered per piece.

If you are migrating thousands of routings, we can build checks that compare your staged data to legacy ERP data and flag outliers before the load, with human review.