Mass Routing Creation Upload Program from Excel
Short answer: A custom program that creates material routings in bulk from operation rows in an Excel or CSV file, with header, operations, work centers, control keys and setup/machine/labor standard values. In test mode it checks the work center and material, skips materials that already have a routing and lists the result for each routing.
- Estimated effort
- M · 5–7 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
CA01 enters one routing on screen, operation by operation; for hundreds of new materials with dozens of operations this takes days. CA85 only replaces work centers in existing routings and does not create new ones. LSMW recordings are sensitive to screen changes and are not recommended in S/4HANA; the Migration Cockpit is for the initial migration. The custom program groups the file per routing and creates it through a BAPI.
Who uses it? Industrial engineering teams introducing new products, PP master data owners and project teams opening a new plant.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| MARCPlant Data for Material | Existence of the material in the plant | Read | ECC + S/4 |
| CRHDWork Center Header | Existence and deletion flag of the work center | Read | ECC + S/4 |
| PLKOTask List Header | Routing header: usage, status, lot size | Write | ECC + S/4 |
| MAPLAssignment of Task Lists to Materials | Material – routing assignment | Write | ECC + S/4 |
| PLASTask List Selection of Operations | Assignment of operations to the routing counter | Write | ECC + S/4 |
| PLPOTask List Operation | Operations: work center, control key, standard values | Write | ECC + S/4 |
BAPIs and functions used
- BAPI_ROUTING_EXISTENCE_CHECKCheck Routing Existence. Checks whether the material already has a routing with the same usage
- BAPI_ROUTING_CREATECreate Routing. Creates the routing with header, material assignment and operations
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful routings permanently
- BAPI_TRANSACTION_ROLLBACKRoll Back BAPI Transaction. Rolls back in test mode and for failed routings
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | — | Yes | C:\temp\yeni-rotalar.xlsx |
| P_DATUV | Valid from | Single value | PLKO-DATUV | Yes | 01.12.2026 |
| P_AENNR | Change number | Single value | PLKO-AENNR | No | 500000000455 |
| P_TEST | Test mode (check without posting) | Checkbox | — | No | X |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Material | MAPL-MATNR | Yes |
| 2 | Plant | MAPL-WERKS | Yes |
| 3 | Usage | PLKO-VERWE | Yes |
| 4 | Status | PLKO-STATU | No |
| 5 | Lot size from | PLKO-LOSVN | No |
| 6 | Lot size to | PLKO-LOSBS | No |
| 7 | Routing text | PLKO-KTEXT | No |
| 8 | Operation | PLPO-VORNR | Yes |
| 9 | Work center | CRHD-ARBPL | Yes |
| 10 | Control key | PLPO-STEUS | Yes |
| 11 | Operation text | PLPO-LTXA1 | No |
| 12 | Base quantity | PLPO-BMSCH | No |
| 13 | Setup time | PLPO-VGW01 | No |
| 14 | Machine time | PLPO-VGW02 | No |
| 15 | Labor time | PLPO-VGW03 | No |
| 16 | Time unit | PLPO-VGE01 | No |
Sample upload file
| 1 | Material * | Plant * | Usage * | Status | Lot size from | Lot size to | Routing text | Operation * | Work center * | Control key * | Operation text | Base quantity | Setup time | Machine time | Labor time | Time unit |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | FG-8100 | 1000 | 1 | 4 | 1 | 99,999,999 | Shelf unit R3 production | 0010 | PRES-01 | PP01 | Sheet cutting and bending | 10 | 30 | 6 | 6 | MIN |
| 3 | FG-8100 | 1000 | 1 | 4 | 1 | 99,999,999 | Shelf unit R3 production | 0020 | KAYN-02 | PP01 | Welding | 10 | 15 | 12 | 12 | MIN |
| 4 | FG-8100 | 1000 | 1 | 4 | 1 | 99,999,999 | Shelf unit R3 production | 0030 | BOYA-01 | PP01 | Powder coating | 10 | 20 | 8 | 4 | MIN |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Rows | Calculated File row range of the routing |
| 2 | Material | MAPL-MATNR |
| 3 | Plant | MAPL-WERKS |
| 4 | Operations | Calculated Number of rows in the group |
| 5 | Routing group | PLKO-PLNNR |
| 6 | Counter | PLKO-PLNAL |
| 7 | Status | Calculated Created, test passed, already exists or error |
| 8 | Message | Calculated BAPI return message or check error |
Sample result list
| Rows | Material | Plant | Operations | Routing group | Counter | Status | Message |
|---|---|---|---|---|---|---|---|
| 2–4 | FG-8100 | 1000 | 3 | 50000231 | 1 | Created | Routing 50000231 saved |
| 5–9 | FG-8200 | 1000 | 5 | Error | Row 7: work center MONT-09 does not exist in plant 1000 | ||
| 10–12 | FG-6100 | 1000 | 3 | 50000144 | 1 | Already exists | Routing exists for usage 1 |
How does the program work?
- The file (XLSX or CSV) is read; consecutive rows with the same material, plant and usage are grouped into one routing, each row being an operation.
- MARC confirms the material exists in the plant, CRHD that the work center is defined for the plant and not flagged for deletion; operation numbers must be ascending and unique.
- BAPI_ROUTING_EXISTENCE_CHECK checks whether the material already has a routing with the same usage; if so, the routing is skipped as ‘already exists’.
- For valid groups BAPI_ROUTING_CREATE is called with the header (usage, status, lot size range, text), the material assignment and the operations (work center, control key, text, base quantity, VGW01–VGW03 and unit); the valid-from date and change number come from the selection screen.
- In test mode the call is rolled back with BAPI_TRANSACTION_ROLLBACK; in a real run each routing is committed separately.
- The result list shows routing group, counter, number of operations and the BAPI message; rows of failed routings can be downloaded as an error file.
Performance notes
Each routing is processed with a separate BAPI call and commit; run files above a few thousand operations in the background. Do the work center and material checks in one read with the keys from the file.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file All rows of failed routings are downloaded in the same template.
- Runs as a background job
Authorization objects
- C_ROUTAuthorization to create routings
- C_ROUT_MATAssignment of the routing to materials
Frequently asked questions
Can component allocation and production resources/tools be loaded too?
The base template covers operations and standard values. Allocation of BOM components to operations and production resources/tools can be added to the template as separate sheets; each extra object increases the effort range.
Can existing routings be updated?
This program creates new routings. A separate change mode working with change numbers can be added to update standard values in existing routings; the changes can be audited in the routing standard value change report.
Does the program work on S/4HANA?
Yes. BAPI_ROUTING_CREATE is supported on S/4HANA. Because S/4HANA also needs a production version to use the routing, the program can optionally produce a version proposal for the new routing.
Packages that include this solution
BOM, Routing and Production Version Pack
A five-component pack that loads, changes and audits production master data: mass routing creation from Excel, mass BOM component changes, an audit of …
Related reports
Missing Production Versions Check Report for S/4HANA Migration
A custom ALV report that compares BOM alternatives, routings and production versions of in-house produced materials and lists, with a finding code, …
Routing Standard Value Change Audit Report
A custom ALV report that lists operations changed in routings within a date range, with the old and new setup, machine and labor standard values, the …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.