Most FICO tutorials start with a screenshot of a transaction code, which teaches you where to click and not what is happening. This one starts with the model, because once the model makes sense the screens explain themselves.
FICO is really two modules that are taught together. The distinction between them is the first thing to get straight, because almost every later concept sits on one side of it.
FI, Financial Accounting, exists to satisfy people outside the company. Statutory accounts, tax authorities, auditors, shareholders. It is bound by accounting standards and legal requirements, its periods are fixed, and its output is the balance sheet and profit and loss statement. You cannot be creative in FI, because the rules are set by somebody else. CO, Controlling, exists to satisfy people inside the company. Which department overspent, which product line actually makes money, what a job really cost to produce. There is no external standard governing it, so its structures are designed to answer management questions. This is why CO has objects with no FI equivalent, such as cost centres, internal orders and profitability segments.The same rupee of expense is usually recorded in both, once as a general ledger posting for the statutory accounts and once against a cost object so somebody can be held accountable for it. Understanding that duality is most of what separates people who have understood FICO from people who have memorised transaction codes.
Everything in FICO hangs off a small set of organisational units. Configure these wrongly at the start of a project and the mistake is expensive to undo, which is why they get so much attention in training.
| Unit | What it represents | Why it matters |
|---|---|---|
| Client | The highest level, a completely separate data environment | Master data defined here is shared by everything below it |
| Company code | A legal entity that produces its own statutory accounts | The central FI unit. If a business must file its own balance sheet, it needs a company code |
| Business area | An optional reporting segment across company codes | Largely superseded by profit centres in modern designs |
| Chart of accounts | The list of general ledger accounts available | Shared across company codes, which is what makes group reporting possible |
| Controlling area | The boundary within which cost accounting happens | The central CO unit. One controlling area can serve several company codes |
| Fiscal year variant | How the financial year is divided into periods | India commonly runs April to March, which is a configuration decision, not a default |
The relationship worth memorising is that a controlling area can contain several company codes, but only if they share a chart of accounts and a fiscal year variant. That single constraint explains a surprising number of design decisions on real projects.
In SAP, every financial transaction creates a document, and once posted a document is never deleted. If something is wrong you post a reversal, which is itself a document. The audit trail is therefore complete by construction rather than by policy.
Every document has a header carrying the date, the document type and the currency, and at least two line items, because postings must balance. Each line item carries a posting key that determines whether it is a debit or a credit and what kind of account it can post to. Document types control number ranges and which account types are permitted. When somebody says a posting is failing, the answer is very often the posting key or the document type rather than the amount.
This is also where the FI and CO duality shows up concretely. Post an expense in FI and the system will ask for a cost object, a cost centre or an internal order, because CO needs to know who is accountable. If it does not ask, somebody has configured a default, and knowing where that default lives is a genuinely useful skill.
People who struggle with FICO almost always started in the wrong place, usually by trying to learn CO before FI made sense, or by learning transaction codes before the structures those transactions operate on.
If you want the full topic-by-topic curriculum in that order, the SAP FICO syllabus is a free download, and the SAP FICO course page explains how the same sequence is delivered with a live system login so you configure each piece yourself rather than watching somebody else do it.