# Orders Without Settlement Rule or With Unsettled Balance Report

> A custom ALV report that lists orders that received costs but have no settlement rule, and internal and production orders that still carry a balance after the period-end settlement. It surfaces costs left behind on orders at the month-end close.

- Type: Report, Custom development, ALV report
- Module: CO
- Estimated effort: M (3–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/orders-without-settlement-rule-report/


## Why is the standard not enough?

KO88 only gives an error log for the orders included in the run; orders without a rule stay as messages in the log and there is no consolidated check list after the close. KO03 shows the settlement rule per order. Costs left on orders at month end are therefore usually noticed later, when reports do not reconcile.

### Closest standard alternatives

- KO88: Settles orders and reports errors in a log; offers no consolidated check list after the close.
- KO03: Shows the settlement rule per order.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| AUFK | Order master: category, type, description, object number (driving table) | Read | - | ECC + S/4 |
| COBRA | Settlement rule header and settlement profile | Read | COBRA-OBJNR = AUFK-OBJNR | ECC + S/4 |
| COBRB | Distribution rules: receiver type, receiver, percentage, validity | Read | COBRB-OBJNR = AUFK-OBJNR | ECC + S/4 |
| COSP | Primary actual costs and settlement credits | Read | COSP-OBJNR = AUFK-OBJNR | ECC + S/4 |
| COSS | Secondary actual costs and settlement credits | Read | COSS-OBJNR = AUFK-OBJNR | ECC + S/4 |
| JEST | System status (REL, TECO, DLV, CLSD) | Read | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |
| TKA01 | Controlling area currency | Read | TKA01-KOKRS = AUFK-KOKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_KOKRS | Controlling area | Single value | AUFK-KOKRS | Yes |
| S_AUFNR | Order | Range / multiple | AUFK-AUFNR | No |
| S_AUTYP | Order category | Range / multiple | AUFK-AUTYP | No |
| S_AUART | Order type | Range / multiple | AUFK-AUART | No |
| P_GJAHR | Fiscal year | Single value | COSS-GJAHR | Yes |
| P_PERIO | Period | Single value | - | Yes |
| P_NORULE | Only orders without a rule | Radio button | - | No |
| P_ALL | Orders without a rule and with a balance | Radio button | - | No |
| P_TOLAMT | Balance tolerance | Single value | - | No |

## Output columns

| Column | Source |
|---|---|
| Order | AUFK-AUFNR |
| Description | AUFK-KTEXT |
| Category | AUFK-AUTYP |
| Order type | AUFK-AUART |
| Created on | AUFK-ERDAT |
| System status | Calculated: Short text of the active system statuses in JEST |
| Rule exists | Calculated: A COBRB line valid in the period with a percentage total > 0 |
| Receiver | Calculated: COBRB-KONTY and the receiver object (KOSTL, AUFNR, HKONT, ANLN1…) |
| Period debit | Calculated: Non-settlement debits in P_PERIO, COSP + COSS value type 04 |
| Balance | Calculated: COSP + COSS value type 04 total from the start of the year to P_PERIO (settlement included) |
| Issue | Calculated: No rule, period not settled, or balance after settlement |
| Currency | TKA01-WAERS |

## How does the report work?

1. Orders matching the selection (internal orders, production orders and other categories) are read from AUFK; the active system status comes from JEST and closed orders are skipped.
2. Settlement rule: the COBRA header and the COBRB distribution rules are read; if there is no rule valid in the selected period, or the percentages add up to zero, the status is "No rule".
3. Balance: value type 04 amounts in COSP and COSS, settlement credits included, are summed from the start of the fiscal year up to P_PERIO. If the absolute balance exceeds P_TOLAMT, the status is "Balance after settlement".
4. The period debit is the non-settlement debit posted in the selected period; it highlights orders that receive costs without a rule.
5. For production orders, a balance in status delivered (DLV) or technically complete (TECO) is flagged separately as an unsettled variance or work in process.

## Authorization objects

- K_ORDER: Internal order display authorization by order type
- C_AFKO_AWK: Production order authorization by plant and order type

## Frequently asked questions

### Are statistical orders listed too?

No. Statistical orders are not settled, so they are excluded by default; they can be made visible with a separate selection if needed.

### Is a balance on a production order always an error?

No. On orders that are not fully delivered, the balance is work in process and is normal. The report flags separately the balance left on delivered or technically complete orders; this is usually an unsettled variance.

### Does it work on S/4HANA?

Yes. COBRA, COBRB and JEST are used the same way; COSP and COSS are read as compatibility views and actuals come from ACDOCA.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=co-orders-settlement-check
