BAPI_ROUTING_CREATE — BAPI_ROUTING_CREATE for Routing Master Data

BAPI_ROUTING_CREATE creates a group routing, the task list object normally maintained through transaction CA01 (create routing) or CA02 (change). It writes the routing group and group counter, the header data (plant, usage, status, planner group), one or more sequences (standard, parallel, alternative), the operations within each sequence, and the assignment of the routing to a material so it can be used for order scheduling and costing. It is a master data creation BAPI, not a change BAPI: an existing routing group with the same key produces an error rather than an update. It is typically called from custom load programs, migration tooling, or PP-to-PP interfaces that need to generate routings from an external process planning system.

BAPI_ROUTING_CREATE does not commit. It builds the routing objects in the update task and returns before the database write is finalized. A separate call to BAPI_TRANSACTION_COMMIT is required to make the change durable; without it, the routing is rolled back at the end of the logical unit of work as though nothing happened. The dangerous part is that the BAPI itself can return a clean RETURN table with no error messages, so the caller has every reason to believe the routing was created. It is only on the next attempt to read or use that routing, sometimes in a completely separate program or the next day's batch run, that its absence is discovered.

RETURN is a table, and an empty table is the only completely safe signal of success. The recurring bug is checking sy-subrc after the function module call, which for an RFC-enabled function module is almost always zero regardless of application-level failure, or checking only whether RETURN[1] exists rather than scanning every line for type E or A. A routing create can fail partway through: the header writes but an operation is rejected because its work center does not exist in the target plant, and the resulting RETURN table mixes a success message about the header with an error message about the operation, with no single flag summarizing overall success. Correct handling loops the full table, treats any E or A type as a hard failure, and does not call the commit if one is found. Where the group and counter were left blank for the system to generate, they typically come back embedded in a success message's variables rather than as a clean output field, so interfaces that only read TASK_LIST_HEADER back out lose the generated key and later fail to attach materials or components to the routing they just created.

BAPI_ROUTING_CREATE continues to function on S/4HANA and is still the standard interface for programmatic routing creation; there is no widely adopted released public API that fully replaces it for this specific object. Mass data migration during a conversion project typically goes through the migration cockpit's own routing object rather than through this BAPI directly, but custom integrations and legacy interfaces built around it keep working unchanged. No version-specific behavior change to the parameter interface itself should be assumed without checking the target system directly.

Interface development owns the commit call and RETURN parsing; a missing commit or a swallowed error message in RETURN is a development defect regardless of what the functional team configured. Functional PP owns whether the routing content is correct: right work centers, right control keys, right sequence structure. When a routing appears missing, the first useful evidence is the full RETURN table from the failing call plus the group and counter the interface believed it created, not just a screenshot of CA03 showing nothing.

Mirrors transaction CA01 for creation and CA02 or CA03 for change and display. Underlying tables are PLKO for the routing header, PLPO for operations, PLFL for sequence links, and MAPL for the material-to-task-list assignment. Sibling BAPIs cover reading and changing routings and are usually paired with this one in a full load cycle: create the routing, then attach it to a production version or use it as input to production order creation.