Transcript

Reading SampleThese sample chapters describe the customizing steps you must per-form for the new SAP General Ledger and the new Asset Accounting prior to your migration to SAP S/4HANA Finance.

Anup Maheshwari

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

www.sap-press.com/4045

First-hand knowledge.

“Customizing for the SAP General Ledger”

“Customizing for the New Asset Accounting”

Contents

Index

The Author

127

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 formigration to the new SAP General Ledger (new G/L) as part of the overall SAPS/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 � Prepa-

rations and Migration of Customizing � Preparations and Migration of Cus-

tomizing for the General Ledger, as shown in Figure 3.1.

Customizing for the SAP General Ledger3

128

Figure 3.1 Customizing the General Ledger

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

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 menupath that is associated with it by following these steps:

1. Select Transaction SA38.

2. Enter the Program RFAGL_SWAP_IMG_NEW.

3. Select Execute.

Check and Adopt Fiscal Year Variants 3.2

129

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 (Figure3.3), and then select Execute so that the relevant structure is visible.

Figure 3.3 Activating the New Menu

3.2 Check and Adopt Fiscal Year Variants

The migration to the Universal Journal requires the same fiscal year variant to beused in both FI and CO.

In this activity, you compare the fiscal year variants between controlling areasand their assigned company codes. If an inconsistency exists in the fiscal yearvariant configuration, a report is created with a proposal for the required config-uration 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 ofthe transaction data can be started. The report lists all CO areas and companycodes that need to be changed, as well as the number of the posting periods andspecial periods.

Customizing for the SAP General Ledger3

130

The Det. FYV for CoAr (determined fiscal year variant for controlling area) andDet. FYV for CoCd (determined fiscal year variant for company code) columnsprovide the proposal for the configuration change. The report must be executedusing Transaction FINS_MIG_FYV for all relevant controlling areas.

If no changes are required, the information window shown in Figure 3.4 appears.

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 Trans-action FINS_MIG_LEDGER_CUST, as shown in Figure 3.5.

Figure 3.5 Migrating General Ledger Customizing

Define Settings for the Journal Entry Ledger 3.4

131

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 Define Settings for the Journal Entry Ledger

In this activity, you define ledgers, which you use in accounting. Only one ledgercan be defined as the leading ledger (the standard leading ledger is 0L). There aretwo types of ledgers:

� Standard ledger The standard ledger consists of all journal entries related to any business trans-actions.

� Appendix ledgerIntroduced in SAP S/4HANA Finance, an appendix ledger is assigned to a stan-dard ledger from where it inherits all the journal entry postings. Any specificadjustments required to be posted only to the appendix ledger aren’t dupli-cated in the standard ledger. Thus, the appendix ledger takes the base valuesfrom the standard ledger and then combines the specific appendix ledger post-ings. This prevents multiple data footprints and significantly reduces dataredundancy because the journal entries don’t need to be posted to both theappendix and the standard ledger.

You also need to assign company codes to ledgers and define currency settingsand fiscal year variants. The step-by-step configuration settings are shown in Fig-ure 3.6 through Figure 3.9.

The following requirements must be met before performing this Customizingactivity:

� Company codes are configured with currency, fiscal year variants, and openperiod variants.

Customizing for the SAP General Ledger3

132

� 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.

� The leading ledger is assigned to all company codes.

In this Customizing setting, Ledger 0L needs to be assigned as the Leading Led-

ger (Figure 3.6). Here, you also need to create all the other standard (nonleading)ledgers and extension (appendix) ledgers required for parallel accounting for theorganization.

Figure 3.6 Standard Ledger Customizing

In this Customizing setting, all company codes need to be assigned to the leadingledger 0L. Here, you also need to configure company code assignments to otherledgers along with currency settings, fiscal year variants, and open period vari-ants for nonleading ledgers. If you want to do parallel accounting using G/Laccounts instead of various ledgers, you need to select the Parallel GL Accts

checkbox (Figure 3.7).

Figure 3.7 Ledger Assignment to Company Code

Define Ledger Groups 3.5

133

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

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

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 GeneralLedger Accounting (New).

3.5 Define Ledger Groups

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

Customizing for the SAP General Ledger3

134

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

Figure 3.10 Customizing the Ledger Group

When a ledger is created in the system, a ledger group with the same name isautomatically created whereby data to an individual ledger can be posted andaccessed by merely entering the ledger group. Some of the properties of ledgergroups include the following:

� You can rename the ledger group that was created automatically when creatingthe ledger.

� You can create ledger groups that enable you to bring several ledgers togetherfor joint processing in a function.

� If a ledger group isn’t specified while posting an entry, the system by defaultposts to all the ledgers. Thus, creating ledger groups for all ledgers isn’t re-quired.

Within the ledger group, you need to assign and check one ledger as the repre-sentative ledger as shown in Figure 3.11. The best practice is to have the leadingledger 0L as your representative ledger. Posting to all the ledgers is determined

Assign the Accounting Principle to the Ledger Group 3.6

135

by the posting period of the representative ledger. If the posting period of therepresentative ledger is open while the posting period of the nonrepresentativeledger is closed, the system still posts to all the ledgers. The criteria for a repre-sentative ledger are listed here:

� Any ledger can be assigned as a representative ledger if all the ledgers in thegroup have a fiscal year variant that is different from the one assigned to thecompany code.

� If a ledger in the group has the same fiscal year variant as assigned to the com-pany code, that ledger must be assigned as the representative ledger within theledger group.

Thus, you may not be able to use the same ledger group for all the active companycodes within the organization.

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 theaccounting principle for the organizational legal and statutory reporting require-ments. 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 accountingprinciple to the ledger group, as shown in Figure 3.13.

Customizing for the SAP General Ledger3

136

Figure 3.12 Assign Accounting Principle to Ledger Groups

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 postedby assigning Version 0 to a ledger. The version is assigned at the company codelevel, 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 companycodes 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 con-trolling area.

Define Document Types for Postings in Controlling 3.8

137

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 thereposting or allocation of primary costs. For document types used in CO, you mustselect the G/L account indicator under the Account types allowed section.

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

Figure 3.15 Document Type Properties for CO

Customizing for the SAP General Ledger3

138

3.9 Define Document Type Mapping Variants for Controlling Business Transactions

In this activity, you define a variant for mapping CO business transactions to doc-ument types. You must conduct and define this mapping exercise for all CO actualposting business transactions.

A default mapping variant is generated during the Customizing activity for themigration of the ledger where all CO business transactions are mapped to thedocument type associated with the CO-FI real-time integration, as shown in Fig-ure 3.16.

Figure 3.16 Variant for Mapping the CO Transaction to Document Types

Figure 3.17 depicts how the CO business transactions are assigned to the docu-ment type.

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 inwhich the user interfaces don’t allow any document type or ledger group as an

Check and Define Default Values for Postings in Controlling 3.10

139

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

Figure 3.18 Default Values for Postings in CO

To define the ledger group and assign the ledgers (Figure 3.19), you use the Cus-tomizing menu path, Financial Accounting (New) � Financial Accounting

Global Settings (New) � Ledgers � Ledger � Define Ledger Group.

Figure 3.19 Ledger Group Assignment

Here, you first create ledger groups as required, provide a description to each ofthe 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 docu-ments get posted only to those ledgers that are in that group.

The system assigns a representative ledger within a group that has more than oneledger. The representative ledger is used to determine the posting period and tocheck if the period is open for posting. If the representative ledger is open, thesystem still posts to all the ledgers in the group, even though the posting periodfor the other ledgers in the group might be closed.

Customizing for the SAP General Ledger3

140

3.11 Define the Offsetting Account Determination Type

In this activity, you define the offsetting account determination for all applica-tions. This activity needs to be executed before the migration to SAP S/4HANAFinance.

You should choose the As case 2, but including line items generated automat-

ically option, as shown in Figure 3.20, because this option always displays theoffsetting account with the highest amount along with the line items that are gen-erated automatically.

Figure 3.20 Define Offsetting Account Determination

3.12 Define the Source Ledger for Migration of Balances

In this activity, you define the source ledger and the source database table of thebalances for SAP General Ledger Accounting from which you want to transfer theopening 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 fis-cal years)

Organizations using the new G/L can specify one entry per ledger, where thesource and target ledger are equal. In the example in Figure 3.21, 0L is defined asboth the source and target ledger for CoCd 1000 for the purpose of migration ofbalances.

Activate Business Functions 3.14

141

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 Trans-action FINS_CUST_CONS_CHK. This check must be executed before migration oftransaction 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.22 Consistency Check of General Ledger Settings

3.14 Activate Business Functions

In this activity, you need to activate the business functions that are necessary formigrating to SAP S/4HANA Finance. You have to activate the following businessfunctions in the Customizing system using Transaction SFW5 and then importthem into the production system:

� FIN_GL_CI_1 This new SAP General Ledger Accounting business function helps to optimizethe processes related to parallel accounting as well as planning and reportingbased on profit centers.

� FIN_GL_CI_2 This new SAP General Ledger Accounting business function enhances the pro-cesses for parallel accounting by enabling its integration with CO.

Customizing for the SAP General Ledger3

142

� FIN_GL_CI_3 This business function helps to improve the processes related to periodic tasksand optimize the usage of archive functionality. Analysis of actual/actual com-parison between the ledgers can be done while conducting the financial state-ment analysis. This business function also plays an important role in managingthe assigned numbers when assets are transferred.

All three business functions activate functionality in G/L, which is mandatory forthe 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 SAPS/4HANA Finance to accommodate the required changes. This requires checkingthe consistency of the fiscal year variants between company code and controllingarea, defining the ledgers and their assignment to the accounting principle, set-ting up the postings in CO, and activating any missing business functions.

You now understand the prerequisites, preparations, and migration requirementsrelated to the new SAP General Ledger Accounting, and you can perform the Cus-tomizing steps as well. Let’s now move on to Chapter 4, where we’ll discuss theCustomizing for the new Asset Accounting.

143

Chapter 4

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

4 Customizing for the New Asset Accounting

Prior to the migration, you need to customize the new Asset Accounting (new FI-AA) 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 toperform for migration to the new FI-AA are covered in this chapter.

The SAP S/4HANA Finance migration includes performing prechecks for usingthe new FI-AA, checking accounting principle and ledger group settings, assign-ing the accounting principle to the ledger group, making any additional manualsettings in Customizing for new FI-AA, and checking the prerequisites for activat-ing the new FI-AA. Other tasks you must perform include determining andmigrating active charts of depreciation, changing definitions of depreciationareas, defining transfer rules for the posting values and depreciation terms of adepreciation area, checking the currency type of depreciation areas, and finallyactivating the Customizing switch for new FI-AA. All of the major steps, alongwith any additional details, are shown in Figure 4.1.

When you install SAP S/4HANA Finance, the system shows the Customizingstructure for new FI-AA in the SAP Reference IMG, as shown in Figure 4.1. Bydefault, it hides the Customizing structure for classic FI-AA.

Customizing for the New Asset Accounting4

144

Figure 4.1 Customizing New Asset Accounting

No postings to FI-AA are allowed until the migration of Customizing and trans-action data is complete. After the migration activities are complete, and the newFI-AA has been activated, you can’t revert to classic FI-AA. New FI-AA needs to beconfigured in preparation for migrating to SAP S/4HANA Finance. Some of thetasks will include setting the new FI-AA activation status to In Preparation, cre-ating a new ledger group for local valuation, assigning the ledger group to thelocal generally accepted accounting principles (GAAP), and assigning all the activecompany codes to the chart of depreciation. You’ll also be responsible for config-uring and assigning the accounting principle to the depreciation areas, setting upaccounts assigned to the local accounting principle as asset reconciliationaccounts, creating and assigning the technical clearing account, specifying alter-native document types for accounting principle-specific document postings, anddefining the depreciation area for quantity updates.

Install SAP S/4HANA Finance with New Asset Accounting 4.2

145

4.1 Prerequisites

Before you install SAP S/4HANA Finance, you have to ensure that the prerequisitesare met by using Program RASFIN_MIGR_PRECHECK for preliminary checks. Youhave to import this program to your system by means of SAP Note 1939592 beforeyou 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 itprovides the depreciation calculation program (DCP), which is used for the newdepreciation 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 Gen-eral Ledger Accounting and the depreciation areas of the leading valuation inFI-AA are the same.

The company codes that are assigned to the same chart of depreciation shouldhave the same number and type of parallel currencies used in SAP General LedgerAccounting.

Make sure that the period-end closing has been performed along with the recon-ciliation of the asset subsidiary ledger with the SAP General Ledger (G/L). If youhappen to install SAP S/4HANA Finance at the close of the fiscal year, you shouldalso 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 topost any transactions in FI-AA. If you were already using classic FI-AA, then youonly have to migrate your charts of depreciation and check and possibly add todelta Customizing. If you weren’t already using FI-AA and now want to use it inthe 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 thenew SAP General Ledger Accounting before you can customize the new FI-AA.

Customizing for the New Asset Accounting4

146

4.3 Migrate Charts of Depreciation

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

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 migra-tion because the migration program doesn’t recognize the starting situationdefined in your system.

� Your charts of depreciation are assigned to a deactivated company code, andbecause the deactivated company code’s data haven’t been archived yet, thecompany code must be migrated with the document migration. This chart ofdepreciation should therefore be migrated manually.

This is possible at any time by making the following settings in Customizing fornew FI-AA:

� Assignment of accounting principles and ledger groups to depreciation areas:Asset Accounting (New) � Valuation � Depreciation Areas � Define Depreci-

ation Areas

Customization Prior to Activation 4.4

147

� 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 � Depre-

ciation 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 settingsafter 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 additionalCustomizing settings as described in the following subsections, before you cancheck and activate new FI-AA.

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 defineG/L accounts as reconciliation accounts for depreciation areas of a parallel valua-tion 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 byseparate depreciation areas where the posting is made to separate accounts in theG/L. Before the migration, these asset balance sheet accounts were posted directlyin FI.

In the future, the asset values for both the leading and parallel valuation will beposted directly in FI-AA. Thus, these asset balance sheet accounts must be definedas asset reconciliation accounts because they will only be allowed to be posted inFI-AA.

You can change the existing balance sheet accounts of the parallel valuation thatwere posted directly as asset reconciliation accounts for the future in Customizing

Customizing for the New Asset Accounting4

148

under Asset Accounting (New) � Preparations for Going Live � Production

Startup � Accounts Approach. You can reset the reconciliation accounts for par-allel valuations, as shown in Figure 4.3.

Figure 4.3 Defining Reconciliation Accounts for New Asset Accounting

Before the migration to SAP S/4HANA Finance, you need to check and reconcilethe balance sheet values of both FI-AA and SAP General Ledger Accounting forparallel 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 updatingquantities in your chart of depreciation. This setting is relevant if you’re using col-lective low-value assets in your organization. When there is a posting made tothis depreciation area, the quantities are updated in the asset master record. TheCustomizing is done under Asset Accounting (New) � General Valuation �

Depreciation Areas � Define Depreciation Area for Quantity Update.

Customization Prior to Activation 4.4

149

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/4HANAFinance. When, using Transaction F-90, you post an asset acquisition through avendor and input all the necessary parameters, including a debit to the fixed assetand a credit to the vendor account, new FI-AA breaks the posting into the follow-ing two components:

1. The first document is created with document Type AA which is posted for thespecified ledger/ledger group with a debit to the asset and a credit to the tech-nical clearing account, as specified in Customizing. In Figure 4.4, the documentis posted for Accounting Principle IFRS, while in Figure 4.5, the document isposted for Accounting Principle US GAAP.

Figure 4.4 FI-AA Posting for IFRS

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

Customizing for the New Asset Accounting4

150

Figure 4.5 FI-AA Posting for US GAAP

The business transaction is thus divided into an operational part and a valuatingpart during the integrated asset acquisition posting:

� For the operational part (vendor invoice), a ledger-group-independent docu-ment valid for all accounting principles is posted against the technical clearingaccount for integrated asset acquisitions.

� For each valuating part (capitalization of the asset), a separate ledger-group-spe-cific document valid for each of the accounting principles is posted against thetechnical clearing account for integrated asset acquisitions.

Thus, the technical clearing account for integrated asset acquisitions is postedautomatically and always has a zero balance for each of the accounting principlesin the chart of depreciation.

Because it has a zero balance, this account doesn’t appear in the balance sheet, butit appears as notes to the financial statement. As a prerequisite, you need to createa new G/L account as an asset reconciliation account with the following descrip-tion: “technical clearing account for integrated asset acquisitions.” This account iscreated using Transaction FS00 and appears in both the chart of accounts and thecompany code section.

You need to assign this G/L account in the FI-AA account determination foryour chart of accounts in Customizing under Asset Accounting (New) � Inte-

gration with General Ledger Accounting � Technical Clearing Account

Customization Prior to Activation 4.4

151

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 Specify an Alternative Document Type for Accounting-Principle-Specific Documents

If your organization is using the new G/L with document splitting activated, andyou want the document splitting rules for the valuating document (asset acquisi-tion) and the operative document (Accounts Payable) to be different, you’ll needto specify separate document types for the valuating document that are valid foreach of the accounting principles. Alternatively, if your organization policy is tohave separate document types for both valuating and operative documents, thisCustomizing activity needs to be executed.

You need to check if the existing document types can be used for this activity, orif 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-prin-ciple-specific valuating documents in Customizing under Asset Accounting

(New) � Integration with General Ledger Accounting � Integrated Transac-

tions: Alternative Doc. Type for Accounting-Principle-Specific Documents �

Specify Alternative Document Type for Accounting-Principle-Specific Docu-

ments.

4.4.5 Specify Revenue Distribution for Asset Retirement

You can distribute revenues generated from the retirement of assets for a com-pany 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 distri-bution of revenue for asset retirement under Asset Accounting (New) � Trans-

actions � Retirements � Gain/Loss Posting � Define Revenue Distribution for

Fixed Asset Retirement, as shown in Figure 4.7.

Customizing for the New Asset Accounting4

152

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 methodfor 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; how-ever, based on your legal and organizational requirement, you can configure topost the net book value of the assets for a depreciation area. In that case, the netbook value is posted to the account for clearing of revenue from asset sales toeither vendors or affiliated companies.

In some countries (e.g., France), you’re legally required to post the net bookvalue. Therefore, you need to check if it’s a legal requirement to post the net bookvalue for individual depreciation areas and then configure accordingly in Custom-izing 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 thisposting option. Next, you need to identify the depreciation areas within the com-pany codes for posting the net book value to a revenue clearing account duringthe asset retirement process.

4.4.7 Check Transaction Types

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

Check Prerequisites for Activating New Asset Accounting 4.5

153

4.5 Check Prerequisites for Activating New Asset Accounting

After you’ve migrated the charts of depreciation, made the assignments to thecompany codes, and performed the additional manual Customizing settings, youcan then determine whether the prerequisites for activating the new FI-AA havebeen met.

In this activity, you check the prerequisites for parallel valuation in the new FI-AA. The prerequisite for changing the leading valuation in the new SAP GeneralLedger 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 allprerequisites are met for activating the business function PARALLEL_VAL Custom-izing switch and if all periodic postings have been successfully completed.

You can activate new FI-AA using the business function PARALLEL_VAL Customiz-ing switch. This program checks whether all the prerequisites for activating newFI-AA have been met. You also need to ensure that no postings are made betweenthe execution of Transaction FAA_CHECK_ACTIVATION and the import of thePARALLEL_VAL Customizing switch, as shown in Figure 4.9.

Figure 4.9 Check Prerequisites for Parallel Valuation in FI-AA

Customizing for the New Asset Accounting4

154

The report must show a green light under the Type column, as shown in Figure4.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 depreciationhave been migrated and assigned to the company code before any documents canbe 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 ofdepreciation.

2. Delete the assignments for charts of depreciation that aren’t relevant or areunused.

Figure 4.11 Determining Active Charts of Depreciation

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

Change Definitions of Depreciation Areas 4.7

155

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 Custom-izing settings as depicted in Figure 4.15 allow all depreciation areas to post imme-diately to the G/L instead of periodically. This also applies for reserves for specialdepreciation areas, as shown in Figure 4.13.

Figure 4.13 Depreciation Area Posting to the General Ledger

Customizing for the New Asset Accounting4

156

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

� AREA DOES NOT POST

� AREA POSTS DEPRECIATION ONLY

� AREA POSTS IN REALTIME

� AREA POSTS APC IMMEDIATELY AND DEPRECIATION

Figure 4.14 Account Determination Assignment to Chart of Depreciation

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

Figure 4.15 Depreciation Area Definition

Specify Transfer of Acquisition and Production Cost Values 4.8

157

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

� For cost-accounting purposes, you want to post depreciation that differs frombook depreciation to expense accounts or cost elements.

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

� You have special requirements for legal consolidation of your corporate group.

� If you’re using the new SAP General Ledger Accounting and the ledgerapproach, you can specify additional depreciation areas from which APC trans-actions are posted automatically to the G/L.

4.8 Specify Transfer of Acquisition and Production Cost Values

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

Figure 4.16 Specify Transfer of APC Values

In the ValAd field in Figure 4.17, you specify the reference depreciation areathat provides values to another depreciation area. The system transfers the post-ing amounts of any transactions that affect APC from this area to the dependentarea.

Customizing for the New Asset Accounting4

158

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 beenassigned the same accounting principle.

� For those depreciation areas that post their APC in real time to SAP GeneralLedger Accounting, the depreciation area must never use values from anotherdepreciation area.

� When transferring values from one depreciation area to another, it doesn’tmake any difference if the depreciation area adopts values from an area that hasa 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 depreciationarea are adopted to another depreciation area, as shown in Figure 4.18. The termscan be transferred between depreciation areas that have been assigned the sameaccounting principle. A depreciation area can also adopt depreciation terms froma depreciation area that has a larger key than it does.

Specify Transfer of Depreciation Terms 4.9

159

Figure 4.18 Specify Transfer of Depreciation Terms

It’s only possible to adopt depreciation terms from depreciation areas that havethe same ledger group. For those depreciation areas that post their APC to SAPGeneral Ledger Accounting in real time, the following applies:

� Depreciation areas that manage APC are never allowed to adopt depreciationterms from another depreciation area. In that case, enter “00” as the key for thedepreciation area.

� The other depreciation areas that post in real time (e.g., areas for investmentsupport or revaluation) are allowed to adopt depreciation terms from anotherarea, 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 adoptedby the current depreciation area in the Transfer of Depreciation Terms from

Depreciation Area (TTr) field. The terms can be transferred only from a depreci-ation area to which the same accounting principle is assigned. A depreciation areacan also adopt depreciation terms from a depreciation area that has a larger keythan it does, as shown in Figure 4.19.

In the standard system, changes to control parameters in the reference deprecia-tion area aren’t automatically transferred to dependent depreciation areas thatadopt depreciation terms. Instead, you can change the depreciation terms independent depreciation areas in the asset master record. However, when you setthe Identical checkbox shown in Figure 4.19, the system transfers all changes inthe reference depreciation area to the dependent depreciation areas, where it’sthen not possible to change them.

Customizing for the New Asset Accounting4

160

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 variouschecks and then saves this setting if no errors are encountered. After the checks havebeen passed successfully and the settings have been saved, new FI-AA becomes acti-vated. From this point onward, you can post using the new posting logic.

Figure 4.20 Activate New Asset Accounting

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

Adjust Parameters in Charts of Depreciation 4.11

161

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.22 Adjust Parameters in Chart of Depreciation

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

� Assign the accounting principle An accounting principle is assigned to each depreciation area, including thenonposting depreciation areas. The system derives the accounting principlefrom the relevant ledger group already assigned to the depreciation area.

For each set of depreciation areas that are assigned to the same accounting prin-ciple, only one depreciation area is allowed to manage APC and have the optionArea Posts in Real Time or Area Posts APC Immediately, Depreciation Peri-

odically.

Customizing for the New Asset Accounting4

162

� Change posting indicator for depreciation areasThe system changes the settings for posting in the G/L, whereby the deprecia-tion areas that represent reserves for special depreciation, for example, in thefuture, post immediately to the G/L. The execution of the program as depictedin Figure 4.22 changes the depreciation areas for the specified chart of depre-ciation to Depreciation Area Posts Balance Sheet Value Immediately,

Depreciation Periodically.

The charts of depreciation are adjusted manually in the following cases:

� The parameters of the charts of depreciation couldn’t be adjusted automaticallybecause the program doesn’t recognize the starting situation defined in yoursystem.

� Adjusting the charts of depreciation manually is standard procedure, regardlessof circumstances.

� The charts of depreciation in FI-AA are assigned to a deactivated companycode. The data of this deactivated company code aren’t archived; therefore, thisdata 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 depreciationduring either the test run or the update run, as shown in Figure 4.23. Any error mes-sages 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 changesin 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

Summary 4.13

163

depreciation is active. You also need to set up a parallel area for each additionalcurrency used in the corresponding G/L. You need to ensure that all inconsisten-cies and errors are fixed during the migration, and it’s prudent to involve all thestakeholders to evaluate relevant data for acceptance of migration.

After reading this chapter, you now understand the Customizing of and migrationsteps for the new FI-AA. Let’s now move on to Chapter 5, where we’ll discuss thesteps you need to take to customize Controlling for your SAP S/4HANA Financemigration.

7

Contents

Preface ............................................................................................................. 19Introduction ..................................................................................................... 27

PART I Migrating to SAP S/4HANA Finance

1 Preparation ................................................................................ 51

1.1 Check Functional Scope and Restrictions ....................................... 511.2 Feasibility Checklist ....................................................................... 531.3 The Maintenance Planner and Prechecks ....................................... 601.4 Check Custom Coding ................................................................... 60

1.4.1 Check Custom Code and Modifications ............................ 611.4.2 Handling Custom-Defined Fields and Interfaces ................ 61

1.5 Check Sizing .................................................................................. 621.6 Precheck for Migration to New Asset Accounting .......................... 631.7 Activate Business Functions ........................................................... 65

1.7.1 Activate Business Functions for Asset Accounting, Parallel Valuation ............................................................. 65

1.7.2 Activate Enterprise Extension EA-FIN ............................... 671.7.3 Activate Business Function FIN_AA_CI_1 ......................... 69

1.8 Check and Activate New Depreciation Calculation ......................... 691.8.1 Execute the Periodic Depreciation Posting Run ................ 701.8.2 Execute Year-End Closing ................................................. 711.8.3 Fiscal Year Change ........................................................... 72

1.9 Consistency Checks ....................................................................... 731.9.1 SAP ERP Financials Data Consistency Checks .................... 731.9.2 Reconciliation of General Ledger and the

Accounts Payable/Accounts Receivable Subledgers .......... 761.9.3 Reconciliation of the General Ledger with

Asset Accounting ............................................................. 771.9.4 Reconciliation of the General Ledger with

Materials Management .................................................... 791.9.5 Reconciliation of Ledgers ................................................. 81

1.10 Perform Period-End Closing Activities ............................................ 831.10.1 Copy Number Ranges ....................................................... 831.10.2 Lock Periods in Materials Management ............................ 841.10.3 Perform Closing for Periodic Asset Postings ...................... 841.10.4 Execute the Periodic Depreciation Posting Run ................ 85

8

Contents

1.10.5 Verify Held Documents Status .......................................... 851.10.6 Carry Balances Forward to the Current Fiscal Year ............ 861.10.7 Reset Valuations for Periods in the Current Fiscal Year ..... 881.10.8 Lock Prior Periods in SAP ERP Financials and

Controlling ....................................................................... 891.10.9 Batch Jobs ........................................................................ 911.10.10 Execute Report to Confirm Asset Accounting

Prerequisites .................................................................... 911.10.11 Lock Users ........................................................................ 91

1.11 Consistency Check before Activation of SAP S/4HANA Finance ...... 911.12 Execute Business Reconciliation ..................................................... 931.13 Summary ....................................................................................... 103

2 Installation and Upgrade .......................................................... 105

2.1 Installation and Upgrade Checklist ................................................. 1062.1.1 SAP HANA and Minimum Versions .................................. 1062.1.2 Software Update Manager ................................................ 1082.1.3 SAP HANA Live ................................................................ 1092.1.4 Administrator’s Guide, Release Information Note,

and Browser Support ........................................................ 1092.1.5 SAP Cash Management Powered by SAP HANA,

Cost Objects, and Cost Object Hierarchies ........................ 1102.1.6 Industry Solutions and Add-Ons ....................................... 1102.1.7 Maintenance Optimizer .................................................... 1112.1.8 Target Stack XML and SAP NetWeaver Kernel .................. 1142.1.9 Customer Code ................................................................ 1142.1.10 Data Definition Language Statement Corrections .............. 115

2.2 Use the Maintenance Planner ........................................................ 1152.3 Install the Related Software Component Version ........................... 1162.4 Apply SAP Notes ........................................................................... 1182.5 Content Deployment with SAP HANA Application Lifecycle

Management ................................................................................. 1202.6 Perform HANA-tization ................................................................. 120

2.6.1 HANA-tization Checks ...................................................... 1212.6.2 HANA-tization Tools ........................................................ 121

2.7 Optimization ................................................................................. 1222.7.1 Optimization Approach .................................................... 1232.7.2 Optimization Tools ........................................................... 1242.7.3 Optimization Best Practice ............................................... 1242.7.4 SAP HANA Modeling ....................................................... 125

2.8 Summary ....................................................................................... 125

Contents

9

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

3.1 Activate SAP Reference Implementation Guide for SAP ERP Financials ........................................................................ 128

3.2 Check and Adopt Fiscal Year Variants ............................................ 1293.3 Migrate General Ledger Customizing ............................................. 1303.4 Define Settings for the Journal Entry Ledger .................................. 1313.5 Define Ledger Groups .................................................................... 1333.6 Assign the Accounting Principle to the Ledger Group .................... 1353.7 Define the Ledger for the Controlling Version ................................ 1363.8 Define Document Types for Postings in Controlling ....................... 1373.9 Define Document Type Mapping Variants for

Controlling Business Transactions .................................................. 1383.10 Check and Define Default Values for Postings in Controlling .......... 1383.11 Define the Offsetting Account Determination Type ....................... 1403.12 Define the Source Ledger for Migration of Balances ....................... 1403.13 Execute Consistency Check of General Ledger Settings .................. 1413.14 Activate Business Functions ........................................................... 1413.15 Summary ....................................................................................... 142

4 Customizing for the New Asset Accounting ............................. 143

4.1 Prerequisites .................................................................................. 1454.2 Install SAP S/4HANA Finance with New Asset Accounting ............. 1454.3 Migrate Charts of Depreciation ...................................................... 1464.4 Customization Prior to Activation .................................................. 147

4.4.1 Define Asset Balance Sheet Accounts of Parallel Valuation ............................................................. 147

4.4.2 Define the Depreciation Area for a Quantity Update ........ 1484.4.3 Define the Technical Clearing Account for

Integrated Asset Acquisition ............................................. 1494.4.4 Specify an Alternative Document Type for

Accounting-Principle-Specific Documents ........................ 1514.4.5 Specify Revenue Distribution for Asset Retirement ........... 1514.4.6 Post Net Book Value Instead of Gain/Loss ........................ 1524.4.7 Check Transaction Types .................................................. 152

4.5 Check Prerequisites for Activating New Asset Accounting .............. 1534.6 Determine Active Charts of Depreciation ....................................... 1544.7 Change Definitions of Depreciation Areas ...................................... 1554.8 Specify Transfer of Acquisition and Production Cost Values ........... 1574.9 Specify Transfer of Depreciation Terms .......................................... 158

10

Contents

4.10 Activate New Asset Accounting ..................................................... 1604.11 Adjust Parameters in Charts of Depreciation .................................. 1614.12 Display Migration Log ................................................................... 1624.13 Summary ....................................................................................... 162

5 Customizing for Controlling ...................................................... 165

5.1 Execute SAP Business Warehouse Delta Extraction for Account-Based Profitability Analysis .............................................. 166

5.2 Adapt Settings for Profitability Segment Characteristics ................. 1665.3 Maintain the Operating Concern ................................................... 1675.4 Maintain the Operating Concern for the Banking Add-On ............. 1685.5 Activate Account-Based Profitability Analysis ................................. 1695.6 Transport Operating Concern ........................................................ 1695.7 Summary ....................................................................................... 170

6 Customizing for Migration of House Bank Accounts ............... 171

6.1 Define Number Ranges for Bank Account Technical IDs ................. 1726.2 Define Number Ranges for Change Requests ................................. 1726.3 Define Settings for Bank Account Master Data ............................... 173

6.3.1 Bank Account Types ......................................................... 1736.3.2 Define Sensitive Fields to Be Protected from Changes ...... 1746.3.3 Define Import Methods for Bank Statements .................... 1766.3.4 Define Signatory Groups for Payment Approvals ............... 1766.3.5 Define the Signatory Groups and Approval Sequence

for Approval Patterns ....................................................... 1776.3.6 Assign Approval Patterns .................................................. 178

6.4 Summary ....................................................................................... 179

7 Data Migration .......................................................................... 181

7.1 Partitioning of the Universal Journal Entry Line Items Table ........... 1827.2 Regenerating Core Data Services Views and Field Mapping ........... 1837.3 Migration of Cost Elements ........................................................... 185

7.3.1 Check Consistency of SAP General Ledger Accounts and Cost Elements ............................................................ 187

7.3.2 Migrate Secondary Cost Elements to the Chart of Accounts ...................................................................... 189

7.3.3 Display Status of Migration of Cost Elements .................... 1907.3.4 Migrate Default Account Assignments .............................. 190

Contents

11

7.3.5 Display the Status of the Default Account Assignments Migration ......................................................................... 192

7.3.6 Adopt Authorizations ....................................................... 1927.3.7 Define Authorizations and Profiles ................................... 193

7.4 Technical Check of Transaction Data .............................................. 1987.4.1 Analyze Transactional Data ............................................... 1997.4.2 Display Status of Analysis of Transaction Data .................. 2007.4.3 Reconcile Transactional Data ............................................ 2037.4.4 Display Status of Technical Reconciliation of

Transactional Data ........................................................... 2047.5 Enrichment of Data ....................................................................... 207

7.5.1 Enrich Transactional Data ................................................. 2087.5.2 Display Status of Transactional Data Enrichment .............. 2097.5.3 Check of Migrated Documents ......................................... 2107.5.4 Display Status of Migrated Documents Check .................. 211

7.6 Migration of Line Items into New Data Structure ........................... 2117.6.1 Migrate Accounting Documents to Universal Journal

Entry Structure ................................................................. 2127.6.2 Display the Status of Document Migration to

Universal Journal Entry ..................................................... 2137.6.3 Check Migration of Accounting Documents to

Universal Journal Entry ..................................................... 2147.6.4 Display Status of Accounting Document

Migration Check ............................................................... 2167.6.5 Migrate General Ledger Allocations .................................. 217

7.7 Migration of Balances .................................................................... 2197.7.1 Migrate Balances .............................................................. 2197.7.2 Display Status of Migration of Balances ............................ 2207.7.3 Check Migration of Balances ............................................ 2217.7.4 Display Status of Migration of Balances Check .................. 222

7.8 Calculation of Depreciation and Totals Values ............................... 2267.8.1 Calculate Initial Depreciation Values ................................ 2277.8.2 Display Status of Calculate Initial Depreciation Values ...... 2287.8.3 Check Initial Depreciation and Total Values ...................... 2297.8.4 Display Status of Check Initial Depreciation and

Total Values ..................................................................... 2297.9 Migration of House Bank Accounts ................................................ 2327.10 Completing the Migration ............................................................. 233

7.10.1 Reconcile and Compare Migrated Data ............................ 2347.10.2 Set Migration to Completed ............................................. 235

7.11 Migration with Near Zero Downtime ............................................ 2357.11.1 Overview of Near Zero Downtime .................................... 236

12

Contents

7.11.2 Restrictions on Business ................................................... 2377.11.3 Activities on the Clone System ......................................... 2377.11.4 Delta Migration ................................................................ 237

7.12 Summary ....................................................................................... 239

8 Post-Migration Activities .......................................................... 241

8.1 Run Reconciliation Reports to Check Data Consistency .................. 2428.2 Validate Business Process to Ensure Successful Migration .............. 2428.3 Transfer Application Indexes .......................................................... 2438.4 Display Status of Application Indexes Transfer ............................... 2448.5 Fill Due Dates in SAP ERP Financials Documents ........................... 2448.6 Display Status of Due Dates into SAP ERP Financials Documents ... 2458.7 Fill the Offsetting Account in SAP ERP Financials Documents ........ 2468.8 Display Status of Offsetting Account in SAP ERP Financials

Documents .................................................................................... 2478.9 Summary ....................................................................................... 248

9 Post-Migration Testing ............................................................. 249

9.1 Test SAP HANA-Optimized Report Transactions ............................ 2509.2 Test Multidimensional Reporting Capability ................................... 2509.3 Test Database Footprint Reduction ................................................ 2519.4 Test Intercompany Reconciliation .................................................. 2529.5 Test the New Process Redesign ...................................................... 2529.6 Test Closing Improvement ............................................................. 2539.7 Test the Universal Journal .............................................................. 2539.8 Execute Change Management ........................................................ 2549.9 Summary ....................................................................................... 255

PART II New Functionality in SAP S/4HANA Finance

10 SAP Cash Management ............................................................. 259

10.1 Validate Prerequisites .................................................................... 26110.2 Setup Bank Account Master Data .................................................. 262

10.2.1 Banks and House Banks .................................................... 26210.2.2 Migrate House Bank Accounts .......................................... 26410.2.3 Upload and Download Bank Accounts .............................. 265

10.3 Define the Payment Approval Process ........................................... 26610.3.1 Basic Setting for Approval ................................................ 267

Contents

13

10.3.2 Rule Maintenance ............................................................ 26810.3.3 Additional Criteria for Payment Grouping ......................... 26910.3.4 Mark Rules for Automatic Payment .................................. 27010.3.5 Specify the Signature Method for Approval Using a

Simple Signature .............................................................. 27110.3.6 Enable Signatory Control .................................................. 27210.3.7 Specify Settings for the Bank Statement Monitor .............. 273

10.4 Enable SAP Business Workflow for Bank Account Management ..... 27410.4.1 Maintain Event Type Linkage ........................................... 27410.4.2 Define and Maintain Organizational Hierarchy ................. 27610.4.3 Define Responsibilities and Assign Users .......................... 27610.4.4 Create Custom-Defined Workflows .................................. 28110.4.5 Predefined Workflows ...................................................... 281

10.5 Create Cash Pools for Cash Concentration ..................................... 28510.5.1 Define Clearing Accounts for the Receiving Bank for

Account Transfers ............................................................. 28610.5.2 Define Clearing Accounts for Cross-Country Bank

Account Transfers ............................................................. 28710.5.3 Define Account Determination ......................................... 28810.5.4 Check Account Determination .......................................... 288

10.6 Manage Cash Operations ............................................................... 28910.6.1 Define and Assign Flow Types .......................................... 29010.6.2 Define Liquidity Items and Hierarchies ............................. 30010.6.3 Define Planning Levels and Groups .................................. 304

10.7 Load Data to One Exposure from Operations ................................ 30810.7.1 Integration with Source Applications ................................ 30810.7.2 Integration with Remote Systems ..................................... 309

10.8 Set Up Cash Management Transaction Data .................................. 31010.8.1 Activate Individual Source Applications ............................ 31110.8.2 Activate Multiple Source Applications .............................. 31210.8.3 Rebuild Planning Levels, Groups, and Dates in

Accounting Documents .................................................... 31310.8.4 Insert House Bank and House Bank Account Data to

Accounting Documents .................................................... 31410.8.5 Rebuild Liquidity Items in Accounting Documents ........... 31510.8.6 Rebuild Flow Types in Accounting Documents ................. 31610.8.7 Load Transaction Data into One Exposure from

Operations Hub ............................................................... 31610.9 Set Up SAP Liquidity Management ................................................ 318

10.9.1 Install and Configure SAP BusinessObjects Business Intelligence Content ......................................................... 318

14

Contents

10.9.2 Activate SAP BusinessObjects Business Intelligence Content .......................................................................... 320

10.9.3 Install Template for Cash Flow Analysis ........................... 32110.9.4 Generate a Planning View ............................................... 32310.9.5 Activate SAP BPC Content .............................................. 32410.9.6 Install SAP BPC Content ................................................. 324

10.10 Set Up Liquidity Planning .............................................................. 32710.10.1 Specify an SAP BPC Configuration Set ............................. 32710.10.2 Create Planning Units ..................................................... 32810.10.3 Activate Planning Unit Hierarchy .................................... 32810.10.4 Currency Conversion Rules ............................................. 33010.10.5 Reference Data Sources .................................................. 33110.10.6 Exclude Liquidity Items Representing Balance Values ...... 33110.10.7 Liquidity Planning Types ................................................. 331

10.11 Summary ....................................................................................... 332

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

11.1 Planning Overview and Activation ................................................. 33411.1.1 Business Benefits ............................................................ 33411.1.2 Applications Used by Planning ........................................ 33711.1.3 Activate Business Functions for Planning ........................ 338

11.2 Architecture .................................................................................. 33811.2.1 Planning Accelerators ..................................................... 33911.2.2 Data Flow Architecture ................................................... 340

11.3 Authorizations ............................................................................... 34111.4 Activate Embedded SAP Business Warehouse ................................ 345

11.4.1 Choose SAP Business Warehouse Client .......................... 34511.4.2 Check SAP Business Warehouse Client Setting ................ 34511.4.3 Set the SAP Business Warehouse Client .......................... 34711.4.4 Assign the Logical System Client ..................................... 34811.4.5 Set SAP Business Warehouse Namespaces to

Changeable ..................................................................... 35111.4.6 Install the Technical SAP Business Warehouse Content ... 35211.4.7 Check Installation Status and Resolve Errors ................... 35311.4.8 Check Planning Content Activation ................................. 355

11.5 Activate the SAP BusinessObjects Business Intelligence Content Bundle ............................................................................. 35611.5.1 Activate the DataSources ................................................ 35711.5.2 Activate the Content Bundle ........................................... 358

Contents

15

11.6 Test the SAP Business Warehouse Installation ............................... 36311.6.1 Set the User Parameter ..................................................... 36411.6.2 Test the Planning Query Installation ................................. 364

11.7 Activate Services and Test Planning Applications ........................... 36611.7.1 Check General Settings for Web Dynpro ........................... 36711.7.2 Run Report RSICF_SERVICE_ACTIVATION ....................... 36711.7.3 Activate Services for the Planning Applications ................. 36811.7.4 Test the New Planning Application ................................... 369

11.8 Planning Modeler .......................................................................... 37111.9 SAP BusinessObjects Analysis for Microsoft Office ......................... 37311.10 Summary ....................................................................................... 378

12 SAP Fiori Applications ............................................................... 379

12.1 SAP Fiori Project Phases ................................................................ 38012.2 Architecture .................................................................................. 38112.3 Configure SAP Fiori ....................................................................... 38312.4 Install SAP Fiori Apps .................................................................... 386

12.4.1 Transaction and Fact Sheet Apps ...................................... 38612.4.2 Analytical Apps ................................................................ 387

12.5 SAP Fiori Launchpad ...................................................................... 38712.5.1 Frontend User Screen ....................................................... 38812.5.2 Backend Configuration Screen .......................................... 39012.5.3 SAP Smart Business Key Performance Indicators ............... 392

12.6 SAP Fiori Application and Roles ..................................................... 39412.6.1 General Ledger Accountant .............................................. 39412.6.2 Accounts Payable Accountant .......................................... 39712.6.3 Accounts Receivable Accountant ...................................... 39912.6.4 Controller ......................................................................... 40112.6.5 Cash Manager .................................................................. 40512.6.6 Cost Manager ................................................................... 408

12.7 SAP Smart Business Application and Roles ..................................... 40912.7.1 SAP Smart Business for Accounts Payable ......................... 40912.7.2 SAP Smart Business for Accounts Receivable .................... 41112.7.3 SAP Smart Business for Chief Financial Officers ................. 41212.7.4 SAP Smart Business for SAP Cash Management ................ 413

12.8 Summary ....................................................................................... 414

16

Contents

PART III Impact of SAP S/4HANA Finance

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

13.1 Architectural Impact ...................................................................... 41713.2 Functionality Impact ...................................................................... 42413.3 Configuration Impact ..................................................................... 426

13.3.1 Copy Company Code ........................................................ 42613.3.2 Consistency Check ............................................................ 42713.3.3 Document Summarization ................................................ 42713.3.4 Universal Journal Entry Organization ................................ 42713.3.5 Ledger Configuration ........................................................ 42813.3.6 Document Types and Numbering ..................................... 43113.3.7 Document Posting ............................................................ 43113.3.8 Integration of SAP ERP Financials and Controlling ............ 43213.3.9 Define Ledger for the Controlling Version ........................ 434

13.4 Customer and Vendor Master Data ................................................ 43413.5 Credit Management Impact ........................................................... 43513.6 SAP HANA Views in SAP S/4HANA Finance ................................... 43613.7 Summary ....................................................................................... 437

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

14.1 Architectural Impact ...................................................................... 43914.2 Functionality Impact ...................................................................... 440

14.2.1 General Functionality Changes ......................................... 44014.2.2 Changes in Transaction Codes .......................................... 44514.2.3 Table Changes .................................................................. 446

14.3 Configuration Impact ..................................................................... 44714.3.1 Define How Depreciation Areas Post to the

SAP General Ledger .......................................................... 44714.3.2 Specify Transfer of Acquisition and Production

Cost Values ...................................................................... 44714.3.3 Specify Transfer of Depreciation Terms ............................. 44814.3.4 Activate New Asset Accounting ........................................ 44914.3.5 Technical Clearing Account for Integrated Asset

Acquisition ....................................................................... 44914.4 Closing Process Impact .................................................................. 45014.5 SAP HANA Views in SAP S/4HANA Finance ................................... 45114.6 Summary ....................................................................................... 451

Contents

17

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

15.1 Functionality Impact ...................................................................... 45315.1.1 Cost Elements ................................................................. 45415.1.2 Allocations ..................................................................... 45415.1.3 Currencies ...................................................................... 45515.1.4 Integration of SAP ERP Financials and Controlling .......... 45615.1.5 Document Numbers in Controlling ................................. 45615.1.6 SAP Material Ledger ....................................................... 45715.1.7 Transfer Pricing ............................................................... 45915.1.8 General Cost Objects and Cost Object Hierarchies .......... 45915.1.9 Changes in Transaction Codes ......................................... 460

15.2 Configuration Impact ..................................................................... 46115.2.1 Integration of Controlling with SAP ERP Financials ......... 46115.2.2 Cost Element as an SAP General Ledger Account ............ 46215.2.3 Ledger for Controlling ..................................................... 46315.2.4 Rule for Posting in Controlling ........................................ 46315.2.5 Ledger View in Customizing ........................................... 46415.2.6 SAP General Ledger Planning .......................................... 46515.2.7 Cash Journal View .......................................................... 46515.2.8 Report Hierarchies Added ............................................... 46615.2.9 Reference and Simulation Costing View .......................... 46715.2.10 Assign Currencies to SAP Material Ledger ....................... 46815.2.11 Assign SAP Material Ledger Type to Valuation Area ........ 46815.2.12 Cost of Goods Sold Posting ............................................. 469

15.3 Summary ....................................................................................... 469

16 Impact on Cost Center Accounting and Profit Center Accounting ........................................................... 471

16.1 Architectural Impact ...................................................................... 47116.2 Functionality Impact ...................................................................... 47316.3 SAP HANA Views in SAP S/4HANA Finance .................................. 47616.4 Web Dynpro Reports ..................................................................... 47616.5 Summary ....................................................................................... 477

17 Impact on Profitability Analysis ................................................ 479

17.1 Architectural Impact ...................................................................... 48017.2 Functionality Impact ...................................................................... 481

18

Contents

17.3 Configuration Impact ..................................................................... 48217.3.1 Define Profitability Segment Characteristics ...................... 48217.3.2 SAP HANA Integration ..................................................... 48317.3.3 Segment-Level Characteristics for Distributed

Profitability Analysis ........................................................ 48417.4 Summary ....................................................................................... 484

18 Impact on Period-End Closing .................................................. 485

18.1 Architectural Impact ...................................................................... 48518.2 Functionality Impact ...................................................................... 48618.3 Security Impact .............................................................................. 48818.4 SAP HANA Views .......................................................................... 48918.5 Summary ....................................................................................... 490

19 Impact on SAP Cash Management and Bank Account Management ...................................................... 491

19.1 Introduction of SAP Business Client ............................................... 49119.2 Functionality Impact ...................................................................... 49319.3 Security Impact .............................................................................. 49519.4 Configuration Impact ..................................................................... 49619.5 Summary ....................................................................................... 497

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

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

527

Index

A

ABAP, 61, 124, 387backend server, 383frontend server, 382

ABAP Development Tools (ADT), 115, 123ABAP Workbench, 342Account assignment, 190Account determination, 140, 288Accounting, 30Accounting principle, 135, 159, 161Accounting principle document, 441Accounts Payable (AP), 36, 489Accounts payable accountant, 397Accounts Payable Manager app, 410Accounts Receivable (AR), 36Accounts receivable accountant, 399Acquisition and production cost (APC), 64,

159, 161, 450transaction, 157value, 157

Activation log, 363Activity-based costing (ABC), 52Administrator’s Guide, 109Adopt authorizations, 192Adopt fiscal year variant, 129Allocation, 454Analytic view, 125Appendix ledger, 131, 422–423, 429Application index, 244

transfer, 243Application Linking and Embedding (ALE), 62Approval pattern, 177–179Architecture, 34Asset, 439Asset Accounting, 145Asset acquisition, 441Asset retirement, 151Asset value, 157Attribute view, 125Authorization, 196Authorization profile, 193, 197Authorization value, 196Automatic payment, 270

B

Balance carryforward, 81, 486Balance sheet, 157Balance sheet account, 88, 190Balance sheet adjustment, 487Bank account

closure, 494master data, 172–173technical ID, 172type, 173–174

Bank Account Management, 172, 232, 259, 266, 274, 276, 285, 491, 493

Bank account master data, 262review, 284

Bank account number mapping, 232Bank clearing account, 294Bank clearing account determination, 288Bank directory, 263Bank master data, 496Bank statement, 176Bank statement monitor, 273Bank subaccount, 294Banking add-on, 168Business Add-In (BAdI), 232Business Application Programming Interface

(BAPI), 61Business Configuration Sets (BC Sets), 68Business function, 141, 338

DAAG_DATA_AGING, 243EA-FIN, 67FI-G/L, 62FIN_AA_PARALLEL_VAL, 65, 153FIN_CO_CCMGMT, 338FIN_CO_CCPLAN, 338FIN_CO_ORPLAN, 338FIN_FSCM_CLM, 261FIN_GL_CI_1, 141FIN_GL_DISTR_SCEN_1, 62OPS_PS_CI_1, 338

Business function/switch concept, 114Business Object Repository, 281Business unit, 479

528

Index

C

Cash concentration, 285Cash Journal, 465Cash manager, 405Cash manager role, 495Cash Operations, 259, 289Cash pool, 285Cash Position, 496Central Finance, 44CFO, 28, 412Change and Transport System (CTS), 341Change management, 38, 254Change request, number range, 172Chart of accounts, 190Chart of depreciation, 146–147, 154, 161, 447

migration, 146Charts, 393Checklist, 106Clearing account, 286–287Clone system, 236Closing Cockpit, 486Closing process, 450Cluster table, 125Cluster/pool table, 121Code pushdown, 122Company code, 92, 131, 135–136, 145, 162,

175, 426, 463Compatibility view, 472Compliance capabilities, 251Compliance Management, 31Concur, 27Consistency check, 73, 141, 187Consumer and Mortgage Loans (CML), 310Content bundle, 358Control parameter, 159Controller, 401Controlling, 35, 52, 105, 127, 138, 165, 338,

441, 453, 471, 489area, 92, 132, 480business transaction, 138document, 204document migration, 457historic plan data, 339posting, 454transactional data, 206version, 136

Core Data Services (CDS) view, 115, 183, 473Cost center, 191, 444, 473Cost Center Accounting, 471, 474

views, 476Cost center planning, 489Cost center report, 476–477Cost element, 187, 189, 339, 473Cost manager, 408Cost object, 110Cost object hierarchy, 110Cost of goods sold (COGS), 252, 469, 479Create Manual Payment app, 398Credit Management, 435Currency

new settings, 455Currency conversion, 330Custom code, 40, 42, 60Custom Development Management Cockpit

(CDMC), 123

D

Data aging, 34Data cleansing, 39Data consistency, 73, 242Data definition language (DDL), 183

description, 115Data definition language statement (DDLS)

views, 115Data Dictionary, 38, 183, 348Data migration, 37Data model, 115Data structure, 211, 459Data Warehousing Workbench, 344, 372Database footprint, 251Database migration option (DMO), 38, 108Database size, 55Database table, 120DataSource, 357Days sales outstanding (DSO), 379Days Sales Outstanding app, 412Declustering, 122Default ledger group, 139, 463Delta CO totals, 219Delta migration, 237Depooling, 121

Index

529

Depreciation, 85, 226area, 64, 143, 146, 148, 155, 158–159, 447calculation, 70terms, 158–159, 448

Depreciation calculation program (DCP), 145Depreciation run, 243

posting, 444Depreciation value, 227

initial, 229Display Customer Balances app, 400Document migration status, 213Document number, 201Document number range, 83Document posting, 431Document splitting, 41Document type, 137, 431Due date, 244Duplicate entry, 215

E

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

F

FI-CO integration, 432FI-CO reconciliations, 31Field

FDTAG, 305HBKID, 314HKTID, 314

Financial close, 30, 33Financial operations source application, 312Fiscal year, 140Fiscal year change, 72Fiscal year variants for fixed assets, 441Fixed Assets functionality, 40

Flow category, 290Flow level, 290Flow type, 290, 292Function module

RS_MANDT_UNIQUE_SET, 346Functional account, 174

G

G/L accountant, 394General Availability (GA) Care program, 114Generally accepted accounting principles

(GAAP), 67Goods receipt/invoice receipt (GR/IR), 243Graphical calculation view, 125Greenfield implementation, 43, 51

H

HANA-tization, 120tools, 121

Held document, 85House bank, 314House bank account, 171, 232

I

Import and Export Bank Accounts tool, 233Import method, 176Income statement, 480Index table, 42Industry solution, 110InfoCube, 339InfoObject, 339, 356InfoProvider, 339Installation, 105Integrated asset acquisition, 449Intercompany reconciliation, 252, 486International Financial Reporting Standards

(IFRS), 67Internet Communication Framework (ICF),

367Internet Communication Manager (ICM), 367Invoice Verification, 397, 399

530

Index

J

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

K

Key performance indicator (KPI), 30, 379

L

Landscape Management Database (LMDB), 116

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

M

Maintenance Optimizer, 62, 108, 111Maintenance planner, 60, 115Manage Bank Accounts app, 407Mapping, 184Mapping variant, 463Materials Management (MM), 73Migrate Balance activity, 457Migrate house bank accounts, 264Migrated documents

check, 210Migration, 88, 206

cost element, 185cost elements, 190data, 181data view, 184house bank account, 232log, 162phases, 45

Migration of balances, 127, 219, 221check, 221display status, 222

Month-end depreciation run, 440Multidimensional reporting, 250My Spend app, 408

N

Near Zero Downtime (NZDT), 181, 235Net book value, 152New Asset Accounting, 33, 40, 42, 52, 63–64,

143, 160, 226, 439, 486activation, 449

New G/L migration, 37Nonleading ledger, 422, 428Nonoperating expense, 190Nonsequential signatory pattern, 178Nonstatistical line item, 440Number range, 172

interval, 172

O

ObjectFINS_MIG, 239

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

P

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

Index

531

Payment approval, 266Payment grouping, 268Payment request, 295Performance expectations, 55Performance statistics, 123Period control, 84Period-end closing, 83, 485Periodic depreciation posting run, 70Plan data, 447Planned depreciation value, 439Planned status, 66Planning group, 304, 306Planning level, 298, 304Planning Modeler, 371–372Planning query, 364Planning unit, 328Planning unit hierarchy, 328–329Planning view, 323Post General Journal Entries app, 396Post-migration activity, 241Preparation, 51Prima nota, 422Primary cost, 190Primary cost element, 187, 462Prior period, 89Product Cost Controlling (CO-PC), 110Product System Editor, 116Production variance, 480Profit & loss, 453Profit Center Accounting, 52, 471, 474Profit center planning, 473Profit Centers – Actuals app, 404Profitability Analysis (CO-PA), 57, 165, 243,

249, 454account-based, 166, 479costing-based, 479distributed, 484

Profitability characteristic, 480Profitability segment, 165, 213Program

FAA_DEPRECIATION_CALCULATE, 227FAA_DEPRECIATION_POST, 70FCO_ADD_COPA_FIELD_TO_ACDOCA, 481FINS_MIGRATION_START, 237General Ledger Line Items List, 94RAABST02, 77RAGITT_ALV01, 97

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

Project plan, 499

Q

Questionnaire, 53

R

Read access, 185Real Estate Management, 52Real-time integration, 131Reconciliation, 93, 206, 234

ledgers, 81Reconciliation reports, 242Reference data source, 331Relational database management system

(RDBMS), 38Remote Function Call, 361, 385Report, 242, 476

FINS_MIGRATION_STATUS, 185FQME_BANK_CASH_BAL_IMPORT, 309PFCG_TIME_DEPENDENCY, 198RSICF_SERVICE_ACTIVATION, 367

Report hierarchy, 466Reporting, 440Representative ledger, 139Restrictions, 51

532

Index

Role, 194FUCN_GL_ACCOUNTANT, 192SAP_BW_BI_ADMINISTRATOR, 355SAP_SFIN_ACC_PLANNING, 339SAP_SFIN_CASH_MANAGER, 261

Roll up values, 486Root cause, 206Rule

FCLM_CASHMGR, 281FCLM_CASHSYSCOLL, 282FCLM_REVWOR, 282

S

SAP Add-On Installation Tool (SAINT), 108SAP Ariba Network, 27SAP Bank Communication Management, 266SAP BPC for S/4HANA Finance, 58, 324, 336–

337, 474, 493SAP BPC web client, 337SAP Business Client, 117, 337, 465, 474, 491–

492SAP Business Explorer, 344SAP Business Suite, 36, 39, 65SAP Business Suite on SAP HANA, 379SAP Business Warehouse, 54, 165–166, 328,

335client, 345, 347embedded, 345namespace, 351

SAP Business Workflow, 174SAP BusinessObjects BI, 318, 340, 382SAP BusinessObjects Business Intelligence

Content Activation Workbench, 359SAP BusinessObjects Business Intelligence

Content bundle, 356SAP BusinessObjects Design Studio, 406SAP Cash and Liquidity Management, 58, 232,

491SAP Cash Management, 33, 40, 52, 110, 179,

259, 304, 312, 413, 491, 496SAP Code Inspector (SCI), 123–124SAP DataSource, 343SAP ERP, 53–54SAP ERP 6.0, 36SAP ERP 6.0 EHP 7, 107

SAP ERP Financials (FI), 35, 70, 105, 110, 114, 128–129, 147, 165, 241, 250, 380, 454

SAP ERP Financials Extension (EA-FIN), 145SAP EWM, 112SAP Fiori, 27, 56, 106, 337, 377, 379, 486

analytical app, 379app, 28, 496apps, 386architecture, 381dashboard for Cash Manager, 407Fact sheet app, 379project phases, 380Transactional app, 379

SAP Fiori launchpad, 382, 387SAP Fiori UI5, 395, 397, 399, 402, 406SAP Gateway, 113, 117, 382, 384SAP General Ledger, 34–35, 40–41, 52, 73,

127, 147, 156, 339, 454, 480account, 187, 189, 252, 454account mapping, 456allocation, 217Customizing, 127, 130document, 203summary table, 217

SAP General Ledger Accounting, 36, 61, 73, 140–141, 157, 226, 417, 439–440, 465, 471, 479, 489migration, 459

SAP GUI, 56, 334SAP HANA, 29, 56, 106, 121, 377, 483

artifact, 123database, 27database migration, 44integration, 483modeling, 125view, 436, 451

SAP HANA application lifecycle management (HALM), 109, 120

SAP HANA Cloud Platform, 27SAP HANA Extended Application Services

Advanced, 382SAP HANA Lifecycle Manager (HLM), 109SAP HANA Live, 28, 120

packages, 109SAP HANA view, 489SAP HCM Organizational Management, 198SAP Landscape Transformation Replication

Server, 106

Index

533

SAP Liquidity Management, 260, 318SAP List Viewer (ALV), 124SAP Material Ledger, 58, 457, 459, 468SAP Mobile Platform, 114, 381SAP NetWeaver, 108, 114, 337SAP NetWeaver 7.40, 107SAP NetWeaver ABAP, 38SAP NetWeaver Enterprise Search, 386SAP Process Integration (SAP PI), 383SAP reference IMG structure, 128SAP S/4HANA, 27SAP S/4HANA Finance, 36, 64, 143, 494SAP Smart Business, 57, 109, 113, 409, 411

for cash management, 491KPIs, 392

SAP Smart Business mobile UI, 34SAP Treasury and Risk Management, 31, 287SAP Web Dispatcher, 382, 386Scale-out, 39Scale-up, 39Secondary cost, 190, 485Secondary cost element, 454, 473Secure Sockets Layer (SSL), 385Segment reporting, 41Segment-level characteristics, 484Sensitive field, 174Sequential approval pattern, 178Server group, 444Signatories tab, 175Signatory approval, 271Signatory control, 176Signatory group, 176–177Signature method, 271Single signature, 177Single Sign-On (SSO), 387Sizing, 62Software Update Manager, 38, 60, 62, 108,

116Sorting behavior, 122Source ledger, 140SQL, 61SQL Monitor, 124SQL Performance Tuning Worklist, 124Stack calculation, 107Standard ledger, 131Statistical data, 447Subledger, 79, 86, 221

reconciliation, 76

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

T

Table, 446, 475ACDOCA, 35, 60, 183, 186, 214, 418, 456ANLC, 439ANLP, 439BKPF, 417BNKA, 262BSAD_BCK, 202BSAS_BCK, 202BSEG, 61, 214, 427BSID_BCK, 201BSIS_BCK, 201FAAT_DOC_IT, 439FAAT_PLAN_VALUES, 439–440FAGLFLEXA, 419, 421FAGLFLEXT, 419FAGLFLEXT_BCK, 223, 225, 419FCLM_BAM_ACLINK2, 264FCLM_BAM_AMD, 496FDES, 310FQM_FLOW, 298, 310FQMI_FLOW_CAT, 290HRRP_DIRECTORY, 467HRRP_NODE, 467MLHD, 422MLIT, 422RSADMINA, 345T012K, 264

Table index, 73Table join, 39Technical clearing account, 149, 449Transaction, 124, 195, 445, 460, 474, 486

AB01, 443ABLDT, 443AFAB, 78AFAR, 229AJAB, 71, 78AJRW, 72, 78, 87AS91, 443, 451

534

Index

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

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

Index

535

Transaction (Cont.)SPRO, 66, 348, 358SQLM, 123STC01, 383–384SU01, 385SWDD, 281SWETYPV, 274SWLT, 123

Transaction data, 141, 310Transaction type, 152Transactional data, 198–200, 203Transfer rule, 157, 447Transport Layer Security, 382

U

Unicode, 54Universal Journal, 29, 31–32, 34, 181, 185,

253–254, 419, 454, 457, 485User experience (UX), 27, 335, 379User interface (UI), 28, 333User screen, 388

V

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

W

Web Dynpro, 233, 367, 395, 402, 406report, 476–477

Work in Process (WIP), 252Workflow, 274

custom, 281Workflow template, 282Workflow, report, interface, conversion,

enhancement, form (WRICEF), 57, 254

Y

Year-end closing, 39, 84

First-hand knowledge.

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.

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, Col-laborative 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, Cont-rolling, and Travel Management.

Anup has master’s degrees in business administration and project ma-nagement from The George Washington University, Washington, DC. He is a Stanford Certified Project Manager and a PMI-certified Project Ma-nagement 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 Accoun-ting.

Anup Maheshwari

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

www.sap-press.com/4045


Top Related