SAP Library / FICO / Cheat sheet
SAP FICO cheat sheet
27 objects in 4 groups. Each links to its full reviewed page.
T-Codes12
- FB50FB50 posts a general ledger journal entry as a single multi-line document, entering all debit and credit lines on one screen rather than the header-then-line sequence used by FB01. It is the standard transaction for manual journal entries, accruals, reclassifications and corrections that do not originate from a vendor or customer invoice.
- FB60FB60 posts a vendor invoice directly in Financial Accounting with no purchase order behind it. It creates a document with a vendor line hitting the reconciliation account from the vendor master and one or more G/L expense lines. Used for invoices outside procurement scope: rent, utilities, services, freight, subsequent debits. Not the same as MIRO, which matches invoices to a PO.
- FB70FB70 is the one-screen ('enjoy') transaction for posting a customer invoice directly in Financial Accounting, debiting the customer reconciliation account and crediting revenue or other G/L accounts. It bypasses Sales and Distribution entirely, so it produces no billing document, no delivery reference and no SD pricing procedure. It is used when the invoice originates outside SD, or for correction and intercompany postings.
- FBL1NFBL1N displays vendor line items - open, cleared, or all - for one or more vendors in a company code. It reads from the open and cleared item tables (or their equivalent views on the universal journal in S/4HANA) and is the standard first stop for checking why an invoice is unpaid, confirming a vendor balance, or reconciling against the GL.
- FBL3NFBL3N is used to list open, cleared or all G/L account line items for reconciliation, audit and posting analysis. It is most useful when investigating account balances, clearing status, posting references or line-item details for a G/L account. For reliable support work, start with the exact system, client, user and business context, then use the transaction's own status, document or log evidence before changing configuration or data.
- FBL5NFBL5N displays open, cleared, or all line items for one or more customer accounts, read from the customer sub-ledger (or the universal journal on S/4HANA). It is a display-only transaction. The most common source of confusion is the special G/L indicator: down payments and bills of exchange are posted as special G/L transactions and will not appear in the list unless that indicator is explicitly included in the selection.
- F110F110 is the transaction for the automatic payment program, which selects open vendor and customer items due for payment, proposes a payment run, and on execution clears the items and generates payment media or bank transfer files. It runs in two distinct steps, proposal and payment run, and most confusion comes from treating those two steps as one.
- OB52OB52 maintains the posting period variant, the table that decides which fiscal periods are open for posting, broken down by account type and optionally by authorization group. It does not set the fiscal year variant itself. A company code inherits its open/closed periods from whichever posting period variant is assigned to it, and that variant is often shared across several company codes.
- FS00FS00 is the central transaction for creating, changing and displaying General Ledger account master records. It combines two distinct data segments in one screen: the chart of accounts segment, shared across all company codes using that chart, and the company code segment, which is local to one company code. Most posting errors trace back to one segment existing without the other.
- FB03FB03 displays a posted Financial Accounting document with its header, line items, account assignments, clearing information, and navigation to related source documents. Use it to prove what SAP actually posted and to reconcile logistics or subledger activity to FI. In S/4HANA, distinguish the operational document view from Universal Journal reporting.
- FB08FB08 reverses a posted financial accounting document by creating a new offsetting document, not by deleting the original. The original document remains in the system with a reversal flag and a link to the reversal document. It fails if the item is cleared, the period is closed, or the document originated in MM or SD and needs to be reversed at source instead.
- F-28F-28 posts a manually entered incoming customer payment and clears it against open AR items in the same transaction. The header screen captures the bank/cash account and amount; a second screen lists the customer's open items for selection. Most problems trace back to a mismatch between the header amount and the total of items selected on that second screen.
Key Tables8
- ACDOCAACDOCA is the S/4HANA Universal Journal table holding one row per accounting line item per ledger, merging what used to be split across BSEG, the New GL totals tables, CO line items, and material ledger data. It carries FI, CO, and profit-center attributes on the same row, at the grain of ledger, company code, fiscal year, document, and document line.
- BKPFBKPF stores the header of Financial Accounting documents, keyed by company code, document number, and fiscal year. It contains document type, posting and document dates, entry user/time, reference, currency and reversal context, while line-item account assignments and amounts are in BSEG and ACDOCA. In S/4HANA BKPF remains a real document-header table.
- BSEGBSEG stores the operational line-item or entry-view segments of Financial Accounting documents, keyed by company code, document number, fiscal year, and line item. It contains posting key, account type, account, amounts, payment and clearing attributes, and many source-specific fields. In S/4HANA BSEG remains a database table; SAP explicitly states that there is no compatibility view for BSEG.
- SKA1SKA1 holds the chart-of-accounts level of a G/L account master record: one row per chart of accounts and account number, independent of company code. It carries control data like the balance-sheet/P&L classification and account group, but not the description (SKAT) or company-code-specific data such as currency and field status group (SKB1).
- SKB1SKB1 holds the company-code-dependent segment of the general ledger account master, one row per company code and account number. It stores account currency, open item management, posting block, deletion flag, field status group, and sort key. It is joined by chart-of-accounts key to SKA1 for the account itself and to SKAT for the description text.
- T001T001 is the SAP company code master table. One row equals one company code, holding its name, country, city, currency, language, chart of accounts, and fiscal year variant. Every FI posting document, G/L account extension, and reporting selection is scoped by the company code defined here, making T001 the anchor lookup for confirming basic legal-entity setup before chasing a posting or configuration error elsewhere.
- T001BT001B stores Financial Accounting posting-period interval control by posting-period variant, account type, account range, period, and fiscal-year boundaries. The effective posting permission is not simply 'company code open or closed': the company code points to a posting-period variant, and multiple account-type or account-range intervals can allow or block the same posting date differently.
- T030T030 stores the standard G/L account assigned to a chart of accounts for a given automatic-posting transaction key, used by configuration transactions such as OBYC. Each row is a chart of accounts plus transaction key plus the account (or account pair) posted automatically. Keys needing finer differentiation, such as valuation class or house bank, are resolved in satellite tables, not in T030 itself.
S/4HANA Changes2
- Universal Journal ACDOCA replaces the classic totals and index tablesACDOCA is the single line-item table in S/4HANA that now holds FI, CO, AA, ML and profit centre data together at the most granular level. It replaces the separate GL totals tables, CO totals tables, and the various index tables, eliminating reconciliation between modules but requiring every custom program that read those old tables directly to be rewritten or redirected through compatibility views.
- Business Partner as the single master for customers and vendorsIn S/4HANA, customer and vendor master data no longer exists as an independent object. Every customer and every vendor must have an underlying Business Partner record, linked through Customer Vendor Integration, and that BP record becomes the only place general data can be maintained. This is enforced at conversion, not a design choice a project can defer.
Common Issues5
- F5201 — Posting period is not openMessage F5201 means the document posting date resolves to a fiscal period that is not open for the relevant posting-period variant/account type. The system rejects a document because the posting date falls in a period that is not open for the relevant account type in that company code's period variant. The fix is either to correct the posting date to a period that is genuinely open, or to have the closing team extend the period interval in configuration if the period should legitimately still accept postings.
- Automatic payment run not picking up an open itemAn open item is usually missing from the payment proposal because it carries a payment block (manual or automatic), the item is not yet due under its baseline date and payment terms, the payment method on the item or vendor master does not match the run parameters, or the item's currency or amount falls outside the limits set for the house bank and payment method combination.
- Document splitting error at postingA document splitting error at posting means the general ledger cannot force the document to balance by profit center, segment, or another active splitting characteristic, usually because the GL account or document type involved has never been classified in the document splitting configuration, or a required characteristic is blank on one line and cannot be derived from any other line in the document.
- Open item cannot be cleared due to a tolerance differenceThe clearing transaction (F-28, F-32, F-44, F-13) rejects the difference between invoice and payment because it exceeds either the amount limit, the percentage limit, or both, set in the tolerance group assigned to the customer, vendor, GL account, or posting user. The fix depends on whether the tolerance setting is genuinely too tight or whether the underlying amount is simply wrong.
- Profit centre not populated on the document lineThe profit centre field is blank because nothing in the posting chain derived one: the cost object on the line (cost center, order, WBS) has no profit centre assigned, the GL account has no default profit centre and is not a cost element, or the document splitting/substitution rule that should propagate a profit centre to that line is not configured to cover it. It is a derivation gap, not a display bug.