Skip to Content
Technical Articles

Practical Tips For Implementing SAP S/4HANA Finance 1610

SAP S/4HANA Finance 1610 brings about a change for how users of SAP use currencies in their records. This new system offers two main currencies with eight freely definable other currencies which can be used on their own or in combination with the two main ones. Any ledgers that support the ten currency system will allow for the use of any of these currencies. The older ledgers like those implemented for SAP ERP Central Component (SAP ECC) are built on a three-currency model that is incompatible with the ten currencies that S/4HANA Finance 1610 offers.

Adjustment Postings for Currencies

Older transaction codes (like FBB1) use the old three-currency system. When the main currency of the system changes, the company may need to implement a real-time adjustment of the currencies they have previously defined. An application named SAP Fiori Post Currency Adjustments exists to help users of S/4HANA Finance 1610 deal with these adjustments. Because this is a post adjustment, the user can enter the currency in any of the fields that need adjusting. Even so, the system still follows the standard for all accounting, namely that the total of the debits must equate to the sum of the credits. During posting, standard variants are selectable, and the user needs to choose which of the options apply to correctly populate the field status and ensure that the data enters the database correctly. The app allows for the posting of currency adjustments independent of exchange rates. There may be an issue with values during a period ending, since the exchange rate may be skewed due to the modification.

ACDOCA and Parking

S/4HANA Finance 1610 uses a single-source-of-truth table making it faster for searches and keeping all records in a centralized area. Downstream tables that don’t derive their values from ACDOCA instead use BSEG as their data source and are limited to three currencies because of this. The standard BAPI system (BAPI_ACC_DOCUMENT_POST and BAPI_ACC_DOCUMENT_CHECK) can be used to adjust the postings even though there is a currency limitation. Real-time adjustment of currencies require approval, and because of that, it’s impossible to park as well as post currency adjustments.

Foreign Exchange Valuation

Two new functions added to SAP S/4HANA Finance 1610 are the inception posting and simulation ledger. The simulation ledger can be used to text different exchange rates or currency types and don’t create a binding entry. Inception posting creates the starting values for FX valuation that can then be used in subsequent calculations if you’re running commercial roadside assistance. The valuation area can be created using a freely definable currency. The default setting for these posting is U, meaning that only reports accessing ADOCA can use it, and those accessing BSEG can’t. Any entry views, therefore, that solely use BSEG won’t be able to use these currencies.

The Universal Table of Truth – ACDOCA

Initially, SAP could have multiple tables dealing with different aspects and data could be pulled from a number of those tables, joined, and then a report generated from the relevant data. SAP S/4HANA Finance 1610 changes this by introducing ACDOCA, a single table where all records are based. ACDOCA deals with keeping information regarding currencies at a ledger-specific point. It should be noted that not every iteration of the traditional GUI or even SAP Fiori apps support the use of all fields of the ACDOCA table. Appropriate fields can be defined in the OData model or within the database query.

Reporting with SAP S/4 HANA Finance 1610

Depending on how reports are generated the user-defined currencies may be available for presentation on the report. An SAP Fiori app may decide to offer the data as a modified transaction that fetches the data it needs and creates a format for presenting the report. Alternatively, the app may use a back-end OData model that uses the fields as defined within the model to populate fields which can then be presented as a report. This data model can easily be edited to include support for the user-defined currencies, thereby allowing them to be included in a statement.

Developing Financial Statements

The standard financial statements that SAP can generate using F.01 don’t give the option for including user-defined currencies. However, an SAP Fiori app titled Financial Statements does allow for these currencies to be presented. Despite that, the SAP Fiori app does have a few drawbacks, including a lack of an evaluations tab (which is included in any report generated with the transaction code F.01) as well an inability to export or download data, making it impossible for finance departments to use it for analysis.


Be the first to leave a comment
You must be Logged on to comment or reply to a post.