Reading Sample Sappress 1350 Implementing SAP S4HANA Finance

First-hand knowledge.

Reading Sample These sample chapters describe the customizing steps you must perform for the new SAP General Ledger and the new Asset Accounting prior to your migration to SAP S/4HANA Finance.

“Customizing for the SAP General Ledger” “Customizing for the New Asset Accounting” Contents Index The Author

Anup Maheshwari

Implementing SAP S/4HANA Finance 535 Pages, 2016, $79.95 ISBN 978-1-4932-1350-4

www.sap-press.com/4045

Chapter 3

This chapter highlights the Customizing for SAP General Ledger and currencies, the integration of postings from Controlling, and the creation of ledger groups required as part of the migration to SAP S/4HANA Finance.

3

Customizing for the SAP General Ledger

Following are some of the key customization steps that you need to perform for migration to the new SAP General Ledger (new G/L) as part of the overall SAP S/4HANA migration: 왘 Checking and adopting fiscal year variants 왘 Migrating G/L settings 왘 Defining settings for the journal entry ledger 왘 Defining the ledger for the Controlling (CO) version 왘 Defining document types for postings in CO 왘 Defining offsetting account determination 왘 Defining the source ledger for migration of balances 왘 Executing a consistency check of G/L settings 왘 Activating the required business functions This configuration is completed under SAP Customizing Implementation Guide 폷 Migration from SAP ERP to SAP Accounting powered by SAP HANA 폷 Preparations and Migration of Customizing 폷 Preparations and Migration of Customizing for the General Ledger, as shown in Figure 3.1.

127

3

Customizing for the SAP General Ledger

Check and Adopt Fiscal Year Variants

4. Under Activate/Deactivate New Implementation Guide, choose Activate New IMG, and then select Execute (Figure 3.2).

Figure 3.2 Activating the New Implementation Guide

5. In another SAP session, enter the Program RFAGL_SWAP_MENU_NEW. 6. Select Execute. 7. Under Activate/Deactivate New Menu, choose Activate New Menu (Figure 3.3), and then select Execute so that the relevant structure is visible.

Figure 3.1 Customizing the General Ledger

Figure 3.3 Activating the New Menu

Let’s begin by activating the SAP reference IMG structure for SAP ERP Financials (FI).

3.2

3.1

Activate SAP Reference Implementation Guide for SAP ERP Financials

In this activity, you activate the SAP reference IMG structure for FI and the menu path that is associated with it by following these steps: 1. Select Transaction SA38. 2. Enter the Program RFAGL_SWAP_IMG_NEW. 3. Select Execute.

128

Check and Adopt Fiscal Year Variants

The migration to the Universal Journal requires the same fiscal year variant to be used in both FI and CO. In this activity, you compare the fiscal year variants between controlling areas and their assigned company codes. If an inconsistency exists in the fiscal year variant configuration, a report is created with a proposal for the required configuration change. You need to execute the report as part of the migration process. The fiscal year variants of CO and FI have to be aligned before the migration of the transaction data can be started. The report lists all CO areas and company codes that need to be changed, as well as the number of the posting periods and special periods.

129

3.2

3

Customizing for the SAP General Ledger

The Det. FYV for CoAr (determined fiscal year variant for controlling area) and Det. FYV for CoCd (determined fiscal year variant for company code) columns provide the proposal for the configuration change. The report must be executed using Transaction FINS_MIG_FYV for all relevant controlling areas. If no changes are required, the information window shown in Figure 3.4 appears.

Define Settings for the Journal Entry Ledger

The following settings are migrated: 왘 Company code assignments 왘 Currency settings 왘 Fiscal year variant 왘 Open period variant 왘 Settings for real-time integration of CO and FI After all these items are migrated successfully, you can proceed to the next step.

3.4

Figure 3.4 Aligning Fiscal Year Variants between CO and FI

3.3

Migrate General Ledger Customizing

In this activity, you migrate all the ledgers to the new configuration using Transaction FINS_MIG_LEDGER_CUST, as shown in Figure 3.5.

Define Settings for the Journal Entry Ledger

In this activity, you define ledgers, which you use in accounting. Only one ledger can be defined as the leading ledger (the standard leading ledger is 0L). There are two types of ledgers: 왘 Standard ledger The standard ledger consists of all journal entries related to any business transactions. 왘 Appendix ledger Introduced in SAP S/4HANA Finance, an appendix ledger is assigned to a standard ledger from where it inherits all the journal entry postings. Any specific adjustments required to be posted only to the appendix ledger aren’t duplicated in the standard ledger. Thus, the appendix ledger takes the base values from the standard ledger and then combines the specific appendix ledger postings. This prevents multiple data footprints and significantly reduces data redundancy because the journal entries don’t need to be posted to both the appendix and the standard ledger. You also need to assign company codes to ledgers and define currency settings and fiscal year variants. The step-by-step configuration settings are shown in Figure 3.6 through Figure 3.9. The following requirements must be met before performing this Customizing activity: 왘 Company codes are configured with currency, fiscal year variants, and open period variants.

Figure 3.5 Migrating General Ledger Customizing

130

131

3.4

3

Customizing for the SAP General Ledger

왘 Controlling areas are configured with currency types and fiscal year variants. 왘 Company codes are assigned to controlling areas. 왘 Migration and customization of the ledger is completed. 왘 Ledger 0L is configured as the leading ledger.

Define Ledger Groups

In this Customizing setting, you need to assign accounting principles to the ledger. This assignment ensures that documents posted for a particular accounting principle get posted to the assigned ledger while documents where the accounting principle hasn’t been assigned are posted to all ledgers (Figure 3.8 and Figure 3.9).

왘 The leading ledger is assigned to all company codes. In this Customizing setting, Ledger 0L needs to be assigned as the Leading Ledger (Figure 3.6). Here, you also need to create all the other standard (nonleading) ledgers and extension (appendix) ledgers required for parallel accounting for the organization.

Figure 3.8 Accounting Principle Assignment to Ledger 0L and Company Code

Figure 3.6 Standard Ledger Customizing

In this Customizing setting, all company codes need to be assigned to the leading ledger 0L. Here, you also need to configure company code assignments to other ledgers along with currency settings, fiscal year variants, and open period variants for nonleading ledgers. If you want to do parallel accounting using G/L accounts instead of various ledgers, you need to select the Parallel GL Accts checkbox (Figure 3.7).

Figure 3.9 Accounting Principle Assignment to Ledger L1 and Company Code

References/Tips For more information, see SAP Note 1951069: Different Fiscal Year Variants in General Ledger Accounting (New).

3.5 Figure 3.7 Ledger Assignment to Company Code

132

Define Ledger Groups

In this activity, you define ledger groups, as shown in Figure 3.10. The creation of ledger groups simplifies the individual functions and processes of SAP General

133

3.5

3

Customizing for the SAP General Ledger

Ledger Accounting. You can create as many ledger groups and can assign any number of ledgers in a ledger group as needed to meet your business goals.

Assign the Accounting Principle to the Ledger Group

by the posting period of the representative ledger. If the posting period of the representative ledger is open while the posting period of the nonrepresentative ledger is closed, the system still posts to all the ledgers. The criteria for a representative ledger are listed here: 왘 Any ledger can be assigned as a representative ledger if all the ledgers in the group have a fiscal year variant that is different from the one assigned to the company code. 왘 If a ledger in the group has the same fiscal year variant as assigned to the company code, that ledger must be assigned as the representative ledger within the ledger group. Thus, you may not be able to use the same ledger group for all the active company codes within the organization.

Figure 3.10 Customizing the Ledger Group

When a ledger is created in the system, a ledger group with the same name is automatically created whereby data to an individual ledger can be posted and accessed by merely entering the ledger group. Some of the properties of ledger groups include the following: 왘 You can rename the ledger group that was created automatically when creating the ledger. 왘 You can create ledger groups that enable you to bring several ledgers together for joint processing in a function. 왘 If a ledger group isn’t specified while posting an entry, the system by default posts to all the ledgers. Thus, creating ledger groups for all ledgers isn’t required. Within the ledger group, you need to assign and check one ledger as the representative ledger as shown in Figure 3.11. The best practice is to have the leading ledger 0L as your representative ledger. Posting to all the ledgers is determined

134

Figure 3.11 Defining the Ledger Group and Representative Ledger

3.6

Assign the Accounting Principle to the Ledger Group

After the ledger groups are created, you need to assign the ledger group to the accounting principle for the organizational legal and statutory reporting requirements. You can do this by choosing SAP Customizing Implementation Guide 폷 Financial Accounting (New) 폷 Financial Accounting Global Settings (New) 폷 Ledgers 폷 Parallel Accounting 폷 Assign Accounting Principle to Ledger Groups, as depicted in Figure 3.12. Upon execution of this Customizing transaction, you then assign the accounting principle to the ledger group, as shown in Figure 3.13.

135

3.6

3

Customizing for the SAP General Ledger

Define Document Types for Postings in Controlling

Figure 3.14 Assigning the Ledger to the CO Version

3.8

Define Document Types for Postings in Controlling

In this activity, you create and define new document types for CO-related postings. For example, you can create a separate document type that can be used for the reposting or allocation of primary costs. For document types used in CO, you must select the G/L account indicator under the Account types allowed section. Figure 3.12 Assign Accounting Principle to Ledger Groups

In the example shown in Figure 3.15, Document Type CO is defined with account type G/L account checked.

Figure 3.13 Ledger Groups Assigned to Accounting Principles

3.7

Define the Ledger for the Controlling Version

In this activity, you define a ledger where all actual data relevant to CO are posted by assigning Version 0 to a ledger. The version is assigned at the company code level, and the same ledger needs to be used for all company codes. Currently, Version 0 need to be assigned to the leading ledger for all company codes that are assigned to a CO area, as shown in Figure 3.14. The fiscal year variant of the company code must be identical to that of the controlling area.

136

Figure 3.15 Document Type Properties for CO

137

3.8

3

Customizing for the SAP General Ledger

3.9

Define Document Type Mapping Variants for Controlling Business Transactions

Check and Define Default Values for Postings in Controlling

input while posting. If a default ledger group isn’t specified in this Customizing activity, all CO-related transactions are posted to all the ledgers, as shown in Figure 3.18.

In this activity, you define a variant for mapping CO business transactions to document types. You must conduct and define this mapping exercise for all CO actual posting business transactions. A default mapping variant is generated during the Customizing activity for the migration of the ledger where all CO business transactions are mapped to the document type associated with the CO-FI real-time integration, as shown in Figure 3.16.

Figure 3.18 Default Values for Postings in CO

Figure 3.16 Variant for Mapping the CO Transaction to Document Types

To define the ledger group and assign the ledgers (Figure 3.19), you use the Customizing menu path, Financial Accounting (New) 폷 Financial Accounting Global Settings (New) 폷 Ledgers 폷 Ledger 폷 Define Ledger Group.

Figure 3.17 depicts how the CO business transactions are assigned to the document type.

Figure 3.19 Ledger Group Assignment

Figure 3.17 Mapping of CO Transactions to Document Types

3.10

Check and Define Default Values for Postings in Controlling

In this activity, you define default values for posting CO business transactions in which the user interfaces don’t allow any document type or ledger group as an

138

Here, you first create ledger groups as required, provide a description to each of the groups, and then assign ledgers as applicable to each of the ledger groups. When posting a document, you can specify a ledger group so that all the documents get posted only to those ledgers that are in that group. The system assigns a representative ledger within a group that has more than one ledger. The representative ledger is used to determine the posting period and to check if the period is open for posting. If the representative ledger is open, the system still posts to all the ledgers in the group, even though the posting period for the other ledgers in the group might be closed.

139

3.10

3

Customizing for the SAP General Ledger

3.11

Activate Business Functions

Define the Offsetting Account Determination Type

In this activity, you define the offsetting account determination for all applications. This activity needs to be executed before the migration to SAP S/4HANA Finance. You should choose the As case 2, but including line items generated automatically option, as shown in Figure 3.20, because this option always displays the offsetting account with the highest amount along with the line items that are generated automatically.

Figure 3.21 Source Ledger for Migration of Balances

3.13

Execute Consistency Check of General Ledger Settings

In this activity, the Customizing settings for the ledgers are checked using Transaction FINS_CUST_CONS_CHK. This check must be executed before migration of transaction data with no error messages. You should receive the Check passed message, as shown in Figure 3.22, upon execution of this consistency check.

Figure 3.20 Define Offsetting Account Determination Figure 3.22 Consistency Check of General Ledger Settings

3.12

Define the Source Ledger for Migration of Balances

In this activity, you define the source ledger and the source database table of the balances for SAP General Ledger Accounting from which you want to transfer the opening balances. To do so, you use the following: 왘 Target ledger 왘 Company code (you can specify * to apply the settings to all company codes) 왘 Starting fiscal year (by specifying year “0001”, you apply the settings for all fiscal years) Organizations using the new G/L can specify one entry per ledger, where the source and target ledger are equal. In the example in Figure 3.21, 0L is defined as both the source and target ledger for CoCd 1000 for the purpose of migration of balances.

140

3.14

Activate Business Functions

In this activity, you need to activate the business functions that are necessary for migrating to SAP S/4HANA Finance. You have to activate the following business functions in the Customizing system using Transaction SFW5 and then import them into the production system: 왘 FIN_GL_CI_1 This new SAP General Ledger Accounting business function helps to optimize the processes related to parallel accounting as well as planning and reporting based on profit centers. 왘 FIN_GL_CI_2 This new SAP General Ledger Accounting business function enhances the processes for parallel accounting by enabling its integration with CO.

141

3.14

3

Customizing for the SAP General Ledger

왘 FIN_GL_CI_3 This business function helps to improve the processes related to periodic tasks and optimize the usage of archive functionality. Analysis of actual/actual comparison between the ledgers can be done while conducting the financial statement analysis. This business function also plays an important role in managing the assigned numbers when assets are transferred.

Chapter 4

With the installation of SAP S/4HANA Finance, classic Asset Accounting is replaced by new Asset Accounting. This chapter focuses on the Customizing and activation steps related to new Asset Accounting, including performing the prechecks, migrating and defining the chart of depreciation, and specifying the posting rules.

4

Customizing for the New Asset Accounting

All three business functions activate functionality in G/L, which is mandatory for the implementation of SAP S/4HANA Finance (Figure 3.23).

Figure 3.23 New General Ledger Business Functions Activated

3.15

Summary

You’ll need to execute the Customizing steps for the G/L before migration to SAP S/4HANA Finance to accommodate the required changes. This requires checking the consistency of the fiscal year variants between company code and controlling area, defining the ledgers and their assignment to the accounting principle, setting up the postings in CO, and activating any missing business functions. You now understand the prerequisites, preparations, and migration requirements related to the new SAP General Ledger Accounting, and you can perform the Customizing steps as well. Let’s now move on to Chapter 4, where we’ll discuss the Customizing for the new Asset Accounting.

142

Prior to the migration, you need to customize the new Asset Accounting (new FIAA) in the system, which is replacing the classic Asset Accounting (classic FI-AA) in SAP S/4HANA Finance. Some of the key customization steps that you need to perform for migration to the new FI-AA are covered in this chapter. The SAP S/4HANA Finance migration includes performing prechecks for using the new FI-AA, checking accounting principle and ledger group settings, assigning the accounting principle to the ledger group, making any additional manual settings in Customizing for new FI-AA, and checking the prerequisites for activating the new FI-AA. Other tasks you must perform include determining and migrating active charts of depreciation, changing definitions of depreciation areas, defining transfer rules for the posting values and depreciation terms of a depreciation area, checking the currency type of depreciation areas, and finally activating the Customizing switch for new FI-AA. All of the major steps, along with any additional details, are shown in Figure 4.1. When you install SAP S/4HANA Finance, the system shows the Customizing structure for new FI-AA in the SAP Reference IMG, as shown in Figure 4.1. By default, it hides the Customizing structure for classic FI-AA.

143

4

Customizing for the New Asset Accounting

Install SAP S/4HANA Finance with New Asset Accounting

4.1

Prerequisites

Before you install SAP S/4HANA Finance, you have to ensure that the prerequisites are met by using Program RASFIN_MIGR_PRECHECK for preliminary checks. You have to import this program to your system by means of SAP Note 1939592 before you install SAP S/4HANA Finance. Perform this check in all of your SAP clients— the development client, the test client, and the production client. You have to activate the SAP ERP Financials (FI) Extension (EA-FIN) because it provides the depreciation calculation program (DCP), which is used for the new depreciation calculation. As a prerequisite, you also need to migrate the assigned chart of depreciation. You have to ensure that the parallel currencies in the leading ledger of SAP General Ledger Accounting and the depreciation areas of the leading valuation in FI-AA are the same. The company codes that are assigned to the same chart of depreciation should have the same number and type of parallel currencies used in SAP General Ledger Accounting. Figure 4.1 Customizing New Asset Accounting

No postings to FI-AA are allowed until the migration of Customizing and transaction data is complete. After the migration activities are complete, and the new FI-AA has been activated, you can’t revert to classic FI-AA. New FI-AA needs to be configured in preparation for migrating to SAP S/4HANA Finance. Some of the tasks will include setting the new FI-AA activation status to In Preparation, creating a new ledger group for local valuation, assigning the ledger group to the local generally accepted accounting principles (GAAP), and assigning all the active company codes to the chart of depreciation. You’ll also be responsible for configuring and assigning the accounting principle to the depreciation areas, setting up accounts assigned to the local accounting principle as asset reconciliation accounts, creating and assigning the technical clearing account, specifying alternative document types for accounting principle-specific document postings, and defining the depreciation area for quantity updates.

144

Make sure that the period-end closing has been performed along with the reconciliation of the asset subsidiary ledger with the SAP General Ledger (G/L). If you happen to install SAP S/4HANA Finance at the close of the fiscal year, you should also perform year-end closing before the migration.

4.2

Install SAP S/4HANA Finance with New Asset Accounting

After you start the installation of SAP S/4HANA Finance, it’s no longer possible to post any transactions in FI-AA. If you were already using classic FI-AA, then you only have to migrate your charts of depreciation and check and possibly add to delta Customizing. If you weren’t already using FI-AA and now want to use it in the future, you have to configure your system completely for FI-AA. You’ll also need to complete and follow the relevant steps for migrating to the new SAP General Ledger Accounting before you can customize the new FI-AA.

145

4.2

4

Customizing for the New Asset Accounting

4.3

Migrate Charts of Depreciation

You either have to migrate the charts of depreciation automatically using the migration program or do it manually. You should run the migration Program FAA_CHECK_MIG2SFIN as a test run first, as shown in Figure 4.2, so that you can correct any errors before processing the update run. If you run the program as an update run, the system updates the tables for the depreciation areas.

Customization Prior to Activation

왘 Settings for posting to the G/L (for each depreciation area): Asset Accounting (New) 폷 Valuation 폷 Depreciation Areas 폷 Define Depreciation Areas 왘 Value transfer for acquisition and production costs (APC): Asset Accounting (New) 폷 Valuation 폷 Depreciation Areas 폷 Specify Transfer of APC Values 왘 Transfer of depreciation terms: Asset Accounting (New) 폷 Valuation 폷 Depreciation Areas 폷 Specify Transfer of Depreciation Terms 왘 Use of parallel currencies: Asset Accounting (New) 폷 Valuation 폷 Currencies 폷 Specify the Use of Parallel Currencies You can also use these activities if you want to check the Customizing settings after charts of depreciation have been migrated automatically.

4.4

Customization Prior to Activation

After the migration of the charts of depreciation, you have to make additional Customizing settings as described in the following subsections, before you can check and activate new FI-AA.

Figure 4.2 Migrating Chart of Depreciation

You’ll have to manually migrate the charts of depreciation in the following cases: 왘 Your charts of depreciation couldn’t be migrated during the automatic migration because the migration program doesn’t recognize the starting situation defined in your system. 왘 Your charts of depreciation are assigned to a deactivated company code, and because the deactivated company code’s data haven’t been archived yet, the company code must be migrated with the document migration. This chart of depreciation should therefore be migrated manually. This is possible at any time by making the following settings in Customizing for new FI-AA: 왘 Assignment of accounting principles and ledger groups to depreciation areas: Asset Accounting (New) 폷 Valuation 폷 Depreciation Areas 폷 Define Depreciation Areas

146

4.4.1

Define Asset Balance Sheet Accounts of Parallel Valuation

This step is required if you’re using the accounts approach for parallel valuation. It isn’t relevant if you’re using the ledger approach. In this activity, you can define G/L accounts as reconciliation accounts for depreciation areas of a parallel valuation of FI-AA, or you can define them again as accounts for normal posting. In the accounts approach, one or more additional valuations are represented by separate depreciation areas where the posting is made to separate accounts in the G/L. Before the migration, these asset balance sheet accounts were posted directly in FI. In the future, the asset values for both the leading and parallel valuation will be posted directly in FI-AA. Thus, these asset balance sheet accounts must be defined as asset reconciliation accounts because they will only be allowed to be posted in FI-AA. You can change the existing balance sheet accounts of the parallel valuation that were posted directly as asset reconciliation accounts for the future in Customizing

147

4.4

4

Customizing for the New Asset Accounting

under Asset Accounting (New) 폷 Preparations for Going Live 폷 Production Startup 폷 Accounts Approach. You can reset the reconciliation accounts for parallel valuations, as shown in Figure 4.3.

Customization Prior to Activation

4.4.3

Define the Technical Clearing Account for Integrated Asset Acquisition

This is a necessary process to post an integrated asset acquisition in SAP S/4HANA Finance. When, using Transaction F-90, you post an asset acquisition through a vendor and input all the necessary parameters, including a debit to the fixed asset and a credit to the vendor account, new FI-AA breaks the posting into the following two components: 1. The first document is created with document Type AA which is posted for the specified ledger/ledger group with a debit to the asset and a credit to the technical clearing account, as specified in Customizing. In Figure 4.4, the document is posted for Accounting Principle IFRS, while in Figure 4.5, the document is posted for Accounting Principle US GAAP.

Figure 4.3 Defining Reconciliation Accounts for New Asset Accounting

Before the migration to SAP S/4HANA Finance, you need to check and reconcile the balance sheet values of both FI-AA and SAP General Ledger Accounting for parallel valuations as part of closing operations.

4.4.2

Define the Depreciation Area for a Quantity Update

In this activity, you specify which depreciation area you want to use for updating quantities in your chart of depreciation. This setting is relevant if you’re using collective low-value assets in your organization. When there is a posting made to this depreciation area, the quantities are updated in the asset master record. The Customizing is done under Asset Accounting (New) 폷 General Valuation 폷 Depreciation Areas 폷 Define Depreciation Area for Quantity Update.

148

Figure 4.4 FI-AA Posting for IFRS

2. The second document is created with document Type KR, which is not posted to any specific ledger/ledger group.

149

4.4

4

Customizing for the New Asset Accounting

Customization Prior to Activation

for Integrated Asset Acquisition 폷 Define Technical Clearing Account for Integrated Asset Acquisition, as shown in Figure 4.6.

Figure 4.6 Defining the Technical Clearing Account for Integrated Acquisition

4.4.4

Figure 4.5 FI-AA Posting for US GAAP

The business transaction is thus divided into an operational part and a valuating part during the integrated asset acquisition posting: 왘 For the operational part (vendor invoice), a ledger-group-independent document valid for all accounting principles is posted against the technical clearing account for integrated asset acquisitions. 왘 For each valuating part (capitalization of the asset), a separate ledger-group-specific document valid for each of the accounting principles is posted against the technical clearing account for integrated asset acquisitions. Thus, the technical clearing account for integrated asset acquisitions is posted automatically and always has a zero balance for each of the accounting principles in the chart of depreciation. Because it has a zero balance, this account doesn’t appear in the balance sheet, but it appears as notes to the financial statement. As a prerequisite, you need to create a new G/L account as an asset reconciliation account with the following description: “technical clearing account for integrated asset acquisitions.” This account is created using Transaction FS00 and appears in both the chart of accounts and the company code section. You need to assign this G/L account in the FI-AA account determination for your chart of accounts in Customizing under Asset Accounting (New) 폷 Integration with General Ledger Accounting 폷 Technical Clearing Account

150

Specify an Alternative Document Type for Accounting-Principle-Specific Documents

If your organization is using the new G/L with document splitting activated, and you want the document splitting rules for the valuating document (asset acquisition) and the operative document (Accounts Payable) to be different, you’ll need to specify separate document types for the valuating document that are valid for each of the accounting principles. Alternatively, if your organization policy is to have separate document types for both valuating and operative documents, this Customizing activity needs to be executed. You need to check if the existing document types can be used for this activity, or if you need to create a new one to assign to the valuating documents. You assign the alternative document type for the posting of your accounting-principle-specific valuating documents in Customizing under Asset Accounting (New) 폷 Integration with General Ledger Accounting 폷 Integrated Transactions: Alternative Doc. Type for Accounting-Principle-Specific Documents 폷 Specify Alternative Document Type for Accounting-Principle-Specific Documents.

4.4.5

Specify Revenue Distribution for Asset Retirement

You can distribute revenues generated from the retirement of assets for a company code either on the net book value or on an acquisition and production cost (APC) basis. In this Customizing step, you need to specify the method for distribution of revenue for asset retirement under Asset Accounting (New) 폷 Transactions 폷 Retirements 폷 Gain/Loss Posting 폷 Define Revenue Distribution for Fixed Asset Retirement, as shown in Figure 4.7.

151

4.4

4

Customizing for the New Asset Accounting

Check Prerequisites for Activating New Asset Accounting

4.5

Figure 4.7 Revenue Distribution Method for Asset Retirement

4.4.6

Post Net Book Value Instead of Gain/Loss

In this step, for each company code level, you need to specify the posting method for the retirement of an asset due to the sale or scrapping of that asset. By default, the standard process is to post a gain or a loss during the asset retirement; however, based on your legal and organizational requirement, you can configure to post the net book value of the assets for a depreciation area. In that case, the net book value is posted to the account for clearing of revenue from asset sales to either vendors or affiliated companies. In some countries (e.g., France), you’re legally required to post the net book value. Therefore, you need to check if it’s a legal requirement to post the net book value for individual depreciation areas and then configure accordingly in Customizing under Asset Accounting (New) 폷 Transactions 폷 Retirements 폷 Gain/Loss Posting 폷 Post Net Book Value Instead of Gain/Loss 폷 Specify Depreciation Areas for Net Book Value Posting. First, you must identify the company codes where you require the use of this posting option. Next, you need to identify the depreciation areas within the company codes for posting the net book value to a revenue clearing account during the asset retirement process.

4.4.7

After you’ve migrated the charts of depreciation, made the assignments to the company codes, and performed the additional manual Customizing settings, you can then determine whether the prerequisites for activating the new FI-AA have been met. In this activity, you check the prerequisites for parallel valuation in the new FIAA. The prerequisite for changing the leading valuation in the new SAP General Ledger Accounting is met by setting up and activating the business function FIN_ AA_PARALLEL_VAL using Transaction SFW5, as shown in Figure 4.8.

Figure 4.8 Business Function FIN_AA_PARALLEL_VAL Activated

You then need to execute Transaction FAA_CHECK_ACTIVATION to check if all prerequisites are met for activating the business function PARALLEL_VAL Customizing switch and if all periodic postings have been successfully completed. You can activate new FI-AA using the business function PARALLEL_VAL Customizing switch. This program checks whether all the prerequisites for activating new FI-AA have been met. You also need to ensure that no postings are made between the execution of Transaction FAA_CHECK_ACTIVATION and the import of the PARALLEL_VAL Customizing switch, as shown in Figure 4.9.

Check Transaction Types

In the existing SAP ERP environment, if some of the transaction types that you had been using were restricted to certain depreciation areas, those transaction types can’t be used after the migration. You need to ensure that the current, nonrestricted transaction types are adequate to meet your requirements. If not, then you must create new transaction types that don’t have restrictions to depreciation areas to bridge the gap.

152

Check Prerequisites for Activating New Asset Accounting

Figure 4.9 Check Prerequisites for Parallel Valuation in FI-AA

153

4.5

4

Customizing for the New Asset Accounting

Change Definitions of Depreciation Areas

The report must show a green light under the Type column, as shown in Figure 4.10. Otherwise, activation of new FI-AA isn’t possible.

Figure 4.10 Checking Data before Activating the PARALLEL_VAL Customizing Switch

4.6

Determine Active Charts of Depreciation

In this Customizing step, you need to check if all the active charts of depreciation have been migrated and assigned to the company code before any documents can be migrated, as shown in Figure 4.11. You need to perform the following activities: 1. Check if all active and relevant company codes are assigned the correct chart of depreciation. 2. Delete the assignments for charts of depreciation that aren’t relevant or are unused.

Figure 4.12 Assigning Charts of Depreciation to Company Codes

4.7

Change Definitions of Depreciation Areas

The migration of the chart of depreciation is done in such a way that the Customizing settings as depicted in Figure 4.15 allow all depreciation areas to post immediately to the G/L instead of periodically. This also applies for reserves for special depreciation areas, as shown in Figure 4.13.

Figure 4.11 Determining Active Charts of Depreciation

All links between “sample” charts of depreciation and company codes must be deleted because they will trigger an error during new FI-AA activation (Figure 4.12).

154

Figure 4.13 Depreciation Area Posting to the General Ledger

155

4.7

4

Customizing for the New Asset Accounting

Specify Transfer of Acquisition and Production Cost Values

For your depreciation areas, you may select one of following four options in the G/L column from in Figure 4.13 to specify if and how they should post automatically to the G/L:

It’s normally sufficient to post APC transactions and depreciation from one area automatically to the G/L. You might need additional areas that post automatically to the G/L for the following reasons:

왘 AREA DOES NOT POST 왘 AREA POSTS DEPRECIATION ONLY

왘 For cost-accounting purposes, you want to post depreciation that differs from book depreciation to expense accounts or cost elements.

왘 AREA POSTS IN REALTIME

왘 You need special valuations for the balance sheet (e.g., special reserves).

왘 AREA POSTS APC IMMEDIATELY AND DEPRECIATION

왘 You have special requirements for legal consolidation of your corporate group. 왘 If you’re using the new SAP General Ledger Accounting and the ledger approach, you can specify additional depreciation areas from which APC transactions are posted automatically to the G/L.

4.8

Figure 4.14 Account Determination Assignment to Chart of Depreciation

Specify Transfer of Acquisition and Production Cost Values

In this activity, you define transfer rules of APC posting values of depreciation areas, as shown in Figure 4.16. These transfer rules define the depreciation areas that will have identical asset values, as shown in Figure 4.17.

The standard depreciation areas in the SAP reference chart of depreciation are set up so that book depreciation area 01 posts APC transactions and depreciation automatically to the G/L, as shown in Figure 4.15. The system posts automatically to the G/L from other standard depreciation areas in accordance with the specific requirements of the country.

Figure 4.16 Specify Transfer of APC Values

In the ValAd field in Figure 4.17, you specify the reference depreciation area that provides values to another depreciation area. The system transfers the posting amounts of any transactions that affect APC from this area to the dependent area. Figure 4.15 Depreciation Area Definition

156

157

4.8

4

Customizing for the New Asset Accounting

Specify Transfer of Depreciation Terms

Figure 4.18 Specify Transfer of Depreciation Terms

Figure 4.17 Depreciation Area Rules

You must adhere to the following rules when transferring APC values: 왘 A transfer of APC values is only possible from depreciation areas that have been assigned the same accounting principle. 왘 For those depreciation areas that post their APC in real time to SAP General Ledger Accounting, the depreciation area must never use values from another depreciation area. 왘 When transferring values from one depreciation area to another, it doesn’t make any difference if the depreciation area adopts values from an area that has a key either greater or smaller than its own key.

4.9

Specify Transfer of Depreciation Terms

In this activity, you specify how the depreciation terms from one depreciation area are adopted to another depreciation area, as shown in Figure 4.18. The terms can be transferred between depreciation areas that have been assigned the same accounting principle. A depreciation area can also adopt depreciation terms from a depreciation area that has a larger key than it does.

158

It’s only possible to adopt depreciation terms from depreciation areas that have the same ledger group. For those depreciation areas that post their APC to SAP General Ledger Accounting in real time, the following applies: 왘 Depreciation areas that manage APC are never allowed to adopt depreciation terms from another depreciation area. In that case, enter “00” as the key for the depreciation area. 왘 The other depreciation areas that post in real time (e.g., areas for investment support or revaluation) are allowed to adopt depreciation terms from another area, as long as both areas have the same ledger group. Within the customizing activity shown in Figure 4.18 using Transaction OABD, you specify the depreciation area from which the depreciation terms are adopted by the current depreciation area in the Transfer of Depreciation Terms from Depreciation Area (TTr) field. The terms can be transferred only from a depreciation area to which the same accounting principle is assigned. A depreciation area can also adopt depreciation terms from a depreciation area that has a larger key than it does, as shown in Figure 4.19. In the standard system, changes to control parameters in the reference depreciation area aren’t automatically transferred to dependent depreciation areas that adopt depreciation terms. Instead, you can change the depreciation terms in dependent depreciation areas in the asset master record. However, when you set the Identical checkbox shown in Figure 4.19, the system transfers all changes in the reference depreciation area to the dependent depreciation areas, where it’s then not possible to change them.

159

4.9

4

Customizing for the New Asset Accounting

Adjust Parameters in Charts of Depreciation

Figure 4.21 New Asset Accounting Active

4.11

Adjust Parameters in Charts of Depreciation

This activity supports you in adjusting the parameters for charts of depreciation, as shown in Figure 4.22. Figure 4.19 Rules for Takeover of Depreciation Terms

4.10

Activate New Asset Accounting

In this activity, the new FI-AA functionality is activated, as shown in Figure 4.20. When you execute this Customizing transaction, the system performs various checks and then saves this setting if no errors are encountered. After the checks have been passed successfully and the settings have been saved, new FI-AA becomes activated. From this point onward, you can post using the new posting logic.

Figure 4.22 Adjust Parameters in Chart of Depreciation

You can use this activity, if necessary, to make the following adjustments:

Figure 4.20 Activate New Asset Accounting

After executing the Customizing setting in Figure 4.20, you’ll be taken to the new FI-AA activation screen where you can select the Actv. (active) option, and then save (Figure 4.21).

160

왘 Assign the accounting principle An accounting principle is assigned to each depreciation area, including the nonposting depreciation areas. The system derives the accounting principle from the relevant ledger group already assigned to the depreciation area. For each set of depreciation areas that are assigned to the same accounting principle, only one depreciation area is allowed to manage APC and have the option Area Posts in Real Time or Area Posts APC Immediately, Depreciation Periodically.

161

4.11

4

Customizing for the New Asset Accounting

왘 Change posting indicator for depreciation areas The system changes the settings for posting in the G/L, whereby the depreciation areas that represent reserves for special depreciation, for example, in the future, post immediately to the G/L. The execution of the program as depicted in Figure 4.22 changes the depreciation areas for the specified chart of depreciation to Depreciation Area Posts Balance Sheet Value Immediately, Depreciation Periodically. The charts of depreciation are adjusted manually in the following cases:

Summary

depreciation is active. You also need to set up a parallel area for each additional currency used in the corresponding G/L. You need to ensure that all inconsistencies and errors are fixed during the migration, and it’s prudent to involve all the stakeholders to evaluate relevant data for acceptance of migration. After reading this chapter, you now understand the Customizing of and migration steps for the new FI-AA. Let’s now move on to Chapter 5, where we’ll discuss the steps you need to take to customize Controlling for your SAP S/4HANA Finance migration.

왘 The parameters of the charts of depreciation couldn’t be adjusted automatically because the program doesn’t recognize the starting situation defined in your system. 왘 Adjusting the charts of depreciation manually is standard procedure, regardless of circumstances. 왘 The charts of depreciation in FI-AA are assigned to a deactivated company code. The data of this deactivated company code aren’t archived; therefore, this data must be migrated with the document migration.

4.12

Display Migration Log

You can use this activity to display the migration log of the charts of depreciation during either the test run or the update run, as shown in Figure 4.23. Any error messages must be resolved before you can mark the migration to new FI-AA as complete.

Figure 4.23 Job Log for Adjusting Parameters in a Chart of Depreciation

4.13

Summary

The introduction of SAP S/4HANA Finance introduced some significant changes in the FI-AA module. You need to execute the special check Report RASFIN_ MIGR_PRECHECK for FI-AA installation and check whether the new asset

162

163

4.13

Contents Preface ............................................................................................................. Introduction .....................................................................................................

19 27

PART I Migrating to SAP S/4HANA Finance 1

Preparation ................................................................................ 51 1.1 1.2 1.3 1.4

1.5 1.6 1.7

1.8

1.9

1.10

Check Functional Scope and Restrictions ....................................... Feasibility Checklist ....................................................................... The Maintenance Planner and Prechecks ....................................... Check Custom Coding ................................................................... 1.4.1 Check Custom Code and Modifications ............................ 1.4.2 Handling Custom-Defined Fields and Interfaces ................ Check Sizing .................................................................................. Precheck for Migration to New Asset Accounting .......................... Activate Business Functions ........................................................... 1.7.1 Activate Business Functions for Asset Accounting, Parallel Valuation ............................................................. 1.7.2 Activate Enterprise Extension EA-FIN ............................... 1.7.3 Activate Business Function FIN_AA_CI_1 ......................... Check and Activate New Depreciation Calculation ......................... 1.8.1 Execute the Periodic Depreciation Posting Run ................ 1.8.2 Execute Year-End Closing ................................................. 1.8.3 Fiscal Year Change ........................................................... Consistency Checks ....................................................................... 1.9.1 SAP ERP Financials Data Consistency Checks .................... 1.9.2 Reconciliation of General Ledger and the Accounts Payable/Accounts Receivable Subledgers .......... 1.9.3 Reconciliation of the General Ledger with Asset Accounting ............................................................. 1.9.4 Reconciliation of the General Ledger with Materials Management .................................................... 1.9.5 Reconciliation of Ledgers ................................................. Perform Period-End Closing Activities ............................................ 1.10.1 Copy Number Ranges ....................................................... 1.10.2 Lock Periods in Materials Management ............................ 1.10.3 Perform Closing for Periodic Asset Postings ...................... 1.10.4 Execute the Periodic Depreciation Posting Run ................

51 53 60 60 61 61 62 63 65 65 67 69 69 70 71 72 73 73 76 77 79 81 83 83 84 84 85

7

Contents

Contents

1.10.5 1.10.6 1.10.7 1.10.8

1.11 1.12 1.13

2

3

2.2 2.3 2.4 2.5 2.6

2.7

2.8

Installation and Upgrade Checklist ................................................. 2.1.1 SAP HANA and Minimum Versions .................................. 2.1.2 Software Update Manager ................................................ 2.1.3 SAP HANA Live ................................................................ 2.1.4 Administrator’s Guide, Release Information Note, and Browser Support ........................................................ 2.1.5 SAP Cash Management Powered by SAP HANA, Cost Objects, and Cost Object Hierarchies ........................ 2.1.6 Industry Solutions and Add-Ons ....................................... 2.1.7 Maintenance Optimizer .................................................... 2.1.8 Target Stack XML and SAP NetWeaver Kernel .................. 2.1.9 Customer Code ................................................................ 2.1.10 Data Definition Language Statement Corrections .............. Use the Maintenance Planner ........................................................ Install the Related Software Component Version ........................... Apply SAP Notes ........................................................................... Content Deployment with SAP HANA Application Lifecycle Management ................................................................................. Perform HANA-tization ................................................................. 2.6.1 HANA-tization Checks ...................................................... 2.6.2 HANA-tization Tools ........................................................ Optimization ................................................................................. 2.7.1 Optimization Approach .................................................... 2.7.2 Optimization Tools ........................................................... 2.7.3 Optimization Best Practice ............................................... 2.7.4 SAP HANA Modeling ....................................................... Summary .......................................................................................

3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15

106 106 108 109 109 110 110 111 114 114 115 115 116 118 120 120 121 121 122 123 124 124 125 125

Customizing for the SAP General Ledger .................................. 127 3.1

Installation and Upgrade .......................................................... 105 2.1

8

Verify Held Documents Status .......................................... 85 Carry Balances Forward to the Current Fiscal Year ............ 86 Reset Valuations for Periods in the Current Fiscal Year ..... 88 Lock Prior Periods in SAP ERP Financials and Controlling ....................................................................... 89 1.10.9 Batch Jobs ........................................................................ 91 1.10.10 Execute Report to Confirm Asset Accounting Prerequisites .................................................................... 91 1.10.11 Lock Users ........................................................................ 91 Consistency Check before Activation of SAP S/4HANA Finance ...... 91 Execute Business Reconciliation ..................................................... 93 Summary ....................................................................................... 103

4

Activate SAP Reference Implementation Guide for SAP ERP Financials ........................................................................ Check and Adopt Fiscal Year Variants ............................................ Migrate General Ledger Customizing ............................................. Define Settings for the Journal Entry Ledger .................................. Define Ledger Groups .................................................................... Assign the Accounting Principle to the Ledger Group .................... Define the Ledger for the Controlling Version ................................ Define Document Types for Postings in Controlling ....................... Define Document Type Mapping Variants for Controlling Business Transactions .................................................. Check and Define Default Values for Postings in Controlling .......... Define the Offsetting Account Determination Type ....................... Define the Source Ledger for Migration of Balances ....................... Execute Consistency Check of General Ledger Settings .................. Activate Business Functions ........................................................... Summary .......................................................................................

128 129 130 131 133 135 136 137 138 138 140 140 141 141 142

Customizing for the New Asset Accounting ............................. 143 4.1 4.2 4.3 4.4

4.5 4.6 4.7 4.8 4.9

Prerequisites .................................................................................. Install SAP S/4HANA Finance with New Asset Accounting ............. Migrate Charts of Depreciation ...................................................... Customization Prior to Activation .................................................. 4.4.1 Define Asset Balance Sheet Accounts of Parallel Valuation ............................................................. 4.4.2 Define the Depreciation Area for a Quantity Update ........ 4.4.3 Define the Technical Clearing Account for Integrated Asset Acquisition ............................................. 4.4.4 Specify an Alternative Document Type for Accounting-Principle-Specific Documents ........................ 4.4.5 Specify Revenue Distribution for Asset Retirement ........... 4.4.6 Post Net Book Value Instead of Gain/Loss ........................ 4.4.7 Check Transaction Types .................................................. Check Prerequisites for Activating New Asset Accounting .............. Determine Active Charts of Depreciation ....................................... Change Definitions of Depreciation Areas ...................................... Specify Transfer of Acquisition and Production Cost Values ........... Specify Transfer of Depreciation Terms ..........................................

145 145 146 147 147 148 149 151 151 152 152 153 154 155 157 158

9

Contents

4.10 4.11 4.12 4.13

Contents

Activate New Asset Accounting ..................................................... Adjust Parameters in Charts of Depreciation .................................. Display Migration Log ................................................................... Summary .......................................................................................

7.3.5

160 161 162 162 7.4

5

Customizing for Controlling ...................................................... 165 5.1 5.2 5.3 5.4 5.5 5.6 5.7

Execute SAP Business Warehouse Delta Extraction for Account-Based Profitability Analysis .............................................. Adapt Settings for Profitability Segment Characteristics ................. Maintain the Operating Concern ................................................... Maintain the Operating Concern for the Banking Add-On ............. Activate Account-Based Profitability Analysis ................................. Transport Operating Concern ........................................................ Summary .......................................................................................

166 166 167 168 169 169 170

7.5

7.6

6

Customizing for Migration of House Bank Accounts ............... 171 6.1 6.2 6.3

6.4

Define Number Ranges for Bank Account Technical IDs ................. Define Number Ranges for Change Requests ................................. Define Settings for Bank Account Master Data ............................... 6.3.1 Bank Account Types ......................................................... 6.3.2 Define Sensitive Fields to Be Protected from Changes ...... 6.3.3 Define Import Methods for Bank Statements .................... 6.3.4 Define Signatory Groups for Payment Approvals ............... 6.3.5 Define the Signatory Groups and Approval Sequence for Approval Patterns ....................................................... 6.3.6 Assign Approval Patterns .................................................. Summary .......................................................................................

172 172 173 173 174 176 176

7.7

177 178 179 7.8

7

Data Migration .......................................................................... 181 7.1 7.2 7.3

10

Partitioning of the Universal Journal Entry Line Items Table ........... Regenerating Core Data Services Views and Field Mapping ........... Migration of Cost Elements ........................................................... 7.3.1 Check Consistency of SAP General Ledger Accounts and Cost Elements ............................................................ 7.3.2 Migrate Secondary Cost Elements to the Chart of Accounts ...................................................................... 7.3.3 Display Status of Migration of Cost Elements .................... 7.3.4 Migrate Default Account Assignments ..............................

182 183 185 187

7.9 7.10

189 190 190

7.11

Display the Status of the Default Account Assignments Migration ......................................................................... 7.3.6 Adopt Authorizations ....................................................... 7.3.7 Define Authorizations and Profiles ................................... Technical Check of Transaction Data .............................................. 7.4.1 Analyze Transactional Data ............................................... 7.4.2 Display Status of Analysis of Transaction Data .................. 7.4.3 Reconcile Transactional Data ............................................ 7.4.4 Display Status of Technical Reconciliation of Transactional Data ........................................................... Enrichment of Data ....................................................................... 7.5.1 Enrich Transactional Data ................................................. 7.5.2 Display Status of Transactional Data Enrichment .............. 7.5.3 Check of Migrated Documents ......................................... 7.5.4 Display Status of Migrated Documents Check .................. Migration of Line Items into New Data Structure ........................... 7.6.1 Migrate Accounting Documents to Universal Journal Entry Structure ................................................................. 7.6.2 Display the Status of Document Migration to Universal Journal Entry ..................................................... 7.6.3 Check Migration of Accounting Documents to Universal Journal Entry ..................................................... 7.6.4 Display Status of Accounting Document Migration Check ............................................................... 7.6.5 Migrate General Ledger Allocations .................................. Migration of Balances .................................................................... 7.7.1 Migrate Balances .............................................................. 7.7.2 Display Status of Migration of Balances ............................ 7.7.3 Check Migration of Balances ............................................ 7.7.4 Display Status of Migration of Balances Check .................. Calculation of Depreciation and Totals Values ............................... 7.8.1 Calculate Initial Depreciation Values ................................ 7.8.2 Display Status of Calculate Initial Depreciation Values ...... 7.8.3 Check Initial Depreciation and Total Values ...................... 7.8.4 Display Status of Check Initial Depreciation and Total Values ..................................................................... Migration of House Bank Accounts ................................................ Completing the Migration ............................................................. 7.10.1 Reconcile and Compare Migrated Data ............................ 7.10.2 Set Migration to Completed ............................................. Migration with Near Zero Downtime ............................................ 7.11.1 Overview of Near Zero Downtime ....................................

192 192 193 198 199 200 203 204 207 208 209 210 211 211 212 213 214 216 217 219 219 220 221 222 226 227 228 229 229 232 233 234 235 235 236

11

Contents

7.12

8

7.11.2 Restrictions on Business ................................................... 7.11.3 Activities on the Clone System ......................................... 7.11.4 Delta Migration ................................................................ Summary .......................................................................................

10.3.2 10.3.3 10.3.4 10.3.5

237 237 237 239

Post-Migration Activities .......................................................... 241 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9

9

Contents

Run Reconciliation Reports to Check Data Consistency .................. Validate Business Process to Ensure Successful Migration .............. Transfer Application Indexes .......................................................... Display Status of Application Indexes Transfer ............................... Fill Due Dates in SAP ERP Financials Documents ........................... Display Status of Due Dates into SAP ERP Financials Documents ... Fill the Offsetting Account in SAP ERP Financials Documents ........ Display Status of Offsetting Account in SAP ERP Financials Documents .................................................................................... Summary .......................................................................................

242 242 243 244 244 245 246

10.4

10.5

247 248

Post-Migration Testing ............................................................. 249 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9

Test SAP HANA-Optimized Report Transactions ............................ Test Multidimensional Reporting Capability ................................... Test Database Footprint Reduction ................................................ Test Intercompany Reconciliation .................................................. Test the New Process Redesign ...................................................... Test Closing Improvement ............................................................. Test the Universal Journal .............................................................. Execute Change Management ........................................................ Summary .......................................................................................

250 250 251 252 252 253 253 254 255

10.6

10.7

10.8

PART II New Functionality in SAP S/4HANA Finance 10 SAP Cash Management ............................................................. 259 10.1 10.2

10.3

12

Validate Prerequisites .................................................................... Setup Bank Account Master Data .................................................. 10.2.1 Banks and House Banks .................................................... 10.2.2 Migrate House Bank Accounts .......................................... 10.2.3 Upload and Download Bank Accounts .............................. Define the Payment Approval Process ........................................... 10.3.1 Basic Setting for Approval ................................................

261 262 262 264 265 266 267

10.9

Rule Maintenance ............................................................ Additional Criteria for Payment Grouping ......................... Mark Rules for Automatic Payment .................................. Specify the Signature Method for Approval Using a Simple Signature .............................................................. 10.3.6 Enable Signatory Control .................................................. 10.3.7 Specify Settings for the Bank Statement Monitor .............. Enable SAP Business Workflow for Bank Account Management ..... 10.4.1 Maintain Event Type Linkage ........................................... 10.4.2 Define and Maintain Organizational Hierarchy ................. 10.4.3 Define Responsibilities and Assign Users .......................... 10.4.4 Create Custom-Defined Workflows .................................. 10.4.5 Predefined Workflows ...................................................... Create Cash Pools for Cash Concentration ..................................... 10.5.1 Define Clearing Accounts for the Receiving Bank for Account Transfers ............................................................. 10.5.2 Define Clearing Accounts for Cross-Country Bank Account Transfers ............................................................. 10.5.3 Define Account Determination ......................................... 10.5.4 Check Account Determination .......................................... Manage Cash Operations ............................................................... 10.6.1 Define and Assign Flow Types .......................................... 10.6.2 Define Liquidity Items and Hierarchies ............................. 10.6.3 Define Planning Levels and Groups .................................. Load Data to One Exposure from Operations ................................ 10.7.1 Integration with Source Applications ................................ 10.7.2 Integration with Remote Systems ..................................... Set Up Cash Management Transaction Data .................................. 10.8.1 Activate Individual Source Applications ............................ 10.8.2 Activate Multiple Source Applications .............................. 10.8.3 Rebuild Planning Levels, Groups, and Dates in Accounting Documents .................................................... 10.8.4 Insert House Bank and House Bank Account Data to Accounting Documents .................................................... 10.8.5 Rebuild Liquidity Items in Accounting Documents ........... 10.8.6 Rebuild Flow Types in Accounting Documents ................. 10.8.7 Load Transaction Data into One Exposure from Operations Hub ............................................................... Set Up SAP Liquidity Management ................................................ 10.9.1 Install and Configure SAP BusinessObjects Business Intelligence Content .........................................................

268 269 270 271 272 273 274 274 276 276 281 281 285 286 287 288 288 289 290 300 304 308 308 309 310 311 312 313 314 315 316 316 318 318

13

Contents

Contents

Activate SAP BusinessObjects Business Intelligence Content .......................................................................... 10.9.3 Install Template for Cash Flow Analysis ........................... 10.9.4 Generate a Planning View ............................................... 10.9.5 Activate SAP BPC Content .............................................. 10.9.6 Install SAP BPC Content ................................................. 10.10 Set Up Liquidity Planning .............................................................. 10.10.1 Specify an SAP BPC Configuration Set ............................. 10.10.2 Create Planning Units ..................................................... 10.10.3 Activate Planning Unit Hierarchy .................................... 10.10.4 Currency Conversion Rules ............................................. 10.10.5 Reference Data Sources .................................................. 10.10.6 Exclude Liquidity Items Representing Balance Values ...... 10.10.7 Liquidity Planning Types ................................................. 10.11 Summary .......................................................................................

11.6

10.9.2

320 321 323 324 324 327 327 328 328 330 331 331 331 332

11 SAP BPC for S/4HANA Finance ................................................. 333 11.1

11.2

11.3 11.4

11.5

14

Planning Overview and Activation ................................................. 11.1.1 Business Benefits ............................................................ 11.1.2 Applications Used by Planning ........................................ 11.1.3 Activate Business Functions for Planning ........................ Architecture .................................................................................. 11.2.1 Planning Accelerators ..................................................... 11.2.2 Data Flow Architecture ................................................... Authorizations ............................................................................... Activate Embedded SAP Business Warehouse ................................ 11.4.1 Choose SAP Business Warehouse Client .......................... 11.4.2 Check SAP Business Warehouse Client Setting ................ 11.4.3 Set the SAP Business Warehouse Client .......................... 11.4.4 Assign the Logical System Client ..................................... 11.4.5 Set SAP Business Warehouse Namespaces to Changeable ..................................................................... 11.4.6 Install the Technical SAP Business Warehouse Content ... 11.4.7 Check Installation Status and Resolve Errors ................... 11.4.8 Check Planning Content Activation ................................. Activate the SAP BusinessObjects Business Intelligence Content Bundle ............................................................................. 11.5.1 Activate the DataSources ................................................ 11.5.2 Activate the Content Bundle ...........................................

334 334 337 338 338 339 340 341 345 345 345 347 348

Test the SAP Business Warehouse Installation ............................... 11.6.1 Set the User Parameter ..................................................... 11.6.2 Test the Planning Query Installation ................................. 11.7 Activate Services and Test Planning Applications ........................... 11.7.1 Check General Settings for Web Dynpro ........................... 11.7.2 Run Report RSICF_SERVICE_ACTIVATION ....................... 11.7.3 Activate Services for the Planning Applications ................. 11.7.4 Test the New Planning Application ................................... 11.8 Planning Modeler .......................................................................... 11.9 SAP BusinessObjects Analysis for Microsoft Office ......................... 11.10 Summary .......................................................................................

363 364 364 366 367 367 368 369 371 373 378

12 SAP Fiori Applications ............................................................... 379 12.1 12.2 12.3 12.4

12.5

12.6

12.7 351 352 353 355 12.8

SAP Fiori Project Phases ................................................................ Architecture .................................................................................. Configure SAP Fiori ....................................................................... Install SAP Fiori Apps .................................................................... 12.4.1 Transaction and Fact Sheet Apps ...................................... 12.4.2 Analytical Apps ................................................................ SAP Fiori Launchpad ...................................................................... 12.5.1 Frontend User Screen ....................................................... 12.5.2 Backend Configuration Screen .......................................... 12.5.3 SAP Smart Business Key Performance Indicators ............... SAP Fiori Application and Roles ..................................................... 12.6.1 General Ledger Accountant .............................................. 12.6.2 Accounts Payable Accountant .......................................... 12.6.3 Accounts Receivable Accountant ...................................... 12.6.4 Controller ......................................................................... 12.6.5 Cash Manager .................................................................. 12.6.6 Cost Manager ................................................................... SAP Smart Business Application and Roles ..................................... 12.7.1 SAP Smart Business for Accounts Payable ......................... 12.7.2 SAP Smart Business for Accounts Receivable .................... 12.7.3 SAP Smart Business for Chief Financial Officers ................. 12.7.4 SAP Smart Business for SAP Cash Management ................ Summary .......................................................................................

380 381 383 386 386 387 387 388 390 392 394 394 397 399 401 405 408 409 409 411 412 413 414

356 357 358

15

Contents

Contents

PART III Impact of SAP S/4HANA Finance

15 Impact on Controlling ............................................................... 453

13 Impact on SAP General Ledger Accounting and Related Areas ............................................................................ 417 13.1 13.2 13.3

13.4 13.5 13.6 13.7

Architectural Impact ...................................................................... Functionality Impact ...................................................................... Configuration Impact ..................................................................... 13.3.1 Copy Company Code ........................................................ 13.3.2 Consistency Check ............................................................ 13.3.3 Document Summarization ................................................ 13.3.4 Universal Journal Entry Organization ................................ 13.3.5 Ledger Configuration ........................................................ 13.3.6 Document Types and Numbering ..................................... 13.3.7 Document Posting ............................................................ 13.3.8 Integration of SAP ERP Financials and Controlling ............ 13.3.9 Define Ledger for the Controlling Version ........................ Customer and Vendor Master Data ................................................ Credit Management Impact ........................................................... SAP HANA Views in SAP S/4HANA Finance ................................... Summary .......................................................................................

417 424 426 426 427 427 427 428 431 431 432 434 434 435 436 437

15.1

15.2

14 Impact on New Asset Accounting ............................................. 439 14.1 14.2

14.3

14.4 14.5 14.6

16

Architectural Impact ...................................................................... Functionality Impact ...................................................................... 14.2.1 General Functionality Changes ......................................... 14.2.2 Changes in Transaction Codes .......................................... 14.2.3 Table Changes .................................................................. Configuration Impact ..................................................................... 14.3.1 Define How Depreciation Areas Post to the SAP General Ledger .......................................................... 14.3.2 Specify Transfer of Acquisition and Production Cost Values ...................................................................... 14.3.3 Specify Transfer of Depreciation Terms ............................. 14.3.4 Activate New Asset Accounting ........................................ 14.3.5 Technical Clearing Account for Integrated Asset Acquisition ....................................................................... Closing Process Impact .................................................................. SAP HANA Views in SAP S/4HANA Finance ................................... Summary .......................................................................................

439 440 440 445 446 447 447 447 448 449 449 450 451 451

15.3

Functionality Impact ...................................................................... 15.1.1 Cost Elements ................................................................. 15.1.2 Allocations ..................................................................... 15.1.3 Currencies ...................................................................... 15.1.4 Integration of SAP ERP Financials and Controlling .......... 15.1.5 Document Numbers in Controlling ................................. 15.1.6 SAP Material Ledger ....................................................... 15.1.7 Transfer Pricing ............................................................... 15.1.8 General Cost Objects and Cost Object Hierarchies .......... 15.1.9 Changes in Transaction Codes ......................................... Configuration Impact ..................................................................... 15.2.1 Integration of Controlling with SAP ERP Financials ......... 15.2.2 Cost Element as an SAP General Ledger Account ............ 15.2.3 Ledger for Controlling ..................................................... 15.2.4 Rule for Posting in Controlling ........................................ 15.2.5 Ledger View in Customizing ........................................... 15.2.6 SAP General Ledger Planning .......................................... 15.2.7 Cash Journal View .......................................................... 15.2.8 Report Hierarchies Added ............................................... 15.2.9 Reference and Simulation Costing View .......................... 15.2.10 Assign Currencies to SAP Material Ledger ....................... 15.2.11 Assign SAP Material Ledger Type to Valuation Area ........ 15.2.12 Cost of Goods Sold Posting ............................................. Summary .......................................................................................

453 454 454 455 456 456 457 459 459 460 461 461 462 463 463 464 465 465 466 467 468 468 469 469

16 Impact on Cost Center Accounting and Profit Center Accounting ........................................................... 471 16.1 16.2 16.3 16.4 16.5

Architectural Impact ...................................................................... Functionality Impact ...................................................................... SAP HANA Views in SAP S/4HANA Finance .................................. Web Dynpro Reports ..................................................................... Summary .......................................................................................

471 473 476 476 477

17 Impact on Profitability Analysis ................................................ 479 17.1 17.2

Architectural Impact ...................................................................... 480 Functionality Impact ...................................................................... 481

17

Contents

17.3

17.4

Configuration Impact ..................................................................... 17.3.1 Define Profitability Segment Characteristics ...................... 17.3.2 SAP HANA Integration ..................................................... 17.3.3 Segment-Level Characteristics for Distributed Profitability Analysis ........................................................ Summary .......................................................................................

482 482 483 484 484

18 Impact on Period-End Closing .................................................. 485 18.1 18.2 18.3 18.4 18.5

Architectural Impact ...................................................................... Functionality Impact ...................................................................... Security Impact .............................................................................. SAP HANA Views .......................................................................... Summary .......................................................................................

485 486 488 489 490

19 Impact on SAP Cash Management and Bank Account Management ...................................................... 491 19.1 19.2 19.3 19.4 19.5

A B

Introduction of SAP Business Client ............................................... Functionality Impact ...................................................................... Security Impact .............................................................................. Configuration Impact ..................................................................... Summary .......................................................................................

491 493 495 496 497

Project Plan for Migrating to SAP S/4HANA Finance ................................ 499 The Author .............................................................................................. 525

Index ................................................................................................................ 527

18

Index A

B

ABAP, 61, 124, 387 backend server, 383 frontend server, 382 ABAP Development Tools (ADT), 115, 123 ABAP Workbench, 342 Account assignment, 190 Account determination, 140, 288 Accounting, 30 Accounting principle, 135, 159, 161 Accounting principle document, 441 Accounts Payable (AP), 36, 489 Accounts payable accountant, 397 Accounts Payable Manager app, 410 Accounts Receivable (AR), 36 Accounts receivable accountant, 399 Acquisition and production cost (APC), 64, 159, 161, 450 transaction, 157 value, 157 Activation log, 363 Activity-based costing (ABC), 52 Administrator’s Guide, 109 Adopt authorizations, 192 Adopt fiscal year variant, 129 Allocation, 454 Analytic view, 125 Appendix ledger, 131, 422–423, 429 Application index, 244 transfer, 243 Application Linking and Embedding (ALE), 62 Approval pattern, 177–179 Architecture, 34 Asset, 439 Asset Accounting, 145 Asset acquisition, 441 Asset retirement, 151 Asset value, 157 Attribute view, 125 Authorization, 196 Authorization profile, 193, 197 Authorization value, 196 Automatic payment, 270

Balance carryforward, 81, 486 Balance sheet, 157 Balance sheet account, 88, 190 Balance sheet adjustment, 487 Bank account closure, 494 master data, 172–173 technical ID, 172 type, 173–174 Bank Account Management, 172, 232, 259, 266, 274, 276, 285, 491, 493 Bank account master data, 262 review, 284 Bank account number mapping, 232 Bank clearing account, 294 Bank clearing account determination, 288 Bank directory, 263 Bank master data, 496 Bank statement, 176 Bank statement monitor, 273 Bank subaccount, 294 Banking add-on, 168 Business Add-In (BAdI), 232 Business Application Programming Interface (BAPI), 61 Business Configuration Sets (BC Sets), 68 Business function, 141, 338 DAAG_DATA_AGING, 243 EA-FIN, 67 FI-G/L, 62 FIN_AA_PARALLEL_VAL, 65, 153 FIN_CO_CCMGMT, 338 FIN_CO_CCPLAN, 338 FIN_CO_ORPLAN, 338 FIN_FSCM_CLM, 261 FIN_GL_CI_1, 141 FIN_GL_DISTR_SCEN_1, 62 OPS_PS_CI_1, 338 Business function/switch concept, 114 Business Object Repository, 281 Business unit, 479

527

Index

C Cash concentration, 285 Cash Journal, 465 Cash manager, 405 Cash manager role, 495 Cash Operations, 259, 289 Cash pool, 285 Cash Position, 496 Central Finance, 44 CFO, 28, 412 Change and Transport System (CTS), 341 Change management, 38, 254 Change request, number range, 172 Chart of accounts, 190 Chart of depreciation, 146–147, 154, 161, 447 migration, 146 Charts, 393 Checklist, 106 Clearing account, 286–287 Clone system, 236 Closing Cockpit, 486 Closing process, 450 Cluster table, 125 Cluster/pool table, 121 Code pushdown, 122 Company code, 92, 131, 135–136, 145, 162, 175, 426, 463 Compatibility view, 472 Compliance capabilities, 251 Compliance Management, 31 Concur, 27 Consistency check, 73, 141, 187 Consumer and Mortgage Loans (CML), 310 Content bundle, 358 Control parameter, 159 Controller, 401 Controlling, 35, 52, 105, 127, 138, 165, 338, 441, 453, 471, 489 area, 92, 132, 480 business transaction, 138 document, 204 document migration, 457 historic plan data, 339 posting, 454 transactional data, 206 version, 136

528

Index

Core Data Services (CDS) view, 115, 183, 473 Cost center, 191, 444, 473 Cost Center Accounting, 471, 474 views, 476 Cost center planning, 489 Cost center report, 476–477 Cost element, 187, 189, 339, 473 Cost manager, 408 Cost object, 110 Cost object hierarchy, 110 Cost of goods sold (COGS), 252, 469, 479 Create Manual Payment app, 398 Credit Management, 435 Currency new settings, 455 Currency conversion, 330 Custom code, 40, 42, 60 Custom Development Management Cockpit (CDMC), 123

D Data aging, 34 Data cleansing, 39 Data consistency, 73, 242 Data definition language (DDL), 183 description, 115 Data definition language statement (DDLS) views, 115 Data Dictionary, 38, 183, 348 Data migration, 37 Data model, 115 Data structure, 211, 459 Data Warehousing Workbench, 344, 372 Database footprint, 251 Database migration option (DMO), 38, 108 Database size, 55 Database table, 120 DataSource, 357 Days sales outstanding (DSO), 379 Days Sales Outstanding app, 412 Declustering, 122 Default ledger group, 139, 463 Delta CO totals, 219 Delta migration, 237 Depooling, 121

Depreciation, 85, 226 area, 64, 143, 146, 148, 155, 158–159, 447 calculation, 70 terms, 158–159, 448 Depreciation calculation program (DCP), 145 Depreciation run, 243 posting, 444 Depreciation value, 227 initial, 229 Display Customer Balances app, 400 Document migration status, 213 Document number, 201 Document number range, 83 Document posting, 431 Document splitting, 41 Document type, 137, 431 Due date, 244 Duplicate entry, 215

E EDI, 494 EHP 7, 38, 43 End-of-day statement, 176 Enhancement Package Installer (EHPI), 111 Enrich transactional data, 208 Enterprise Risk, 31 Error, 200, 206 Error log, 168 Error message, 169, 217, 230, 330, 368

F FI-CO integration, 432 FI-CO reconciliations, 31 Field FDTAG, 305 HBKID, 314 HKTID, 314 Financial close, 30, 33 Financial operations source application, 312 Fiscal year, 140 Fiscal year change, 72 Fiscal year variants for fixed assets, 441 Fixed Assets functionality, 40

Flow category, 290 Flow level, 290 Flow type, 290, 292 Function module RS_MANDT_UNIQUE_SET, 346 Functional account, 174

G G/L accountant, 394 General Availability (GA) Care program, 114 Generally accepted accounting principles (GAAP), 67 Goods receipt/invoice receipt (GR/IR), 243 Graphical calculation view, 125 Greenfield implementation, 43, 51

H HANA-tization, 120 tools, 121 Held document, 85 House bank, 314 House bank account, 171, 232

I Import and Export Bank Accounts tool, 233 Import method, 176 Income statement, 480 Index table, 42 Industry solution, 110 InfoCube, 339 InfoObject, 339, 356 InfoProvider, 339 Installation, 105 Integrated asset acquisition, 449 Intercompany reconciliation, 252, 486 International Financial Reporting Standards (IFRS), 67 Internet Communication Framework (ICF), 367 Internet Communication Manager (ICM), 367 Invoice Verification, 397, 399

529

Index

J

Index

Job, BI_TCO_ACTIVATION, 348, 353 Joint signature, 177 Joint Venture Accounting, 52 Journal entry, 457

Migration of balances, 127, 219, 221 check, 221 display status, 222 Month-end depreciation run, 440 Multidimensional reporting, 250 My Spend app, 408

K

N

Key performance indicator (KPI), 30, 379

Near Zero Downtime (NZDT), 181, 235 Net book value, 152 New Asset Accounting, 33, 40, 42, 52, 63–64, 143, 160, 226, 439, 486 activation, 449 New G/L migration, 37 Nonleading ledger, 422, 428 Nonoperating expense, 190 Nonsequential signatory pattern, 178 Nonstatistical line item, 440 Number range, 172 interval, 172

L Landscape Management Database (LMDB), 116 Leading ledger, 131–132, 136, 428, 434, 463 Lease Accounting Engine (LAE), 52, 59 Ledger comparison report, 81 Ledger group, 73, 133–135, 139, 143, 206 Liquidity Forecast, 496 Liquidity item, 300, 331 Liquidity item hierarchy, 302 Liquidity Planning, 327 Liquidity planning type, 331

M Maintenance Optimizer, 62, 108, 111 Maintenance planner, 60, 115 Manage Bank Accounts app, 407 Mapping, 184 Mapping variant, 463 Materials Management (MM), 73 Migrate Balance activity, 457 Migrate house bank accounts, 264 Migrated documents check, 210 Migration, 88, 206 cost element, 185 cost elements, 190 data, 181 data view, 184 house bank account, 232 log, 162 phases, 45

530

O Object FINS_MIG, 239 OData services, 383 Offsetting account, 140, 246 One Exposure from Operations, 303, 308 Operating account, 174 Operating concern, 165, 167–168 Operational data providers (ODP), 346 Operational entry document, 441 Optimization, 122–123 Overdraft Limit tab, 175 Overdue Payables app, 410

P P&L account, 473 Parallel accounting, 41 Parallel currency, 89, 147 Parallel ledger, 69 Parallel valuation, 147, 153 Partitioning, 182

Payment approval, 266 Payment grouping, 268 Payment request, 295 Performance expectations, 55 Performance statistics, 123 Period control, 84 Period-end closing, 83, 485 Periodic depreciation posting run, 70 Plan data, 447 Planned depreciation value, 439 Planned status, 66 Planning group, 304, 306 Planning level, 298, 304 Planning Modeler, 371–372 Planning query, 364 Planning unit, 328 Planning unit hierarchy, 328–329 Planning view, 323 Post General Journal Entries app, 396 Post-migration activity, 241 Preparation, 51 Prima nota, 422 Primary cost, 190 Primary cost element, 187, 462 Prior period, 89 Product Cost Controlling (CO-PC), 110 Product System Editor, 116 Production variance, 480 Profit & loss, 453 Profit Center Accounting, 52, 471, 474 Profit center planning, 473 Profit Centers – Actuals app, 404 Profitability Analysis (CO-PA), 57, 165, 243, 249, 454 account-based, 166, 479 costing-based, 479 distributed, 484 Profitability characteristic, 480 Profitability segment, 165, 213 Program FAA_DEPRECIATION_CALCULATE, 227 FAA_DEPRECIATION_POST, 70 FCO_ADD_COPA_FIELD_TO_ACDOCA, 481 FINS_MIGRATION_START, 237 General Ledger Line Items List, 94 RAABST02, 77 RAGITT_ALV01, 97

Program (Cont.) RAHAFA_ALV01, 97 RASFIN_MIGR_PRECHECK, 145 RFAGL_SWAP_IMG_NEW, 128 RFAGL_SWAP_MENU_NEW, 129 RFBELJ00, 96 RFDAUB00, 100 RFDEPL00, 100 RFDUML00, 100 RFINDEX_NACC, 74 RFKEPL00, 98 RFKUML00, 98 RFTMPBLD, 85 RGUCOMP4, 81, 83 RKKBSELL, 94 RM07MBST, 79 RM07MMFI, 79 RMMMPERI, 84 Project plan, 499

Q Questionnaire, 53

R Read access, 185 Real Estate Management, 52 Real-time integration, 131 Reconciliation, 93, 206, 234 ledgers, 81 Reconciliation reports, 242 Reference data source, 331 Relational database management system (RDBMS), 38 Remote Function Call, 361, 385 Report, 242, 476 FINS_MIGRATION_STATUS, 185 FQME_BANK_CASH_BAL_IMPORT, 309 PFCG_TIME_DEPENDENCY, 198 RSICF_SERVICE_ACTIVATION, 367 Report hierarchy, 466 Reporting, 440 Representative ledger, 139 Restrictions, 51

531

Index

Role, 194 FUCN_GL_ACCOUNTANT, 192 SAP_BW_BI_ADMINISTRATOR, 355 SAP_SFIN_ACC_PLANNING, 339 SAP_SFIN_CASH_MANAGER, 261 Roll up values, 486 Root cause, 206 Rule FCLM_CASHMGR, 281 FCLM_CASHSYSCOLL, 282 FCLM_REVWOR, 282

S SAP Add-On Installation Tool (SAINT), 108 SAP Ariba Network, 27 SAP Bank Communication Management, 266 SAP BPC for S/4HANA Finance, 58, 324, 336– 337, 474, 493 SAP BPC web client, 337 SAP Business Client, 117, 337, 465, 474, 491– 492 SAP Business Explorer, 344 SAP Business Suite, 36, 39, 65 SAP Business Suite on SAP HANA, 379 SAP Business Warehouse, 54, 165–166, 328, 335 client, 345, 347 embedded, 345 namespace, 351 SAP Business Workflow, 174 SAP BusinessObjects BI, 318, 340, 382 SAP BusinessObjects Business Intelligence Content Activation Workbench, 359 SAP BusinessObjects Business Intelligence Content bundle, 356 SAP BusinessObjects Design Studio, 406 SAP Cash and Liquidity Management, 58, 232, 491 SAP Cash Management, 33, 40, 52, 110, 179, 259, 304, 312, 413, 491, 496 SAP Code Inspector (SCI), 123–124 SAP DataSource, 343 SAP ERP, 53–54 SAP ERP 6.0, 36 SAP ERP 6.0 EHP 7, 107

532

Index

SAP ERP Financials (FI), 35, 70, 105, 110, 114, 128–129, 147, 165, 241, 250, 380, 454 SAP ERP Financials Extension (EA-FIN), 145 SAP EWM, 112 SAP Fiori, 27, 56, 106, 337, 377, 379, 486 analytical app, 379 app, 28, 496 apps, 386 architecture, 381 dashboard for Cash Manager, 407 Fact sheet app, 379 project phases, 380 Transactional app, 379 SAP Fiori launchpad, 382, 387 SAP Fiori UI5, 395, 397, 399, 402, 406 SAP Gateway, 113, 117, 382, 384 SAP General Ledger, 34–35, 40–41, 52, 73, 127, 147, 156, 339, 454, 480 account, 187, 189, 252, 454 account mapping, 456 allocation, 217 Customizing, 127, 130 document, 203 summary table, 217 SAP General Ledger Accounting, 36, 61, 73, 140–141, 157, 226, 417, 439–440, 465, 471, 479, 489 migration, 459 SAP GUI, 56, 334 SAP HANA, 29, 56, 106, 121, 377, 483 artifact, 123 database, 27 database migration, 44 integration, 483 modeling, 125 view, 436, 451 SAP HANA application lifecycle management (HALM), 109, 120 SAP HANA Cloud Platform, 27 SAP HANA Extended Application Services Advanced, 382 SAP HANA Lifecycle Manager (HLM), 109 SAP HANA Live, 28, 120 packages, 109 SAP HANA view, 489 SAP HCM Organizational Management, 198 SAP Landscape Transformation Replication Server, 106

SAP Liquidity Management, 260, 318 SAP List Viewer (ALV), 124 SAP Material Ledger, 58, 457, 459, 468 SAP Mobile Platform, 114, 381 SAP NetWeaver, 108, 114, 337 SAP NetWeaver 7.40, 107 SAP NetWeaver ABAP, 38 SAP NetWeaver Enterprise Search, 386 SAP Process Integration (SAP PI), 383 SAP reference IMG structure, 128 SAP S/4HANA, 27 SAP S/4HANA Finance, 36, 64, 143, 494 SAP Smart Business, 57, 109, 113, 409, 411 for cash management, 491 KPIs, 392 SAP Smart Business mobile UI, 34 SAP Treasury and Risk Management, 31, 287 SAP Web Dispatcher, 382, 386 Scale-out, 39 Scale-up, 39 Secondary cost, 190, 485 Secondary cost element, 454, 473 Secure Sockets Layer (SSL), 385 Segment reporting, 41 Segment-level characteristics, 484 Sensitive field, 174 Sequential approval pattern, 178 Server group, 444 Signatories tab, 175 Signatory approval, 271 Signatory control, 176 Signatory group, 176–177 Signature method, 271 Single signature, 177 Single Sign-On (SSO), 387 Sizing, 62 Software Update Manager, 38, 60, 62, 108, 116 Sorting behavior, 122 Source ledger, 140 SQL, 61 SQL Monitor, 124 SQL Performance Tuning Worklist, 124 Stack calculation, 107 Standard ledger, 131 Statistical data, 447 Subledger, 79, 86, 221 reconciliation, 76

SUM with DMO, 108 Support Package Manager (SPAM), 111 Switch Framework, 342 Switch PARALLEL_VAL, 153 System landscape, 53 System review, 53

T Table, 446, 475 ACDOCA, 35, 60, 183, 186, 214, 418, 456 ANLC, 439 ANLP, 439 BKPF, 417 BNKA, 262 BSAD_BCK, 202 BSAS_BCK, 202 BSEG, 61, 214, 427 BSID_BCK, 201 BSIS_BCK, 201 FAAT_DOC_IT, 439 FAAT_PLAN_VALUES, 439–440 FAGLFLEXA, 419, 421 FAGLFLEXT, 419 FAGLFLEXT_BCK, 223, 225, 419 FCLM_BAM_ACLINK2, 264 FCLM_BAM_AMD, 496 FDES, 310 FQM_FLOW, 298, 310 FQMI_FLOW_CAT, 290 HRRP_DIRECTORY, 467 HRRP_NODE, 467 MLHD, 422 MLIT, 422 RSADMINA, 345 T012K, 264 Table index, 73 Table join, 39 Technical clearing account, 149, 449 Transaction, 124, 195, 445, 460, 474, 486 AB01, 443 ABLDT, 443 AFAB, 78 AFAR, 229 AJAB, 71, 78 AJRW, 72, 78, 87 AS91, 443, 451

533

Index

Transaction (Cont.) ASKB, 78 AW01, 70 AW01_AFAR, 70 BAUP, 262 BSANLY_BI_ACTIVATION, 357 CODE_SCANNER, 121 F.07, 87 F111, 287 FAGLF03, 76 FAGLGVTR, 81, 86, 424 FBICA3, 252 FBICS3, 252 FBL3H, 474 FCLOCO, 488 FCLOCOC, 488 FF7A, 496 FI01, 262 FI12_HBANK, 264, 496 FINS_CUST_CONS_CHK, 427 FINS_MASS_DATA_MASTER, 212, 219 FINS_MASS_DATA_MONITOR, 213 FINS_MIG_DAA, 191 FINS_MIG_DUE, 244 FINS_MIG_GCM, 189 FINS_MIG_GKONT, 246 FINS_MIG_INIT_COLD, 243 FINS_MIG_LEDGER_CUST, 130 FINS_MIG_MONITOR, 209 FINS_MIG_MONITOR_AFA, 228 FINS_MIG_MONITOR_CLD, 244 FINS_MIG_MONITOR_DAA, 192 FINS_MIG_MONITOR_DUE, 245 FINS_MIG_MONITOR_GCM, 190 FINS_MIG_MONITOR_GKO, 247 FINS_MIG_MONITOR_RC0, 200 FINS_MIG_MONITOR_RC1, 204 FINS_MIG_MONITOR_RC2, 211 FINS_MIG_MONITOR_RC3, 216 FINS_MIG_MONITOR_RC4, 222 FINS_MIG_MONITOR_RC5, 229 FINS_MIG_STATUS, 238 FINS_MIGRATION, 208 FINS_RECON_RC0, 199 FINS_RECON_RC1, 203 FINS_RECON_RC3, 215 FINS_RECON_RC5, 229 FLQC0, 303

534

Index

Transaction (Cont.) FLQC15, 303 FLQQA1, 303 FLQQA5, 303 for reports, 250 FQM_ACTIVATE, 312 FQM_INITIALIZE, 316 FQM_UPD_FLOW_TYPE, 316 FQM_UPD_LITEM, 315 FQM21, 297, 309 FS00, 150, 189, 193, 462 GCA9, 218 GCAC, 81, 234–235 GR55, 242 KA01, 462 KA06, 462 KB11, 420 KB11 and KB41, 457 KB41, 420 KEA0, 419 KEA5, 419 KP06, 474 LMDB, 111 MR21, 422 NWBC, 233, 265, 491 OBH2, 83 OXK3, 419 PFCG, 192, 385 PPOCE, 276 PPOMW, 276 RSA1, 328, 353, 356 RSA5, 357 RSD1, 355 RSOR, 359 RSPLAN, 371 RSRTS_ACTIVATE_R3IS, 319 RSTCO_ADMIN, 353 S_ALR_87012993, 102 S_ALR_87013611, 101 SA38, 85, 128, 185 SAT, 123 SFW5, 65, 68–69 SICF, 368 SLG1, 248, 265 SM30, 342 SM37, 248 SMSY, 113 SPDD/SPAU, 114

Transaction (Cont.) SPRO, 66, 348, 358 SQLM, 123 STC01, 383–384 SU01, 385 SWDD, 281 SWETYPV, 274 SWLT, 123 Transaction data, 141, 310 Transaction type, 152 Transactional data, 198–200, 203 Transfer rule, 157, 447 Transport Layer Security, 382

U Unicode, 54 Universal Journal, 29, 31–32, 34, 181, 185, 253–254, 419, 454, 457, 485 User experience (UX), 27, 335, 379 User interface (UI), 28, 333 User screen, 388

V Valuating part, 449 Valuation, 89 Valuation area, 468–469 Value transfer, 147 Value type, 473

W Web Dynpro, 233, 367, 395, 402, 406 report, 476–477 Work in Process (WIP), 252 Workflow, 274 custom, 281 Workflow template, 282 Workflow, report, interface, conversion, enhancement, form (WRICEF), 57, 254

Y Year-end closing, 39, 84

535

First-hand knowledge.

Anup Maheshwari is an SAP S/4HANA Finance practice leader and project management professional with more than 18 years of IT and business-consulting experience in managing and delivering complex SAP and enterprise transformation projects focused on finance efficiency, productivity, and profitability. Anup has led the design, migration, and implementation teams in some of the first global deployments of SAP S/4HANA Finance. He has successfully led and managed numerous full lifecycle and global rollout SAP implementation projects across North America, Europe, and Asia Pacific. Anup’s SAP functional experience includes SAP S/4HANA Finance, Collaborative Finance Operations, new SAP Cash Management, SAP BPC for S/4HANA Finance, Financial Supply Chain Management, new General Ledger, Accounts Payable, Accounts Receivable, Asset Accounting, Controlling, and Travel Management. Anup has master’s degrees in business administration and project management from The George Washington University, Washington, DC. He is a Stanford Certified Project Manager and a PMI-certified Project Management Professional (PMP). Anup is a Chartered Financial Analyst, an SAP Certified Application Associate for SAP Simple Finance On-Premise Edition 1503, and an SAP Certified Application Consultant for Accounting.

Anup Maheshwari

Implementing SAP S/4HANA Finance 535 Pages, 2016, $79.95 ISBN 978-1-4932-1350-4

www.sap-press.com/4045

We hope you have enjoyed this reading sample. You may recommend or pass it on to others, but only in its entirety, including all pages. This reading sample and all its parts are protected by copyright law. All usage and exploitation rights are reserved by the author and the publisher.