CA03 — Display Routing (Task List)

CA03 is the display-only counterpart to CA01 (create) and CA02 (change) for task lists, the master data object SAP calls a routing when used for discrete or process manufacturing. A task list header carries usage, status, and validity; each operation line carries the work center, control key, and standard values (setup, machine, labor times); components can be allocated to specific operations rather than left at the header level. The structural fact that drives most confusion is that a task list is not owned by a material. It is identified by task list type, group, and group counter. A material only gets connected to it through a material-task list assignment record, and several such assignments, or several counters within the same group, can exist for one material at one plant, each valid for a different lot size range or date window.

CA03 gets used mid-incident, after a production or process order has already been created or confirmed with operations, standard values, or components that look wrong. The consultant opens CA03 to see what the master data actually says before deciding whether the order is out of sync with the routing or the routing itself is wrong. It is also used during scheduling investigations, since routing standard values and control key settings drive lead time and capacity calculations picked up by CO01/CO02 order creation. It is not the tool for fixing anything - any correction goes through CA02, and any question about which routing a specific order used goes to the order's operation overview in CO03, not back to CA03. In S/4HANA the same read-only need can be met from a routing-focused Fiori app, but CA03 remains the faster path for most consultants already in the GUI.

Start in MAPL filtered on material number and plant to get every task list group and counter assigned to that material, and note the lot size range on each row. Take the group and counter into PLKO to check status, usage, and validity dates - a task list with a deletion flag set or a validity window that has expired will not be picked even though MAPL still lists it. Then filter PLPO on the same task list type, group, and counter to see the actual operations and standard values, and PLMZ on the same key to see which components are tied to which operation rather than sitting loose at the order header.

CA03 and its underlying tables are unchanged in S/4HANA; the task list group/counter structure and the material assignment logic through MAPL work the same way. S/4HANA adds Fiori apps for viewing routing and work center data in a worklist style, useful for browsing across many materials at once, but CA03 remains fully supported for single-object display and is usually faster for a targeted lookup during an incident.

This sits with the functional PP process planning or production planning consultant maintaining routings. Basis has no role beyond authorization and transport issues; ABAP only gets involved if a custom check or BAdI alters routing selection or standard value derivation. A good handover includes the material, plant, task list group and counter under investigation, and the specific order number whose operations look wrong.

Read CA01 and CA02 next to understand how the same task list gets created and changed, since CA03 only exposes what those transactions produced. CS03 is worth checking alongside CA03 when component allocation looks wrong, since the routing only references BOM items, it does not own them. CR03 explains where the standard value formulas and capacity data referenced by each operation actually live. CO03 shows what an order copied from the routing at creation time, which is the comparison point for any mismatch investigation.