3768898 - Planned order API returns empty BillOfOperationsGroup while the routing can be seen in Display Planned Order app

When trying to retrieve the routing information of a planned order via API (API_PlannedOrder or API_PLANNED_ORDERS), the response shows an empty BillOfOperationsGroup.
However, the routing information can be seen in Display Planned Order (MD13) app.

SAP S/4HANA Cloud Public Edition

1. Perform a read call to the API_PLANNED_ORDERS service for a planned order header (entity A_PlannedOrder).
2. Observe that fields such as BillOfOperationsGroup (and related bill of operations fields) are empty in the API response.
3. Open the same planned order in MD13 and observe that routing information is displayed there.

This is an expected discrepancy due to data mapping differences between Display Planned Order app and the OData API.

The app derives and displays the routing group by resolving it through the Production Version assigned to the planned order and its associated task list assignment, whereas the API service reads the fields directly from the planned order header table (PLAF). If the routing reference is not explicitly written back to PLAF-PLNNR / PLAF-PLNTY / PLAF-PLNKN, the API will return empty values even though the app can resolve and display them via the production version linkage.

And these fields are only written to PLAF when scheduling is executed on the planned order, because it is the scheduling run that resolves and binds the routing (task list) to the order. If the planned order is not scheduled yet, the API will return no BillOfOperationsGroup value.

1. Schedule the planned order so that routing (task list) is resolved and written to the PLAF record.
2. After scheduling completes, read the planned order again via API to retrieve BillOfOperationsGroup and related fields.

API_PLANNED_ORDERS, API_PlannedOrder, A_PlannedOrder, BillOfOperationsGroup, empty, MD13, Display Planned Order, PLAF, routing, task list, production version, scheduling, PLNTY, PLNKN, PLNNR , KBA , PP-PLO-ES-2CL , Enterprise Services in Planned Order (Public Cloud) , PP-PLO-2CL , Planned Orders (Public Cloud) , Problem