Setup Step 2 — Test the CC with a real FI posting (F-02)
RECOMMENDED
Layer 1 · FI Foundation · owned by FI
⏱️ ~10 min
F-02
🎯 Why this setting exists
Step 1 had you verify each sub-step in isolation. But the only true confirmation that everything works together is to post one real FI document. F-02 — a plain manual G/L posting — touches almost every Step 1 sub-step in a single transaction: it reads the Chart of Accounts (1E) to pick the G/L, the open posting periods (1B/1C) to accept today's date, the Field Status Variant (1D) to validate the fields, a number range (1F) to issue the document number, and the tolerance group (1G) to authorise the amount. If it saves with a document number, the foundation is solid. If it errors, the message names the exact sub-step that is incomplete — far cheaper to diagnose here than three steps deep in a failed PO.
💡 Easy example
This is like writing a ₨1,000 test cheque between two of your own accounts before you open the business to customers. PakSteel's accountant moves ₨1,000 from the cash drawer to the bank account — no real business happens, but if the cheque clears, it proves the chequebook is valid: the account numbers exist, the date is in an open month, and the bank accepts the entry.
If the test cheque bounces, you would much rather find out now — with a harmless ₨1,000 transfer — than when a real ₨5,000,000 supplier invoice fails to post on a Friday afternoon. Same idea: prove the plumbing works before the real water flows.
If the test cheque bounces, you would much rather find out now — with a harmless ₨1,000 transfer — than when a real ₨5,000,000 supplier invoice fails to post on a Friday afternoon. Same idea: prove the plumbing works before the real water flows.
🔗 How this connects to everything else
F-02 builds nothing permanent — it is a checkpoint. But what it proves is exactly the foundation that every later MM transaction stands on, which is why it earns its own step.
⬆️ Depends on (must exist first)
⬇️ Enables (what this unlocks)
- Confidence to build MM on top. A green F-02 proves the periods, field status, ledger and G/L extension actually work — so you can move to Step 3 (Plants) without doubt.
- It is also a fast pre-flight for any later FI-touching transaction: if F-02 posts but a goods receipt fails, you instantly know the problem is MM-side (periods OMSY / tolerances / Material Ledger), not the FI foundation.
🧩 Who owns it & why MM cares
FI This is an FI test transaction — an MM consultant will rarely post F-02 in real life. But MM must know how to run and read it, because MIGO and MIRO sit on the exact same FI foundation. If F-02 won't post, MIGO/MIRO won't either — and being able to prove that in 10 minutes saves hours of blaming the wrong module.
🔮 Links to other modules (now & later)
- FI Pure FI — the document lands in tables
BKPF(header) andBSEG(lines), the same place every MM-generated FI document goes. - No other module is involved at this step — which is precisely why it isolates the FI foundation so cleanly.
🔧 Configuration — fields & steps
F-02 · This is not a customizing step — it is a one-off test posting. No SPRO path; just run the transaction.
Action sequence — quick test post
- Run F-02
- Header section — fill:
- Document Date: today
- Posting Date: today
- Type:
SA(G/L journal) - Company Code:
PSPK - Currency:
PKR - Reference:
TEST001(any text) - Doc Header Text:
CC smoke test
- First line item:
- Posting Key:
40(debit G/L) - Account: a balance-sheet G/L that's safe to use — try
113100(Bank — Main Account) or100000(Cash). If unsure, run SE16N →SKB1→ BUKRS = PSPK to find an active G/L for PSPK. - Press Enter → next screen
- Amount:
1000.00 - Text:
Smoke test posting
- Posting Key:
- Second line item (must balance):
- Posting Key:
50(credit G/L) - Account: another balance-sheet G/L (different from line 1)
- Amount:
1000.00(must equal line 1)
- Posting Key:
- Click "Post" (Ctrl+S)
- System shows: "Document 100000000 was posted in company code PSPK" ✓
If you see the document number → the CC is FULLY FUNCTIONAL. Move to Step 3 (Plants).
💡 Why F-02 is the perfect smoke test
F-02 is the simplest possible FI transaction — just a debit and a credit. If it works, every more complex MM transaction (MIRO vendor invoice, MIGO goods receipt, F110 payment run) will also work for the same CC, because they all use the same underlying config (number ranges, periods, tolerance, field status). And if it fails, you instantly know which Step 1 sub-step is incomplete — far faster than debugging a failed PO three steps later.
🚨 Issues & fixes (from a live IDES)
Every F-02 error points back to a specific Step 1 sub-step. Read the message, fix that sub-step, re-post.
| Error message | Root cause | Where to fix |
|---|---|---|
| "Posting period MM YYYY is not open" | OB52 missing a row for today's date | Step 1 → 1C — add row covering current period |
| "Document number not in range 51 defined for CC PSPK" | FBN1 range 51 missing (or year-specific entry expired) | Step 1 → 1F — create range 51 (Year 9999) |
| "No field status variant assigned to CC PSPK" | OBY6 missing the FSV field | Step 1 → 1E — fill Field Status Variant = PSPK |
| "G/L account 113100 not created in CC PSPK" | G/L master not extended to your CC | Step 1 → 1J — extend 113100 via FS00 (or pick a G/L that IS extended) |
| "There is no item category assigned to account XXXXXX/INT" | G/L not classified for Document Splitting | Step 1 → 1I — classify the G/L |
| "Correct the Customizing settings for ledgers for the universal journal" | CC not assigned to ledger 0L / no accounting principle | Step 1 → 1H — FINSC_LEDGER |
| "Cost center XX does not exist" | The G/L you picked requires CO; CO not set up | Pick a balance-sheet G/L that doesn't need a cost center (cash, bank, vendor recon) |
| "Amount exceeds upper limits for posting" | OBA4 limits set too low | Step 1 → 1G — raise the values |
⚠️ Common gotcha
Don't pick a P&L account (expense/revenue) for the test — many require a cost object (cost center / profit center) and you'll get "account requires assignment to a CO object" before you've set up Controlling. Use two balance-sheet accounts (cash, bank, vendor/customer reconciliation) so the posting needs nothing but the FI foundation you just built. Full error-by-error troubleshooting is in the Troubleshooting Center.
✅ Verification
- The post itself is the verification: "Document 100000000 was posted in company code PSPK" = pass.
- View it: run FB03 → enter the doc number from F-02 → both line items visible.
- Or SE16N → table
BKPF→ BUKRS = PSPK → the document header appears. - Keep the books clean: run FB08 to reverse the test posting once you've confirmed it.
- Optional: repeat the whole test for
PSAE(1 AED debit / 1 AED credit) to prove the second company code too.