KO03 — Display Internal Order Master Data

KO03 opens the display view of an internal order's master record: order type, controlling area, company code, responsible cost center, business area, profit center, budget profile, and the settlement rule that determines where costs eventually land. The structural fact that explains most confusion: this transaction is read-only and shows configuration and status, never a running balance. The order's system status (created, released, technically complete, closed) is not editable here but is the single most consulted field, because that status - not any authorization or config setting - is usually what is blocking or allowing postings against the order elsewhere in FI or MM.

Reached for constantly as a first diagnostic step whenever a posting to an internal order fails or behaves unexpectedly - before touching FB60, FB50, MIRO or any goods movement that references the order. Also used to confirm an order exists in the expected controlling area, to check who the responsible cost center is before a cost allocation discussion, and to inspect the settlement rule when month-end settlement runs are producing unexpected results. For actual cost review, KOB1 or the order's line item report is the right tool, not KO03; for changing anything found here, KO02 is the tool, not this transaction.

In SE16 or SE16N, pull AUFK filtered on the order number to get its object number (OBJNR) and controlling area. Then query JEST filtered on that same OBJNR and on the inactive indicator being blank, to see the currently active status entries - this tells whether the order is released, technically complete or closed, independent of what the KO03 screen implies. If the question is settlement, filter COBRA on the same order number to confirm a settlement rule exists at all before assuming it is misconfigured.

KO03 is unchanged functionally on S/4HANA; internal order master data and its status logic work the same way ECC did. Fiori apps exist for browsing and managing internal orders in newer releases, but the underlying master data model and status behaviour are the same, so diagnosis on the classic transaction remains valid regardless of which front end raised the question.

Functional CO problem in almost every case - order status, settlement rule, and controlling area assignment are all configuration and master data decisions owned by controlling. A clean handover states the order number, the exact status found in JEST, and whether a settlement rule exists, so the receiving consultant does not have to re-run the same lookup.

KO01 and KO02 are the create and change counterparts and are where any status or settlement rule correction actually happens. KOB1 and KSB1 answer the actual-cost question that KO03 cannot. KS01, KS02 and KS03 are worth checking when the order's responsible cost center itself looks wrong, since that assignment is master data on the cost center side, not the order side. KP06 is relevant when the budget profile referenced in KO03 traces back to a planning layout question.