KSB1 — Cost Centers: Actual Line Items
KSB1 displays actual line items posted to cost centers. SAP's current documentation describes KSB1 as Cost Centers: Actual and the classic KSB1 report as Cost Centers: Actual Line Items. Use it to drill from a cost-center balance to the individual CO postings that created that balance. For order line items, use KOB1 instead.
This page covers KSB1, the standard transaction for drilling into actual cost line item detail on cost centers, orders and other CO objects. It focuses on why KSB1 totals frequently diverge from FI reports, what missing or duplicated lines actually indicate, and which table joins prove the discrepancy in the underlying data.
Published 20 Sept 2026· 582 words
Esta página ainda não está disponível em português.
Purpose
KSB1 is the Cost Center Accounting actual line-item report. It shows individual actual postings for one or more cost centers over a selected fiscal year and period range, with cost element/G/L account, CO document, amount, quantity, partner object, and other line-item attributes available through the layout.
When it is used
Use KSB1 when a cost center balance or variance needs document-level explanation: month-end review, allocation analysis, unexpected charges, manual repostings, activity allocations, or reconciliation of a cost-center report to its underlying actual postings. If the object under investigation is an internal/production/maintenance order, KOB1 is the corresponding order line-item report.
How to use it in practice
- Enter the controlling area, fiscal year/period range, and cost center or cost-center group.
- Optionally restrict by cost element/G/L account, business transaction, or other selection fields to keep the result focused.
- Execute and add document number, posting date, partner object, transaction currency/controlling-area currency, quantity, and user/reference fields to the layout as required.
- Double-click a line to navigate to its CO/accounting/source document where supported.
- Reconcile subtotals to the same cost-center report using the same period, currency, and value-type context.
Key data objects
The report is cost-center centric; the important keys are the cost center, controlling area, period, and actual line-item document context.
- Cost center and controlling area.
- Fiscal year and period range.
- Cost element/G/L account.
- CO/accounting document number and posting date.
- Partner object/business transaction for allocations and internal postings.
- Currency and quantity fields—compare reports using the same currency type.
How to prove it in the data
Run KSB1 for the exact cost center, periods, and account range in question and preserve the layout/selection. Drill into representative lines to their source documents. In S/4HANA, use the Universal Journal/released analytical views for new custom reporting rather than assuming classic COEP persistence; the business proof is the same line-item population and document trail shown by the standard report.
ECC vs S/4HANA
SAP's current S/4HANA 2025 data-archiving documentation still lists KSB1 as Cost Centers Actual, and SAP documentation also describes KSB1/KSB1N as cost-center actual line-item reports. S/4HANA integrates FI and CO actuals in the Universal Journal, so technical persistence differs from ECC even though the standard cost-center line-item investigation remains familiar.
Common pitfalls and how to diagnose them
- Calling KSB1 a generic report for orders or WBS elements; KSB1 is the cost-center actual line-item report.
- Comparing KSB1 to FI using different currencies or period selections.
- Ignoring allocation/reposting lines that are valid CO actuals and can make a cost-center view differ from a simple external-expense expectation.
- Running a very broad cost-center group and full-year selection when the incident concerns one period/account.
- Treating an empty result as data loss before checking controlling area, period, cost center validity, and authorization.
Whose problem this is
Primary ownership is CO Cost Center Accounting. FI joins for source accounting-document reconciliation, Security for authorization, and ABAP/Basis only when a standard report has a proven technical/runtime problem.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ksb1ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.