SAP FICO Configuration Steps – A Step-by-Step Implementation Guide
Configure the FICO backbone in S/4HANA: create your company code, set fiscal year variants, prepare the chart of accounts, and control posting periods. Below you’ll find SPRO paths, essential tcodes, and quick testing tips.
👉 Enroll in SAP FICO Training in Vizag (Softenant)
Prerequisites & Landscape
- Scope & org plan: enterprise structure (Company, Company Code, Controlling Area).
- Currency decisions: company code currency, group currency, parallel currencies.
- Baseline chart of accounts (operating COA) and account groups.
- Authorizations to IMG (SPRO) and FI/CO config activities.
Tip: Document decisions in a config workbook before making changes in the IMG.
Key SPRO Paths & Tcodes
Task | SPRO Path | Tcode (classic) |
---|---|---|
Company Code | Enterprise Structure → Definition → Financial Accounting → Define Company / Define Company Code | OX15 |
Assign Company ↔ Company Code | Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Company | OX16 |
Fiscal Year Variant | Financial Accounting (FI) → Financial Accounting Global Settings → Fiscal Year → Maintain FY Variant | OB29 |
Assign FY Variant to Co. Code | FI Global Settings → Fiscal Year → Assign Company Code to FY Variant | OB37 |
Chart of Accounts | FI Global Settings → Ledgers → Master Data → G/L Accounts → Edit Chart of Accounts List | OB13 |
Assign COA to Co. Code | G/L Master Data → Preparations → Assign Company Code to Chart of Accounts | OB62 |
Posting Period Variant | FI Global Settings → Posting Periods → Define & Assign Posting Period Variant | OBBO / OBBP |
Open/Close Posting Periods | FI Global Settings → Posting Periods → Open and Close Periods | OB52 |
Paths may appear slightly different in S/4HANA but the sequence remains similar.
Step 1 — Company Code Creation
- Define Company (consolidation level): name, country, currency.
- Create Company Code: address, country, language, currency, FY variant placeholder.
- Assign Company Code → Company.
Field | Example | Notes |
---|---|---|
Company Code | 1000 | 4-character ID (A–Z/0–9) |
Currency | INR | Set group/parallel currencies later if required |
Country | IN | Drives localizations (tax, address, formats) |
You can copy an existing company code as a template (e.g., EC01), then update specifics.
Step 2 — Define & Assign Fiscal Year Variant
- Create or reuse a Fiscal Year Variant (FYV): e.g., K4 (Jan–Dec) or custom Apr–Mar.
- Set periods (12 normal + special periods for adjustments).
- Mark year-dependent if month lengths vary by year.
- Assign FYV → Company Code.
Setting | Typical Value | Impact |
---|---|---|
FYV | K4 / Custom (A4 for Apr–Mar) | Controls posting period calendar |
Periods | 12 + 4 special | Special periods for year-end adjustments |
Year-Dependent? | Yes/No | Use “Yes” for 4-4-5 or irregular month lengths |
Once transactions exist, changing FYV is complex—finalize early.
Step 3 — Chart of Accounts (COA)
- Define COA: COA ID, description, language, length of G/L number, group chart if used.
- Assign COA → Company Code.
- Create Account Groups and Field Status (controls required/optional fields).
- Maintain G/L Master templates (balance sheet vs P&L, open item management, tax relevant).
Decision | Option | Consideration |
---|---|---|
Account length | 6–10 digits | Room for growth; aligns with legacy mapping |
Open item mgmt | On/Off | Enable for reconciliation-style accounts |
Recon accounts | AR/AP/Assets | Auto-updated from subledgers; no direct postings |
Use a group COA for consolidation mapping if multiple operating COAs exist.
Step 4 — Posting Period Variant & Period Control
- Define PPV (Posting Period Variant) and rules (account type + period ranges).
- Assign PPV → Company Code.
- Use OB52 to Open/Close Periods per account type and authorization group.
- Set special periods for year-end adjustments.
Acct Type | From/To Period | FY | Auth Group | Notes |
---|---|---|---|---|
+ | 01 → 12 | 2025 | FI_CLERK | Opens for all account types |
A / D / K / S / M | 01 → 12 | 2025 | FI_MGR | Fine control by asset, customer, vendor, G/L, material |
Lock periods promptly after close; use authorization groups to restrict late postings.
Optional: Number Ranges, Document Types, Tolerances
- Document Types (OBA7): e.g., SA G/L, KR Vendor, DR Customer; posting keys.
- Number Ranges (FBN1): per company code & fiscal year.
- Tolerance Groups (OBA0): user/customer/vendor tolerances.
- Field Status Variant (OBC4): control document field behavior.
These controls prevent data-entry errors and standardize postings across teams.
Testing & Common Errors
Quick Smoke Test
- Create a sample G/L and post a document (FB50 / Fiori app).
- Post a vendor invoice (FB60) and customer invoice (FB70).
- Run depreciation test if AA is in scope (AFAB).
Frequent Issues
- “Posting date not in permitted range” → Maintain OB52 for that account type.
- “Account not defined in chart” → Create G/L in operating COA & extend to company code.
- “Balance in transaction currency” → Check currency settings & exchange rates.
- “No fiscal year variant assigned” → Ensure FYV is assigned to company code (OB37).