Universal Journal Entry
The new universal journal entry replaces the Financial Accounting (FI) document and the Controlling (CO) document with a universal document. A journal entry is created for every business transaction in one of the following application components:
General Ledger Accounting
(FI-GL)
Asset Accounting
(FI-AA)
Controlling
(CO)
Exception: Costing-based Profitability Analysis (CO-PA)
Material Ledger
(CO-PC-ACT)
The introduction of the journal entry eliminates the need for the separation made previously between Financial Accounting (FI) and Controlling (CO) (single source of truth). Since financial accounting and managerial accounting are reconciled constantly, there is no longer any need for reconciliation between FI and CO or between FI-GL and FI-AA, nor is there any need for the real-time integration of these components. The reports in all components use data from the same journal entries.
Technical Name of Product Feature |
|
|---|---|
Product Feature Is | New |
Country Dependency | Valid for all countries |
Software Component Version | SAP_FIN 720 |
Application Component |
|
Available As Of | SAP Simple Finance add-on 2.0 for SAP Business Suite powered by SAP HANA |
For this uniformity, all cost elements (primary and secondary) need to be portrayed as G/L accounts. Consequently, you no longer need to enter the master data for cost elements separately; instead, you only need to create G/L accounts from now on.
The journal entry contains data for characteristics from all of these components. In the case of data that is not entered during document entry or that is not determined by the business transaction, the system derives such data automatically from existing data. In this way, you can analyze the data using characteristics from different components. For example, you can create a balance sheet at the segment level.
Account-based profitability analysis is fully integrated: For account-based profitability analysis, the CO-PA characteristics are incorporated directly in the journal entry. The system derives the characteristics for all financial statement items on the basis of transactions.
The universal journal entry has its own currency fields. This brings the currency concepts used in FI and CO closer together.
Each journal entry contains the ledgers to which the business transaction was posted. By means of the ledgers, parallel accounting is supported in those application components in which it can already be used.
It is possible to enhance the journal entry by extending the coding block and adding CO-PA characteristics.
Universal journal entries are written to a new table, ACDOCA. Consequently, updates are no longer made to some old tables. Nevertheless, you can continue to use reports that use data from these old tables. This is because compatibility views for a data request from one of these tables read the data from ACDOCA.
Perform the migration to SAP Accounting powered by SAP HANA.
You need to observe the information in SAP Note 2131643
if you are using the following Web Dynpro applications:
Financial Statement: Actual/Actual Comparison
(FCOM_FIS_FS_OVP
)
Line Item Browser (G/L View)
(FIS_FPM_GRID_LITB_GL
)
Account Balance
(FIS_FPM_GRID_GLACC_BAL
)
In the SAP Easy Access
menu under , the following entries have been removed:
Path | Transaction or menu nodes |
|---|---|
|
|
|
|
The structure node SAP Smart Financials Migration
has been replaced with the SAP Simple Finance Add-On for SAP Business Suite powered by SAP HANA
structure node.
The most important other changes include:
New ledger master data with settings for currencies, fiscal year variant, period lock and so on, together with a new assignment of the accounting principles to the ledger and company code.
There are no longer scenarios for General Ledger Accounting. This is because all characteristics are posted in the line items of the journal entry.
Real-time integration no longer applies. Instead, CO transactions are posted directly as a universal journal entry. As secondary cost elements are also contained in the chart of accounts, account assignment to a different account is no longer necessary.
There are new settings for determining the document type and document number for postings from CO as well as for assigning the actual version of CO to the ledger.
The local general ledger document number (DOCNR
) in non-leading ledgers and their determination is now no longer required. The document number of the leading ledger is now always used.
The universal journal entry requires new levels of consistency between the Customizing settings for FI and CO. For example, the fiscal year variants need to be identical.
The following details the Customizing activities or structure nodes that have been removed from the SAP Implementation Guide (IMG) because they are no longer relevant, those that have been changed, or those that have been added.
Path | Structure Node or Activity | Removed or New |
|---|---|---|
|
| Removed |
|
| Removed |
|
| Removed |
| Removed | |
| Removed | |
| New | |
| New | |
| Removed | |
|
| Removed |
| New | |
|
| Removed |
|
| Removed |
Path | Structure Node or Activity | Removed or Changed |
|---|---|---|
|
| Removed |
|
| Transaction GCA6 has been replaced by transaction GLGCA6. |
| Transaction GCA1 has been replaced by transaction GLGCA1. | |
|
| Removed |
The following Customizing activity has been removed:
For information, see FI-AA (New): Effects on Existing Data, section .
The following structure node and Customizing activities have been removed:
Path | Structure Node or Activity |
|---|---|
|
|
| |
| |
| |
| |
|
The following Customizing activities have been removed:
Path | Activity |
|---|---|
|
|
|
The following structure nodes and Customizing activities have been removed:
Path | Structure Node or Activity |
|---|---|
|
|
|
|
|
|
|
|
Detailed release notes: