RBCO table — RBCO Commitment Totals for CO Objects

One row in RBCO represents the aggregated open commitment value for a specific CO account assignment object, in a given fiscal year and value type, arising from a purchase requisition or purchase order that has not yet been fully consumed by goods receipt or invoice. It is a totals table analogous to the CO actuals totals tables, not a document-level ledger: as a PO or PR is created, changed, reduced by GR/IR, or reorganized, the relevant row is updated or a new row is written rather than the history being preserved line by line. Budget availability control (active availability control on internal orders, WBS elements, cost centers) and commitment line item reports both ultimately depend on values that trace back to this table.

Always restrict by MANDT first, then by GJAHR and, where possible, OBJNR or EBELN before pulling rows; this is a totals table that accumulates across the life of every open commitment item in the system and can be very large on systems with high PO volume or long-running WBS elements. Do not attempt a full table scan to reconcile commitments across a company code; start from the CO object or the purchasing document and narrow from there. Because WRTTP and VERSN separate different commitment categories, summing across them without filtering produces numbers that do not match any single report.

Symptom: an internal order or WBS element shows consumed budget against a commitment that no longer appears as an open PO in standard purchasing lists. Select RBCO for MANDT, GJAHR of the current fiscal year, and OBJNR of the object in question. If a nonzero row remains while the referenced EBELN and EBELP in EKPO show the item as deleted, blocked, or fully invoiced in EKBE, the commitment update or carryforward that should have zeroed the row did not run.

RBCO originates from classic CO commitment management and is not one of the tables affected by the S/4HANA simplification of the material document and FI line item data models. Where classic active availability control and commitment reporting are still in use in S/4HANA, RBCO continues to be populated the same way. Some newer reporting apps for budget and commitment monitoring read through compatibility or analytic views instead of the table directly, but the underlying persistence and update logic have not been rebuilt.

A controlling or project systems consultant responsible for availability control and budget monitoring owns discrepancies in the commitment value shown against a cost center, order or WBS element. The MM buyer's scope stops at whether the purchase order itself is open, closed, blocked or fully invoiced; reconciling that against the CO-side commitment balance is a controlling-side investigation.

EKKO and EKPO are the purchase order header and item that generate the commitment; EKKN carries the account assignment distribution that determines the CO object stored in OBJNR; EBAN represents the originating requisition where the commitment starts before a PO exists; EKBE records the goods receipt and invoice postings that reduce the commitment. None of these tables are maintained directly; they are written by purchase order and requisition transactions, goods receipt and invoice verification postings, and periodic commitment carryforward or reorganization programs.