SAP S/4HANA FICO Financial - General Ledger

In this lesson, we introduced the Controlling Area and Company Code in the SAP S/4HANA FICO finance module. Their relationship is akin to that of a family and its individual members. The Controlling Area imposes certain minimum requirements on its “family members,” specifically that they share the same Chart of Accounts (COA) and Fiscal Year Variant.

We then covered how the Parallel Ledger works, and finally, we looked at the structure of General Ledger (G/L) account master data and two important configurations: Reconciliation Accounts and Open Item Management.

In this lesson, we primarily introduced Transaction Code FS00 and the Fiori app “Manage G/L Account Master Data” in the SAP S/4HANA FICO finance module, which are used to create, modify, and display General Ledger account master data. We hope you will become proficient in operating this key master data in the finance module.

In this lesson, we introduced the purposes of Posting Keys and Document Types in the SAP S/4HANA FICO finance module, as well as their general naming conventions. This should help you more quickly identify various financial documents in practice. We also covered the background configuration for Document Types—keep in mind that if you encounter related error messages in the future, a good number of them may stem from how Document Types are configured.

In this lesson, we introduced how to enter a simple general ledger document in the SAP S/4HANA FICO finance module using the Fiori app Post General Journal Entries and its corresponding GUI transaction code FB50. In both tools, the input screen is divided into two parts: the upper section for header data and the lower section for line items. When you run a Simulation, SAP performs multiple validations and checks and shows you the entire document, helping you decide whether it can be posted.

In this lesson, we covered a Fiori app in the SAP S/4HANA FICO finance module called Create G/L Account Posting, which can handle nearly all types of General Ledger postings. Its corresponding GUI transaction code is F-02. Both are very similar in that, on the final screen of the first page, you enter the posting key and account, then press Enter to move to the next screen where you input amounts and other relevant fields. We also introduced a handy trick called “Post with Reference,” which you can use when creating very similar journal entries.

In this lesson, we discussed the concepts of clearing and reset clearing in the SAP S/4HANA FICO finance module, as well as their general operations. Clearing can happen at the same time as posting an accounting document or be performed separately (we’ll cover the separate approach later in the financial period-end closing lessons).

It’s important to remember that clearing and resetting clearing by themselves have no direct accounting impact—only the debit/credit line items in a posting affect the accounting. Also note that if a document contains a clearing action, you must cancel that clearing first before you can reverse the document.

Finally, we introduced the topic of document modification. SAP does not allow changes to critical fields in an accounting document—only a few text annotations can be modified, and any such changes are recorded in the system’s history.

In this lesson, we introduced the Fiori app for batch uploading journal entries in the SAP S/4HANA FICO finance module. We then discussed two special types of documents: recurring entries and accrual postings. For accrual postings, besides using SAP’s standard Accrual/Reversal functionality, you can also upload a specific document type in batches and then perform a mass reversal. However, mass reversal is an irreversible, high-impact function, so we recommend automating as much of the process as possible to minimize manual intervention.

In this lesson, we started with simple scenarios and scaled up to more complex ones, covering how to search for financial documents in the SAP S/4HANA FICO finance module. We looked at displaying a single financial document, displaying documents in batches, and querying G/L account balances and their corresponding line items. After studying this lesson, you should be well-equipped to handle financial document inquiries with ease.

In this lesson, we first introduced the concept of Functional Areas in the SAP S/4HANA FICO finance module, which are primarily used to reduce redundant account setups across different departments. We then went into detail on how to configure and modify the structure of the Financial Statement Version (FSV). Finally, we demonstrated how to use two standard Fiori apps for generating a Trial Balance and Financial Statements.

In this lesson, we covered Profit Centers in the SAP S/4HANA FICO finance module and their higher-level organizational units (Segments). Their purpose is to enable cross-company code accounting and reporting for various business departments independently. To achieve accurate reporting, you must split line items in financial documents according to the relevant Profit Center (or Segment). We also gave a brief overview of document splitting logic and introduced the Profit Center Reports.

In this lesson, we discussed the overall process for month-end closing in the SAP S/4HANA FICO finance module. We also went into detail about clearing open items during the review phase, handling foreign currency revaluation in the adjustment phase, and opening/closing the financial posting periods in the final closing phase. We have now covered the most complex steps of the General Ledger month-end closing procedure; you should be able to apply these concepts to related scenarios. If you have any questions, feel free to ask anytime during the course.

In this lesson, we first covered year-end closing procedures in the SAP S/4HANA FICO finance module. We then discussed how to run month-end closing tasks in the background. Finally, we introduced the month-end task list tools in S/4HANA: the Financial Closing Cockpit (FCC) for the on-premise (Enterprise) edition, and Advanced Financial Closing (AFC) for the Cloud edition.