SAP FI is designed to capture all business transactions for an organization and generate legally required financial statements. It provides a real-time view of a company’s financial position in the market.

1.1. Core Purpose and Submodules

The SAP FI module is used to store and manage an organization’s financial data. It enables the management of financial accounting within an international framework, accommodating multiple companies, currencies, and languages. It integrates directly with other SAP modules such as Sales and Distribution (SD), Materials Management (MM), and Production Planning (PP).

The primary sub-components of SAP FI include:

• Finance Accounting General Ledger (G/L): The central record for maintaining all accounting details.
• Finance Accounting Accounts Receivable and Payable (AR/AP): Manages all customer and vendor transactions.
• Finance Accounting Asset Accounting (AA): Manages all fixed assets of the company.
• Finance Accounting Bank Accounting: Manages all transactions conducted through banks.
• Finance Accounting Travel Management: Manages all travel expenses.
• Finance Accounting Fund Management: Manages company funds, including budgeting and forecasting.
• Finance Accounting Legal Consolidation: Consolidates financial statements for multiple units into a single entity (now largely handled by SAP BPC and SEM-BCS).

1.2. Organizational Structure and Foundational Concepts

A proper organizational structure is the backbone of SAP FI. Key elements must be defined during implementation.

1.3. General Ledger (G/L) Accounting

The General Ledger is the core of Financial Accounting, containing all transaction details and serving as the primary record for all accounting.

Key G/L Concepts and Configuration

• Chart of Accounts (COA): A list of all G/L accounts used by one or more company codes. Types include:
  • Operating COA: Contains G/L accounts for daily operational needs. Assigned to a company code.
  • Country COA: Contains G/L accounts required to meet a country’s legal reporting requirements.
  • Group COA: Contains G/L accounts used by the entire corporate group for consolidated reporting.
• Account Group: Groups together G/L accounts with similar business functions (e.g., administrative expenses, revenue accounts). It controls the number range and the field status for the G/L master records.
• Retained Earnings Account: Used to carry forward the balance of Profit & Loss (P&L) accounts from one fiscal year to the next.
• Fiscal Year Variant: Defines the posting periods within a fiscal year (up to 12 regular and 4 special periods). It must be assigned to each company code.
• Posting Period Variant: Controls which accounting periods are open for posting. It can be assigned to multiple company codes.
• Field Status Variant & Group: The Field Status Variant contains multiple Field Status Groups. The group is assigned to a G/L account and determines which fields are required, optional, suppressed (hidden), or display-only during transaction entry.
• Posting Keys: A two-digit numerical key that determines the account type (e.g., Customer, Vendor, G/L Account) and the type of posting (debit or credit).
• Document Type: A two-digit key that classifies accounting documents, distinguishes business transactions, and determines the document number range.

Core G/L Processes

• G/L Account Master Data: A master record must be created for each G/L account. This can be done centrally using T-code FS00. G/L accounts can be blocked for posting or creation and flagged for deletion.
• Journal Entry Posting: The process of recording financial transactions in the G/L. This can be done through T-code FB50, where debit and credit line items are entered for specific G/L accounts.
• Document Management: Documents can be temporarily saved using the Hold function if information is incomplete. The Park function allows a user without sufficient authorization to save a document for later review and posting by an authorized individual.
• G/L Reporting: SAP FI provides various standard reports for G/L analysis, including:
  • Chart of Accounts List (S_ALR_87012326)
  • G/L Account Balances (S_ALR_87012277)
  • G/L Account List (S_ALR_87012328)

1.4. Accounts Receivable (AR)

The AR submodule manages all accounting data for customers and is an integral part of sales management. All postings in AR are recorded directly in the General Ledger.

Customer Management and Transactions

• Customer Master Data: Contains all information about a customer required for business transactions, controlling how transactions are recorded and processed. Master records are created centrally (FD01) and are used by both accounting and sales departments. They can be blocked for posting or marked for deletion.
• Customer Account Group: Classifies customers (e.g., Domestic, Export, One-Time). The account group determines the screen layout and number range for the customer master record. One-time customer master records are used for customers with infrequent transactions.
• Sales Invoice Processing: Invoices are posted (FB70) to create an open item for a customer.
• Incoming Payments: When a customer pays an invoice, the incoming payment is posted (F-28), clearing the open item. Partial payments can also be posted, which create a new open item for the payment amount while leaving the original invoice open.
• Document Reversal: Incorrect documents can be reversed (FB08), provided they contain no cleared items and were posted within FI.
• Sales Returns: Handled via a credit memo posting (FB75) to credit the customer account for returned goods.
• Dunning: A systematic process for reminding customers of overdue payments by generating and sending dunning letters.
• Credit Management: The Credit Control Area is used to monitor and manage customer credit limits (FD32).

1.5. Accounts Payable (AP)

The AP submodule manages and records accounting data for all vendors, handling invoices, deliveries, and payments.

Vendor Management and Transactions

• Vendor Master Data: Similar to customer master data, vendor master records contain all necessary vendor information and are created centrally (XK01). They are used by both accounting and purchasing departments.
• Vendor Account Group: Classifies vendors and controls the screen layout and number range. One-time vendor master records can be created for vendors with whom transactions are infrequent.
• Purchase Invoice Processing: Vendor invoices are posted (FB60), creating an open payable item. Withholding tax can be calculated and applied during this process.
• Outgoing Payments: Payments to vendors are posted (F-53). The Automatic Payment Program (APP) (FBZP) can be configured to automatically process payments for due/overdue vendor invoices for multiple company codes.
• Purchase Returns: Handled by posting a vendor credit memo (FB65).
• Resetting Cleared Items: If a payment is made against an incorrect invoice, the clearing document can be reset (FBRA), which re-opens the original items.

1.6. Asset Accounting (AA)

The FI-AA component manages an organization’s fixed assets, serving as a subsidiary ledger to the G/L.

• Integration: AA is highly integrated with other modules. Asset purchases can be posted directly from Materials Management (MM), and maintenance activities from Plant Maintenance (PM) can be capitalized to assets. Depreciation is passed directly to FI and Controlling (CO).
• Asset Lifecycle: AA covers the entire asset lifecycle, from initial acquisition to retirement. It automatically calculates values for depreciation, interest, and insurance.
• Asset Explorer (AW01N): A key tool that shows all values for a fixed asset, including planned and posted values for acquisition and production costs (APC) and depreciation across different depreciation areas.
• Asset Classes: Assets are categorized into classes (e.g., Buildings, Vehicles, Machinery) using T-code OAOA. The asset class determines the number range, screen layout, and default depreciation parameters for assets created within it.