COBRA table — Settlement Rule Header for Order and WBS Settlement

A row in COBRA represents the header of a settlement rule attached to one sender object, identified by its object number OBJNR. The sender is typically an internal order, a WBS element, a network activity, or another CO object that accumulates costs and needs to pass them on. COBRA does not hold the receivers or the split percentages; it holds the metadata of the rule itself, principally whether settlement is period-based or full, and the reference date used to determine which fiscal period a periodic settlement run applies to. The individual distribution lines, each naming a receiver type, a receiver, a percentage or fixed amount and a validity window, live in a separate child table keyed by the same object number. COBRA is therefore a thin, mostly stable table compared to the volume of postings that settlement actually generates downstream.

Always restrict on MANDT first. OBJNR is the only field worth filtering on for a targeted lookup; it is not the order number or WBS element as written on the business document, it is the converted object number, so convert the business key before querying rather than searching for it directly in COBRA. The table itself is small relative to CO actuals tables, so a scan restricted to a single object is instant, but pulling COBRA for a whole order type or company code without any OBJNR range is unnecessarily slow and rarely the right diagnostic anyway, since the rule header alone answers almost nothing about amounts. Filter out LOEKZ-set rows when the question is 'does this object currently have an active settlement rule'.

Symptom: an order fails settlement with 'no settlement rule maintained' or settles only partially. Convert the order or WBS element to its object number, then select COBRA for that OBJNR. No row at all confirms the first error exactly as stated. A row present but with LOEKZ set means the rule was deleted, which reproduces the same error even though a row exists. If the header row is fine, move to the distribution rule child table for the same OBJNR and check whether the percentages across active receiver lines sum to 100, since a header without a complete distribution is the usual cause of partial settlement.

COBRA remains a classic transparent table on S/4HANA; the settlement rule concept for orders, WBS elements and networks was not redesigned as part of the universal journal move. It has not been replaced by a compatibility CDS view. What changed is where the resulting postings end up: CO actuals that used to live only in classic CO totals and line item tables are now also reflected in ACDOCA, so tracing a settlement's financial effect increasingly means following OBJNR into ACDOCA rather than only into the older CO line item tables.

The recurring mistake is treating 'a row exists in COBRA' as proof that settlement will work. It only proves a header exists.

Settlement rule configuration, allocation structures and settlement profiles are owned by the FI/CO consultant responsible for controlling configuration. Whether a specific object should even have a settlement rule, and to which receiver, is a functional call owned jointly with whoever owns the sender object, PS for WBS elements and networks, PM or PP for orders, depending on the landscape.

The distribution rule child table (commonly referred to as COBRB in CO discussions) carries the receiver-level detail that COBRA lacks and should be checked in the same breath. Sender masters such as AUFK for orders and PRPS for WBS elements supply the object that OBJNR points back to. Individual and collective settlement is executed through order and WBS settlement transactions, and the resulting postings appear in the CO line item and universal journal tables rather than in COBRA itself.