archive

This second article in a series of five on the Intelligent Enterprise shows how apps and extensions to SAP Cloud Platform can benefit vendors building solutions and products to help companies optimize their service to customers.

This content is available to SAPinsider Members(complimentary).
Please click below to log in or create an account

Login Now »

Create Acount »



Goodyear Keeps the Wheels Rolling with SAP Solution Manager

Supporting Operations and Digital Transformation with Version 7.2 Upgrade

For the past 120 years, The Goodyear Tire & Rubber Company has been at the forefront of a continuously changing mobility industry. It has achieved this by leading with innovation in its products and services for customers, as well as in its internal systems and processes. Following this commitment, the company recently updated its system landscapes by expanding its SAP footprint. SAP system monitoring and change management processes have become progressively important to Goodyear – resulting in an increasing trend in working with SAP Solution Manager. With a goal of implementing better, easier, and faster software tools and processes – and answering SAP system users’ call for improved system performance and usability – the business decided to upgrade to SAP Solution Manager 7.2. Learn how the upgrade provided Goodyear benefits such as improved efficiency and resource allocation, enhanced visual representation, and a less restrictive content documentation structure.

This content is available to SAPinsider Premium Members.
Please click below to log in or create an account

Login Now »

Create Acount»



Managing Currencies in a Live SAP S/4HANA Finance 1809 Environment

Traditionally, once you have gone live in a production system, the SAP system gives you a warning message (Figure 1) when you try to add a currency in the ledgers definition, and you then need SAP System Landscape Optimization (SLO) service for such a change in your currency setup.

Figure 1 Issue when adding new currency in the SAP Business Suite

In an SAP S/4HANA environment, SAP provides a program named FINS_ACDOC_UTIL_SET_CURR_KEYS for updating the existing transaction data for new currencies. This program has restrictions as shown in Figure 2.

Figure 2Restrictions when adding currencies in an SAP S/4HANA environment

In a greenfield SAP S/4HANA implementation, it is quite common that not all 10 currencies would have been set up at the start of an SAP S/4HANA system. In a conversion scenario of an SAP S/4HANA implementation, currencies are migrated as they are, and no new currency introduction happens along with conversion. There can be many scenarios that require the new currency introduction, such as

  • Introducing a group currency to unify the group reporting
  • Introducing a sub-group currency to have regional reporting
  • Introducing hard currency for countries with inflation

SAP S/4HANA Finance 1809 provides an integrated framework to add currencies into your company code in a ledger along with managing the journal entries already existing in your production system. Thus, the newly introduced currencies are available in the ACDOCA table only and can be used in both accounting-specific processes and reporting.

In this blog, I explain the activities for managing currencies at a high level as shown in Figure 3.

Figure 3Overview of project activities for currency introduction

In my example scenario, I am adding a currency type Z0 with fixed EUR currency. From here on you will see the setup details and execution flow to add currency.

The Preparatory Phase

This section details the various elements to consider, as well as configuration and setup steps needed to add the new currency.

Define Settings for Currency Types

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Define Settings for Currency Types. This path displays the screen in Figure 4.

Figure 4Create a new currency type (if a standard currency type is not suitable)

If you are going to use a predefined currency type, then this setting is not required; otherwise, you can create a custom currency type. For my example you create a custom currency type of Z0. In Figure 4 select the Currency Types folder in the menu on the left and create a new entry. Enter Z0 in the field under Currency Type and populate the Description and Short Description fields as shown. In the Settings Def. Level (settings definition level) column, select 1 Global from the drop-down list of options.

You also define the EUR as fixed currency for this new currency type Z0. To complete this step, select the Global Currency Conversion Settings folder and create a new entry by populating the fields in the columns under Global Currency Conversion Settings as shown in Figure 5. Here I have defined the conversion to happen from company code currency to this new currency type.

Figure 5Define conversion settings for the custom currency type

Then in the Company Code Settings subfolder under the Ledger folder, you can map the currency type in the freely definable currency field and save the changes (Figure 6).

Figure 6Add a currency type to the company code and ledger

Create a Project for Managing Currencies

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Create Project for Managing Currencies. After you click the New Entries button in the initial screen (not shown), the system displays the screen in Figure 7.

Figure 7 Create a new project for adding currency

In this screen you create a currency introduction project by entering details for the new project. In the field under the Project ID column, enter an alphanumeric identification key for the implementation project that can be a maximum of 10 characters long. For my example, enter ZNEWCUR01. Enter a description in the field under the Description column (e.g., Subsequent Introduction of Currency) and press Enter.

Now double-click the Assign Ledger, Company Code to Project ID folder in the left side of Figure 7 to go to Figure 8. In Figure 8 enter data for the target ledger, company code, target currency type, source for the conversion, exchange rate, and transaction date type. Click the save icon to save your data.

Figure 8 Assign the ledger, company code, and other values to the currency introduction settings

Determine Accounts for Rounding Differences

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Determine Accounts for Rounding Differences.

In this setting as shown in Figure 9, you can create new entries to map the general ledger (G/L) accounts for managing rounding differences while converting the source currency type amount to a target currency type amount. The G/L account can be differentiated to handle balances versus journal entry documents. This G/L account needs to be type N (i.e., Nonoperating Expense or Income).

Figure 9Define G/L account settings for rounding differences

Define Account Assignment to Reconcile Aggregated Values

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Define Account Assignment to Reconcile Aggregated Values. This path takes you to the screen in Figure 10.

Figure 10Create a project for adding currency in the system

Here you need to select the Project ID and Project Type folder and then click the Select Fields for Reconciliation of Sums subfolder in the menu as shown in Figure 10.

In Figure 11, you select the fields on which the sums are calculated during reconciliation after the migration is over for values from the source currency moved over to the target currency.

Figure 11 Define reconciliation settings

Make Settings for Notifications

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Make Settings for Notifications.

Notification settings can be customized for activity progress during the execution phase of the implementation of this project. This setting takes you to Figure 12 in which you need to specify various activities, notification settings, and the email address to be notified. Click the save icon.

Figure 12Specify notification settings

Define the Number of Jobs

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Define Number of Jobs. This path takes you to the screen in Figure 13.

Figure 13 Specify the number of jobs for subsequent introduction of currency

Based on the system capacity and system load, you can specify the number of jobs that this project uses to transfer the data from the source currency type to the target currency type field. If no batch job is specified, the SAP system takes the maximum possible number in the system minus three jobs. In Figure 13 you can specify the number of jobs for various activities in the execution phase. Click the save icon to save your data.

Prepare the Follow-On System and Transport Customizing

All the previously mentioned settings are done in a development environment and then transported to a follow-on system (unit testing system, quality system, and finally to a production system) via transport.

Go to the notes for customizing activity in menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Prepare Follow-On System and Transport Configuration.

It contains a reference list for the various activities to be done in the follow-on system before the downtime starts for the actual execution phase for additional currency introduction (e.g., closing the previous fiscal year in various applications). Once all such prerequisite settings are done in the follow-on system and the customizations are transported, you then execute the steps listed for downtime in the note in the reference list of the same customization (e.g., locking all users for postings, opening posting periods for the current fiscal year, and so on).

Complete Preparations

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Complete Preparations. This path takes you to the screen in Figure 14.

Figure 14 Initiate the completion of the preparatory phase

Once all the settings described in the “The Preparatory Phase section are done, you can mark the preparation phase as completed in the system in which you want to execute the project. Without marking this step, you can’t start the execution activities. In Figure 14 you need to enter the project ID and then click the Complete button.

The SAP system once again shows a warning message (Figure 15) to confirm that you completed all the activities in the preparation phase. You need to click the Confirm button to complete the preparations.

Figure 15 Warning message for verifying the preparatory phase activities

After you click the Confirm button, the SAP system displays the information message shown in Figure 16 (provided there is no error in the setup).

Figure 16Information message for the preparation phase completion confirmation

This activity of confirming preparation phase completion starts your system downtime and thus no further posting can be done until the execution phase mentioned later in this blog is complete. This setting must be done in each system separately as it is not transported.

The Execution Phase

This phase is executed in a follow-on system (e.g., a unit testing system or a quality system and finally the production system). Once all the configuration setup is transported, follow-on activities are performed and downtime is started.

Cockpit: Manage Currencies

To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Cockpit: Manage Currencies.

This path takes you to Figure 17. In the Project field, enter the project ID and then click the Show Cockpit button.

Figure 17 Initiate the cockpit for mass data processing

The next screen (Figure 18) displays various activities of the project execution. Click the Execute button.

Figure 18 Execute the cockpit

The SAP system then displays a confirmation message shown in Figure 19. Click the Yes button to start the execution.

Figure 19 Confirm the execution of the cockpit

After confirming the execution, the SAP system displays a status message indicating that the background jobs have been triggered for various activities in the cockpit (Figure 20).

Figure 20 The status message for the cockpit’s jobs scheduling

Once all the background jobs are finished successfully, the cockpit shows a green status for various activities shown in Figure 21.

Figure 21 Cockpit execution without any error messages

The details of these activities are listed in Table 1.

Table 1 Details of currency introduction project activities

Here the SAP system ensures the following updates automatically:

•           All historical transaction data is enriched by the new introduced currencies

•           Reconciliation and adjustment only for transactional data of the current fiscal year — generation of rounding differences

•           Introduction of the same currency across multiple ledgers for one company ensures identical values in new currency (if it was identical in source currency)

•           Reconciliation and adjustments happen for all general ledger entities (company code, ledger, account and document splitting characteristics with balance zero flag)

(Note: You are very fortunate if you have such green lights after your first execution. There can be multiple errors or warnings during the execution, and the system displays these messages all at once for all the activities. You need to correct them and then re-execute by clicking the Reset button and then clicking the Execute button.)

Checking the Currency Introduction Results

Here I show you the impact of this new currency introduction at table entry level as displayed in Figures 22 and 23. The same currency settings can be verified in other reports such as FAGLL03 and the SAP Fiori application Manage Journal Entries.

Figure 22Entries in table ACDOCA before currency introduction

Figure 23Entries in table ACDOCA after currency introduction

Complete the Project

After you verify that currency amounts have been converted correctly, you can mark the data transfer as completed. To complete this step, follow menu path SPRO > Financial Accounting > Financial Accounting Global Settings > Tools > Manage Currencies > Preparatory Phase > Complete Project This path takes you to the screen shown in Figure 24 in which you need to enter the project ID in the Project field and then click the Complete button.

Figure 24 Initiate the confirmation of currency conversion completion

The system displays a pop-up screen (Figure 25) to confirm that the project is complete. Click the Confirm button.

Figure 25Message to confirm the completion of project

The system then shows you a confirmation message that the status is changed (Figure 26).

Figure 26 Project marked as completed

Note that there are still certain restrictions in this manage currencies framework:

  • Company code and controlling area currency cannot be introduced by this framework, as those are foundation-level elements in the company code definition and they should be tackled during company code setup.
  • Conversion of the existing currency type — that is, changing the definition of an already included currency type as two settings for the same currency type bring inconsistencies
  • Introduction of currency types for transfer prices, as this needs a special currency handling for various valuation views in transfer pricing
  • New currencies are not reconciled with Asset Management, the material ledger, and Controlling, as these are mainly in Financial Accounting itself. This might change in the future when SAP streamlines the 10 currencies set up in all applications.

In a nutshell, this convenience of adding a new currency in a live environment will open up the options for leveraging the freely definable currencies innovation in SAP S/4HANA.




Sanofi Performs a Self-Diagnosis

Global Pharmaceutical Company Remedies Its Financial Processes with Automation

Sanofi, a major multinational pharmaceutical company, has plans for expansion. To facilitate that growth, Sanofi decided it needed to automate its financial close, account reconciliation, and journal entry processes as many of them were manual and disparate across its business units. Discover how even partway through a global implementation of a record-to-report solution to transform its financial processes, Sanofi has already seen greater efficiency and time savings, allowing the staff to concentrate on value-added activities for its life-saving health care operations and medical research and development.

This content is available to SAPinsider Premium Members.
Please click below to log in or create an account

Login Now »

Create Acount»



The Intelligent Enterprise and the Digital Supply Chain of One

This third article in a series of five on the Intelligent Enterprise shows how apps and extensions to SAP Cloud Platform can benefit vendors building solutions and products to help their customers optimize their manufacturing and supply chain operations.

This content is available to SAPinsider Members(complimentary).
Please click below to log in or create an account

Login Now »

Create Acount »



SCM Collection 2018: Part 1

Part 1 of a 2-part series to help you balance supply chain management processes while focusing on fulfilling your customers' demand

Tap into strategic and technical content on topics such as accelerating inventory sorting, forecast planning of transportation resources, and leveraging SAP Product Lifecycle Management for discrete manufacturing.

This content is available to SAPinsider Members(complimentary).
Please click below to log in or create an account

Login Now »

Create Acount »



SCM Collection 2018: Part 2

Part 2 of a 2-part series to help you balance supply chain management processes while focusing on fulfilling your customers' demand

Explore content on building business value with SAP Extended Warehouse Management, as well as articles on SAP Leonardo and SAP HANA, SAP S/4HANA, and SAP Cloud Platform.

This content is available to SAPinsider Members(complimentary).
Please click below to log in or create an account

Login Now »

Create Acount »



The Intelligent Enterprise and the Workforce of the Future

The journey to the Intelligent Enterprise rests upon support and buy-in from an organization’s employees, who hold the key to the creative efforts required for digital transformation. SAP SuccessFactors provides the analytics and processes that work together to transform the workforce. This article, the fourth in a five-part series on the Intelligent Enterprise, highlights four SAP partners who have extended the SAP SuccessFactors to elevate training, improve communication, encourage employee motivation, and provide easy access to the information they need to perform their jobs – all in the interests of an improved customer experience.

This content is available to SAPinsider Members(complimentary).
Please click below to log in or create an account

Login Now »

Create Acount »



SAP S/4HANA Finance 1610: Practical Tips for an Implementation

by Sridevi Pattabiraman, Senior Manager-S/4 HANA Finance, Cognizant Technology Solutions, USA

SAP S/4HANA Finance 1610 provides users with the flexibility of using two main currencies plus eight freely definable currencies. The translation of the user-defined currencies, whether real time or not, is based on the currency configuration completed after executing transaction code FINSC_LEDGER. The eight freely definable currencies allowed by SAP S/4HANA Finance 1610 are available in all ledgers (leading, non-leading, and extension), but they are not available in the material ledger or Asset Accounting (FI-AA). These currency types still follow the traditional three-currency (document, local, and group) setup as in SAP ERP Central Component (SAP ECC).

 I now describe the impact on currency from these five processes:

  • Currency adjustment postings
  • Business application programming interface (BAPI) functions
  • Parking
  • Foreign exchange (FX) valuation
  • Reporting
Currency Adjustment Postings

The traditional transaction codes such as FBB1 still support only three currencies (with eight currencies available in SAP S/4HANA Finance 1610, posting adjustments for three currencies is outdated), whereas transaction codes such as ABF1 are no longer valid. With multiple currencies, there is a real-time need for currency adjustment in each of the eight currencies especially during migration. The currency adjustment is needed if the functional currency of the entity is changed (because of the Financial Accounting Standard Board Accounting Standard Codification (ASC)’s definition of functional currency not necessarily the need to be the legal currency of the country, but the primary currency with which the entity transacts). Regarding the ASC definition of functional currency, few currency adjustment postings are necessary to support a period-end closing. For this process, SAP S/4HANA Finance 1610 provides users with an app called Post Currency Adjustments (app ID F1606).

(Note: For currency adjustment postings in SAP S/4HANA Finance 1610, only the SAP Fiori Post Currency Adjustments app is available, and there is no transaction code available for such adjustment postings.)

Here are the key features of this app:

As the name suggests, the purpose of the app is to post currency adjustments that is, posting without involving any exchange rates. The user can enter (manipulate) the value in each currency.

  • The app allows the user to select the ledger group during posting.
  • Although manipulated, the core of accounting is still valid (that is, the total of the debit should be equal to the total of the credit). Therefore, SAP provides a feature so that users can decide for which currency the debit/credit total check should be performed.
  • The Debits/Credits Cur. (debits/credits currency) field provides users with an option of standard and user-defined currencies (Figure 1). The chosen currency then becomes the main currency, and all other currencies appear in the Details section of the line item.

Figure 1 – Options available in the Debits/Credits Cur field in the SAP Fiori Post Currency Adjustments app

Consider this example. In the Transaction Currency field in Figure 1, enter CHF (Swiss francs). The settings for the Debit (Company Code Currency) and Credit Company Code Currency fields are USD.

Enter $100 in the Debit Company Code Currency field and $50 in the freely definable currency Amount field as shown in Figure 2. The rest of the currency values are left as $0, as this is an adjustment posting.

Figure 2 – Line item entries in the SAP Fiori Post Currency Adjustments app

Figure 3 shows an example of a document posted using the SAP Fiori Post Currency Adjustments app.

Figure 3 – A document posted using the SAP Fiori Post Currency Adjustments app

The Journal entry attribute is set as U (Posting in General Ledger only). (This value is not shown in any of the figures. The SAP S/4HANA Finance 1610 system sets the document status internally in the header. Technically, this means that document details are available only in table ACDOCA, and they are not stored in table BSEG.

There are standard variants available during posting. Depending on the general ledger (G/L) involved, the user needs to select the appropriate variant for posting so that the field status is enabled and necessary data is captured correctly.

Here are some points to be aware of during implementation of this app:

  • The main aim of the app is to post currency adjustments without referencing exchange rates. This means that it becomes necessary for the system to store a currency setting’s value independently in the respective currency fields of table ACDOCA. This step is possible only when ledger-specific postings are created. Therefore, there is no real difference between the entry view and the G/L view while the user displays the document.
  • When the system creates a ledger-specific posting, it brings in a limitation that open item managed G/Ls cannot be posted or adjusted using this tool. This limitation becomes tricky during migration or a period end, especially when an entity’s functional currency is changed and adjustment postings are necessary.
  • Posting using this tool always has a zero value posted against the document currency. Although the transaction currency is entered, the value cannot be populated. The user needs to be cautious using this tool, as it skews the value during FX valuation during a period end. For example, this transaction might be shown as 0.00 CHF = 100 USD.
BAPI Functions

The proven classic BAPIs BAPI_ACC_DOCUMENT_CHECK and BAPI_ACC_DOCUMENT_POST support freely definable currencies. However, if the ledger-specific postings are handled (using accounting principles), then the limitation of open item managed accounts continues in custom objects as well.

 

Parking

 

The single source of truth table ACDOCA supports all 10 currency settings. However, the downstream tables or functionalities still remain with the traditional table BSEG setup. For instance, the parking tables (VBSEG*) follow the three-currency structure. To overcome the limitation of currency adjust postings, the classic BAPIs BAPI_ACC_DOCUMENT_CHECK and BAPI_ACC_DOCUMENT_POST could be used to solve the issues. However, you cannot park and post currency adjustment entries. Entries such as currency adjustments in real time warrant the need for an approval process, as there is so much deviation from the standard value determined using an exchange rate. However, building workflow in SAP S/4HANA Finance 1610 is not straightforward, as the traditional parking tables do not support multiple currencies.

 

FX Valuation

 

A few additional features, such as simulation ledger and inception posting, are now part of SAP S/4HANA Finance 1610. As the name suggests, the simulation ledger is used to simulate FX valuation based on different exchange rates or currency types combinations, and inception posting is used to post initial values of the FX run in the valuation area which is later used in subsequent FX valuation runs. The valuation area also can be defined using the freely definable currency. The SAP system stores ledger-specific postings with a document status set to U. This is true as well for FX valuation postings a status setting of U denotes that documents are available only in table ACDOCA and not in table BSEG. This means any report using the Entry view does not fetch these documents.

Consider this example. For G/L account 8040003 (Foreign Exchange Losses Unrealized), note the difference in reports using Entry and G/L views. (To execute these reports use transaction code FAGLL03.) The Entry view is based on data in table BSEG and therefore results in zero records (Figure 4); the G/L View is based on table ACDOCA in which all the FX valuation documents are displayed (Figure 5).

Figure 4 – The Entry View output after executing transaction code FAGLL03

Figure 5 – The G/L View output after executing transaction code FAGLL03

 

Reporting

 

A few of the standard reports do not support the freely definable currencies. Only traditional currency types are available in the selection screen and in the report output. One of the reasons could be that such reports are built using table BSEG and not table ACDOCA. However, even the SAP HANA-based transaction codes such as FBL3H do not have different currency options in their layouts (Figure 6).

Figure 6 – The Change Layout section of a G/L account after executing transaction code FBL3H (Note that no currency options are available.)

Availability of freely definable currencies in the reports depends on how the reports are made available. The reports in the SAP Fiori application library can be a standard SAP GUI transaction enriched for an SAP Fiori view or a native SAP Fiori application that has a back-end Open Data Protocol (OData) service provider. The service provider is maintained with a data model and can read only the fields maintained in the data model. The data model cannot be enhanced to bring in the user-defined currencies without modifications (for example, KSB1, MB51, MB52, and MB5L).

SAP Fiori-based reports are really good for analysis. Apps such as Trial Balance support cross-tab reporting and provide users with flexibility to define the columns needed for the rows or columns and to add them by just using the drag-and-drop feature (Figure 7).

Figure 7 – Row and column fields in the SAP Fiori Trial Balance app

Certain SAP Fiori-based reports are very helpful. For instance, instead of using an SAP GUI- based transaction code (FBL3N or FBL3H), apps such as G/L Account Line Items are helpful in bringing in user-defined currencies in the report output (Figure 8).

Figure 8 – Currency type availability in the SAP Fiori G/L Account Line Items app

(Note: Users should carefully choose between the traditional transaction code and the new SAP Fiori apps. Every traditional report is not yet fully converted to an SAP Fiori app with new features.)

 

The Universal Journal Entry Table

 

One of the major changes that SAP made in SAP S/4HANA Finance 1610 is bringing in table ACDOCA the universal journal entry table thereby eliminating the need for a multitude of tables. This is a major step in reducing the database footprint and thereby enabling faster access time. Here are some points to consider regarding the practical use of table ACDOCA:

  • The validation and substitution options in SAP Fiori do not support table ACDOCA. These options are still designed based on the standard BKPF, BSEG, and SYST tables (Figure 9).
  • Account-based CO-PA fields are enhanced in table ACDOCA. Any common fields created earlier using a coding block cannot be added again (for example, CO-PA characteristics created in SAP ECC can be added as a coding block. However, in SAP S/4HANA Finance 1610, if both these characteristics are the same, they cannot be added to table ACDOCA. This function prevents using this field in validation and substitution.

Figure 9 – Validation and substitution options

Table ACDOCA stores currency information at the ledger-specific level. The user needs to be careful from a simple aspect such as number range setup. For instance, the number range might be set up frequently as external to match the Financial Accounting (FI) document to have the same numbering as the material document. With a technical clearing account concept in FI-AA in place, such an account assigned purchase order (PO) invoices errors out (that is, it can’t be completed due to an error) because numbering could not be determined separately at the ledger group level if the numbering is made external. This is because FI-AA postings are always at the accounting principle level meaning ledger specific.

Not all traditional GUI reports or native SAP Fiori apps support all fields of table ACDOCA. Either the database query or the fields available in the model defined for the OData should have the new fields fetched. If not, then it needs modifications to the standard reports. To an extent, this can be achieved using ERP accelerators transaction code HDBC in field configurations.

 

Financial Statements

 

Although the above two sections deal with the generic setup of SAP S/4HANA Finance 1610, I need to discuss the financial statements, as they are the key reports used by any controller. Financial statements provide a real-time picture of the financial soundness of a company. Traditionally, financial statements can be viewed using transaction code F.01, and now an equivalent SAP Fiori app named Financial Statements is available. Next, I compare the features of the traditional transaction and the SAP Fiori app.

Financial statements generated with the traditional transaction code F.01 do not support user- defined currencies. The financial statements still have the old currency types only available in the Financial Statements selection screen (Figure 10).

Figure 10 – Currency type options displayed after executing transaction code F.01

The SAP Fiori app supports displaying of financial statements in freely definable currencies and also greatly helps in forward navigation to the line items. However, it has these limitations:

  • A Special evaluations tab available in financial statements generated with transaction code F.01 is not available in the SAP Fiori app. For example, a requirement to display an account with a zero balance is no longer possible in the app. The documentation of the app clearly mentions this limitation. This is a noted as a limitation as some localization demands a zero balance value to be visible in the statements.
  • The report cannot be exported or downloaded, so a finance department cannot pull data and perform detailed analysis.

There are minor changes between how the transactions behave in the SAP GUI versus the SAP Fiori app for instance, transaction code FB41, which is used to post directly to a tax-payable account. Traditionally, this transaction allows the user to post a G/L with a tax category enabled, although the need is quite contradictory. (Executing transaction code FB41 is for adjusting tax accounts — that is, a value entered directly instead of a value determined by the system based on the rate from the tax codes. Therefore, using transaction code FB41 is unnecessary if the system again asks for the tax code, but does not use it.) These features are now streamlined in the corresponding SAP Fiori app named Post Tax Payables.

(For more information on SAP S/4HANA 1610 read these SAPinsider articles:

You Can Now Do Realignments in Account-Based CO-PA with SAP S/4HANA 1610

You Are Now a Step Closer to Real-Time Profitability in SAP S/4HANA Finance with Fewer Settlements

Plan Your SAP S/4HANA Finance Migration with These Tips

Demystifying the Ledger, Currency Setup, and Currency Conversion in SAP S/4HANA Finance 1610

SAP S/4HANA: First Steps Toward Real-Time Profitability Analysis“)