E ERP Atlas
404
CONFIGURATION WORKBENCHDesign, configure, transport, and prove

CO 404 · CONFIGURATION WORKBENCH

CO Configuration Workbench

Configure the smallest Controlling design that can assign, allocate, settle, and explain one representative value flow. Target-system IMG paths, Fiori apps, and compatibility transactions vary by edition and release.

Workbench rule

Begin with an approved management question and a representative business event. A configuration entry is not complete until source, assignment, allocation or settlement, reporting, and reconciliation evidence agree.

01

CONFIGURATION WORKBENCH

Set the organizational and reporting boundary

Define the controlling area and compatible company-code relationships. Confirm the chart, fiscal-year, currency, ledger, profit-center, and reporting design before building object masters.

Maintain in this order

  1. Confirm the business purpose, accountable owner, and release-specific application boundary.
  2. Record the affected Customizing, master-data, and transactional objects separately.
  3. Transport only project-owned Customizing entries using the approved path; do not treat master data or period-end execution as transport content.
  4. Run a positive case, an exception, a correction, and a reconciliation before extending scope.
EXPECTED PROOFOKKP and related enterprise-structure settings are release- and scope-sensitive. Prove that a representative posting accepts the intended real object and reports in the intended management dimensions.
FAILURE CHECK

Trace the source document, G/L account behavior, real object, validity date, sender/receiver selection, driver, period, run log, and report filter before changing configuration.

02

CONFIGURATION WORKBENCH

Create governed cost-accounting master data

Define or extend cost centers, activity types, internal-order types, orders, hierarchies, responsible owners, validity dates, profit-center assignments, and lock/status rules.

Maintain in this order

  1. Confirm the business purpose, accountable owner, and release-specific application boundary.
  2. Record the affected Customizing, master-data, and transactional objects separately.
  3. Transport only project-owned Customizing entries using the approved path; do not treat master data or period-end execution as transport content.
  4. Run a positive case, an exception, a correction, and a reconciliation before extending scope.
EXPECTED PROOFCreate one operating cost center, one support cost center, one activity type, and one overhead order. Post a controlled source cost and prove master-data validity and responsibility reporting.
FAILURE CHECK

Trace the source document, G/L account behavior, real object, validity date, sender/receiver selection, driver, period, run log, and report filter before changing configuration.

03

CONFIGURATION WORKBENCH

Design account assignment and real/statistical behavior

Align the G/L account behavior, permitted CO objects, defaults, substitutions, validations, and statistical assignments. In S/4HANA, do not model primary cost elements as a separate design without confirming the target release behavior.

Maintain in this order

  1. Confirm the business purpose, accountable owner, and release-specific application boundary.
  2. Record the affected Customizing, master-data, and transactional objects separately.
  3. Transport only project-owned Customizing entries using the approved path; do not treat master data or period-end execution as transport content.
  4. Run a positive case, an exception, a correction, and a reconciliation before extending scope.
EXPECTED PROOFPost one expense with a real cost center and a statistical order. Prove Financial Accounting has one cost, CO has one real owner, and the order view is informational only.
FAILURE CHECK

Trace the source document, G/L account behavior, real object, validity date, sender/receiver selection, driver, period, run log, and report filter before changing configuration.

04

CONFIGURATION WORKBENCH

Build allocation and settlement rules

Choose distribution, assessment, activity allocation, Universal Allocation where in scope, and internal-order settlement based on the economic rule. Document sender, receiver, driver, period, reversal, approval, and run ownership.

Maintain in this order

  1. Confirm the business purpose, accountable owner, and release-specific application boundary.
  2. Record the affected Customizing, master-data, and transactional objects separately.
  3. Transport only project-owned Customizing entries using the approved path; do not treat master data or period-end execution as transport content.
  4. Run a positive case, an exception, a correction, and a reconciliation before extending scope.
EXPECTED PROOFRun a small controlled allocation and one order settlement. Reconcile sender credits, receiver debits, quantity or driver, and residual balance to the approved rule.
FAILURE CHECK

Trace the source document, G/L account behavior, real object, validity date, sender/receiver selection, driver, period, run log, and report filter before changing configuration.

05

CONFIGURATION WORKBENCH

Connect product cost and profitability evidence

For approved manufacturing scope, align product-cost planning, cost objects, goods movements, period-end close, variance, settlement, and Margin Analysis. Keep complex actual costing, Material Ledger, WIP, and results-analysis design as separately governed extensions.

Maintain in this order

  1. Confirm the business purpose, accountable owner, and release-specific application boundary.
  2. Record the affected Customizing, master-data, and transactional objects separately.
  3. Transport only project-owned Customizing entries using the approved path; do not treat master data or period-end execution as transport content.
  4. Run a positive case, an exception, a correction, and a reconciliation before extending scope.
EXPECTED PROOFExecute a representative manufactured-product or service scenario and show source cost, activity quantity, production cost object, inventory or cost outcome, variance, and profitability dimensions.
FAILURE CHECK

Trace the source document, G/L account behavior, real object, validity date, sender/receiver selection, driver, period, run log, and report filter before changing configuration.

TRANSACTIONAL PROOF

One controlled overhead-cost scenario

Use a support cost center, operating receiver, overhead order, and measurable driver. The scenario should be small enough to explain line by line.

  1. 01
    Source posting

    Post an approved expense to a real support cost center and statistical order; retain the source and journal references.

  2. 02
    Activity or allocation

    Confirm a measurable service or run the approved allocation cycle with its sender, receiver, and driver.

  3. 03
    Settlement

    Settle the order to its approved receiver and inspect the settlement rule and log.

  4. 04
    Reconciliation

    Reconcile Financial Accounting amount, real CO owner, statistical context, sender credit, receiver debit, and remaining balance.

TECHNICAL REFERENCES

Verify against the target release

The target system and approved SAP scope remain authoritative. These official SAP references anchor the learning design.

READY FOR THE PROJECT?Continue to CO 505

Apply the workbench in discovery, design, integrated testing, close rehearsal, cutover, and stabilization.

Enter the project →