FI / FICOadvanced

FICO Cost Center Accounting Part 5: Integration, Reconciliation and Troubleshooting

Key takeaway

Support cost center postings in production: "account requires an assignment to a CO object" errors, locked or invalid cost centers, wrong default assignments, missing profit centers, allocation issues, and why FI and CO always reconcile in S/4HANA — with a troubleshooting path.

Explanation

📌 KEY POINTS
✅ P&L accounts of type primary cost require a CO object — missing cost center stops the posting.
✅ Lock indicators and validity dates cause errors on otherwise valid cost centers.
✅ In S/4HANA FI and CO share ACDOCA lines, so they reconcile; differences are about wrong objects, not totals.
✅ Analyse with line item reports and document display; correct at source or repost.
⚠️ Creating a catch-all cost center to avoid errors destroys cost responsibility.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered architecture. Now support.

━━━━━━━━━━━━━━━━━━━━
▶ 1. POSTING ERRORS

Missing CO object; locked cost center; invalid date.

━━━━━━━━━━━━━━━━━━━━
▶ 2. WRONG ASSIGNMENTS

Defaults, substitutions, user errors.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ALLOCATION ISSUES

Missing SKFs, sender empty, wrong sequence.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RECONCILIATION

FI vs CO totals equal; object-level analysis.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CORRECTIONS

Reposting; fixing master data and defaults.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Reproduce the error.
Check account type, cost center status/validity.
Fix master data or input; repost if needed.

✅ CHECKPOINT: cause documented and prevented.

Code example

ABAP Code

===== TYPICAL ERRORS → CHECKS ====="Account … requires an assignment to a CO object" → enter cost center/order; review OKB9"Cost center … is locked for primary postings" → category/lock indicator"Cost center … not valid on date" → validity periodMissing profit center → cost center master data ===== ANALYSIS =====KSB1 | FB03 (CO objects on lines) | KB11N reposting

Real project scenario

A user in production support reported a vendor invoice failing with a CO object error. The expense account had been changed to primary cost type, making a cost center mandatory. Training AP on cost center entry and adding a default for one generic account solved it.

Common mistakes

Catch-all cost centers.
Removing account types to avoid errors.
Mass reposting habits.
Ignoring validity.
No root cause.

Best practices

Fix at source.
Maintain validity and locks carefully.
Minimal defaults.
Document causes.
Train users.

Interview angle

Questions: "Why does a posting require a CO object?", "Why can FI and CO not differ in S/4HANA?", "How do you troubleshoot cost center errors?"
Strong answer: account type, locks/validity, defaults, ACDOCA reconciliation, correction path.

Practice this lesson

Quick check

1. A valid cost center rejects postings. What should be checked?

2. An invoice fails with "account requires an assignment to a CO object". What is the meaning?

3. Why can FI and CO totals no longer differ in S/4HANA?

Interview questions

1. Users report cost center posting errors and managers see costs on wrong cost centers. What is your support approach?

Answer it in your own words first, then compare.

2. A production issue is reported in Cost Center Accounting. What would you check first, and how would you troubleshoot it systematically?