Orders Without Settlement Rule or With Unsettled Balance Report
Short answer: 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.
- Estimated effort
- M · 3–4 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Controllers, CO teams running the month-end close and production cost owners.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| AUFKOrder Master Data | Order master: category, type, description, object number (driving table) | — | ECC + S/4 |
| COBRASettlement Rule for Order Settlement | Settlement rule header and settlement profile | COBRA-OBJNR = AUFK-OBJNR | ECC + S/4 |
| COBRBSettlement Rule Distribution Rules | Distribution rules: receiver type, receiver, percentage, validity | COBRB-OBJNR = AUFK-OBJNR | ECC + S/4 |
| COSPCO Object: Cost Totals for External Postings | Primary actual costs and settlement credits | COSP-OBJNR = AUFK-OBJNR | ECC + S/4 |
| COSSCO Object: Cost Totals for Internal Postings | Secondary actual costs and settlement credits | COSS-OBJNR = AUFK-OBJNR | ECC + S/4 |
| JESTIndividual Object Status | System status (REL, TECO, DLV, CLSD) | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |
| TKA01Controlling Areas | Controlling area currency | TKA01-KOKRS = AUFK-KOKRS | ECC + S/4 |
S/4HANA notes
- COSP → ACDOCA: In S/4HANA COSP is a view, not a table; actual totals are calculated from ACDOCA.
- COSS → ACDOCA: In S/4HANA COSS is a view, not a table; internal actual postings are read from ACDOCA.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_KOKRS | Controlling area | Single value | AUFK-KOKRS | Yes | 1000 |
| S_AUFNR | Order | Range / multiple | AUFK-AUFNR | No | — |
| S_AUTYP | Order category | Range / multiple | AUFK-AUTYP | No | 01, 10 |
| S_AUART | Order type | Range / multiple | AUFK-AUART | No | 0400 |
| P_GJAHR | Fiscal year | Single value | COSS-GJAHR | Yes | 2026 |
| P_PERIO | Period | Single value | — | Yes | 10 |
| P_NORULE | Only orders without a rule | Radio button | — | No | — |
| P_ALL | Orders without a rule and with a balance | Radio button | — | No | X |
| P_TOLAMT | Balance tolerance | Single value | — | No | 1 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Order | AUFK-AUFNR |
| 2 | Description | AUFK-KTEXT |
| 3 | Category | AUFK-AUTYP |
| 4 | Order type | AUFK-AUART |
| 5 | Created on | AUFK-ERDAT |
| 6 | System status | Calculated Short text of the active system statuses in JEST |
| 7 | Rule exists | Calculated A COBRB line valid in the period with a percentage total > 0 |
| 8 | Receiver | Calculated COBRB-KONTY and the receiver object (KOSTL, AUFNR, HKONT, ANLN1…) |
| 9 | Period debit | Calculated Non-settlement debits in P_PERIO, COSP + COSS value type 04 |
| 10 | Balance | Calculated COSP + COSS value type 04 total from the start of the year to P_PERIO (settlement included) |
| 11 | Issue | Calculated No rule, period not settled, or balance after settlement |
| 12 | Currency | TKA01-WAERS |
Sample output
| Order | Description | Category | Order type | Created on | System status | Rule exists | Receiver | Period debit | Balance | Issue | Currency |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 400152 | Office relocation costs | 01 | 0400 | 09/08/2026 | REL | No | 84,600 | 84,600 | No rule, costs posted | TRY | |
| 400118 | Dealer training programme | 01 | 0400 | 03/14/2026 | TECO | Yes | Cost center 4300 | 18,500 | 18,500 | Period not settled | TRY |
| 1000081 | Plastic crate 40 L | 10 | PP01 | 10/02/2026 | DLV | Yes | Material 300045 | 0 | 12,840 | Balance after settlement | TRY |
How does the report work?
- 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.
- 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”.
- 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”.
- The period debit is the non-settlement debit posted in the selected period; it highlights orders that receive costs without a rule.
- For production orders, a balance in status delivered (DLV) or technically complete (TECO) is flagged separately as an unsettled variance or work in process.
Performance notes
First find the objects with a balance from the COSP/COSS totals, then read COBRA/COBRB and JEST only for those orders. This order of reads shortens the runtime noticeably for large numbers of orders.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document The order opens KO03, or KKBC_ORD for production orders.
- Export to Excel
- Runs as a background job Can run in the close calendar right after the settlement jobs.
- Send the result by email
Authorization objects
- K_ORDERInternal order display authorization by order type
- C_AFKO_AWKProduction 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.
Packages that include this solution
Month-End Close Control Pack
A pack that lists the five topics to clean up before the close with one company code and period selection: parked documents, unmatched bank items, …
Related reports
Internal Order Budget Availability Report
A custom ALV report that compares the annual or overall budget of internal orders with actual costs and open commitments, and shows the remaining …
Production Order Target vs Actual Cost Variance Report
A custom ALV report that compares the actual cost of production orders in a plant with the target cost from delivered quantity × standard price, and …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.