System Conversion to S/4HANA FINANCE

2017-03-01_215306

For detailed information on the conversion process, please follow the below mentioned SAP SNotes.

S Notes  
2390881 Consistency checks before the installation during the migration to Asset Accounting (new)
2332030 Conversion of accounting to SAP S/4HANA
2333236 Composite SAP Notes: Enhancements and message texts for the program RASFIN_MIGR_PRECHECK
1939592 SFIN: Pre-Check Report for migrating to New Asset Accouting
2180591 Currencies in FI-GL and FI-AA are inconsistent
2147666 Assigned ledgers in FI-GL and FI-AA are inconsistent
2105948 Check report for Financials add-on
1968568 Release Scope Information: SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA
2220152 Ledger approach and Asset Accounting (new): Non-calendar fiscal year variant for parallel valuation
2023763 SFIN: check old dc engine and parallel currency in precheck report RASFIN_MIGR_PRECHECK
2246638 Check parallel areas in ANLB is mssing in Precheck
2226973 sFIN: Period scaling does not correspond to the definition AFASL
2353504 ACC_AA 173 not issued in case of incorrect configuration
2359854 Precheck: No message handling when checking periodic APC posting
1976487 Information about adjusting customer-specific programs to the simplified data model in SAP Simple Finance
2186803 SAP Simple Finance, OP: Treatment of NewGL tables and customer enhancements
2160045 S/4HANA Finance: Fields of Appends to COEP and BSEG missing in table ACDOCA
2076652 SAP Simple Finance: SAP Note for adjustment of customer-specific programs for aging
2105948 Check report for Financials add-on
2408083 FAQ: Data Model of S/4HANA Finance Data Migration
2431747 General Ledger: Incompatible changes in S/4HANA compared to classic ERP releases

Steps to remember for the Conversion:

Preparation of Data

Before starting system conversion, get system ready by performing the following activities:

⇒ Check the consistency of your financial data and perform reconciliation between your accounting components, so the data can be merged correctly in the universal journal entry. In SAP S/4HANA all line item documents are stored in the universal ACDOCA data table.

⇒ Perform period-end closing including the storage of reporting key figures and closing the posting periods.

  • Lock the current and previous periods in Materials Management using program RMMMPERI.
  • Perform closing for periodic asset postings using program RAPERB2000.
  • Execute the periodic depreciation posting run using program RAPOST2000.
  • Make sure that all held documents have either been posted or deleted.
  • If you are already using account-based profitability analysis, perform a delta upload to SAP BW for all account-based CO-PA DataSources for which you use the delta method.

⇒ Document the posting data. Make sure that all carry forward balances are complete and consistent. To ensure this, carry forward the balances for all currencies and all ledgers.

⇒ Archive any data that you no longer need in every day business processes before the migration.

⇒ If you have not been using the new depreciation calculation from the Enterprise Extension Financials Extension (EA-FIN) you must implement it as part of a separate project.

Prepare Asset Accounting

Activate the new depreciation calculation in your source system. To do so you must activate the EA-FIN business function.

Perform Pre-Checks

 ⇒ Pre-Checks help you identify the steps you need to take to ensure your system is compatible with the conversion process.

⇒ The Controlling and General Ledger pre-checks provided analyze whether your ledger, company code and controlling area settings are consistent and can be migrated to SAP S/4HANA. These Controlling and General Ledger pre-checks are automatically executed when you run the report R_S4_PRE_TRANSITION_CHECKS.

⇒ To run pre-checks for Asset Accounting (FI-AA), please implement the SAP Notes listed in the collective SAP Note 2333236. The pre-check program for Asset Accounting (FI-AA) is not included in the central pre-check report R_S4_PRE_TRANSITION_CHECKS. To execute the appropriate pre-checks for Asset Accounting, please run the report RASFIN_MIGR_PRECHECK.

⇒ Whereas you run the report R_S4_PRE_TRANSITION_CHECKS in client 000 to perform the checks across all clients, then run the report RASFIN_MIGR_PRECHECK in each productive client.

Thank You

Jayanth Maydipalle

ACDOCP on S/4 FINANCE

SAP S/4 Finance, 1610 has ACDOCP table for Planning, which has a similar structure to ACDOCA. SAP Plans to switch all CO objects to update ACDOCP and it would be the “Single Source” for planning data. COSP/COSS tables will be replaced with ACDOCP in future.

2017-02-17_212804

ACDOCP will gradually expand to cover “Period based planning” i,e General ledger Planning, Cost Center Planning, Project/WBS planning and Profitability Planning etc.

The Object based plans that for Projects, Sales orders, Productions orders will write into ACDOCP in future.

ACDOCA and ACDOCP  will bring the actual and the planning together all in one single source of truth.

Thank You

Jayanth Maydipalle

Create Bank Accounts on Fiori / NWBC

Below mentioned Roles are required to activate “Manage bank accounts” app on Fiori.

The user must be assigned with role:

  • SAP_BR_CASH_SPECIALIST (for On-premise Edition)
  • SAP_BCR_FIN_CM_BAM_MC (for Cloud Enterprise Edition)
  • SAP_BCR_FIN_CM_BANK_ACC_MGM (for Cloud Project Services Edition)
Back-End Server: Activate Web Dynpro Application:

Component: Web Dynpro Application

Technical Name: WDA_FCLM_BAM_HIERARCHY

Use transaction “SICF” and make sure that the ICF service for the Web Dynpro application is activated.

Back-End Server: Assign Role with Start Authorization for Web Dynpro Application:

Component: Back-End Role

Technical Name: SAP_SFIN_CASH_MANAGER

2016-12-09_133039

The Manage Bank Accounts transactional app provides an overview of your bank accounts in a hierarchical structure and allows you to maintain bank account master data according to your organization’s business requirements, as shown in

2016-12-09_134425.png

Activation of Material Ledger on SAP S/4 HANA 1511 Finance

Activation of Material Ledger is mandatory on S/3 HANA due change in the data design for Inventory valuation but activation of actual costing is not mandatory on SAP S/4 HANA.

Below mentioned screen shot prescribes traditional Inventory management Vs S/4 HANA Inventory management based on Material ledger.

sdad

Material Valuation in SAP S/4 HANA allows Up to 3 currencies,

  • Tracking historic rates in Material master.
  • Local legal valuation & e.g hard or trading currency.

Actual Costing:

  • Optional revaluation of stock and COGS
  • Leverage Actual cost component

Activate Material Ledger

as

We activate the Material ledger for one or more valuation areas, if the material ledger is active for a particular valuation area, all materials in the valuation area are valuated using the material ledger.

But SAP recommends if you activate the material ledger for a plant, you should also activate it for all the other plants in the company code. This ensures that the accounts in Financial Accounting and Materials Management are reconciled.

Activate Valuation Area’s for Material Ledger:

ax

In this activity, you can specify in each valuation area that a planned price is activated as the valuation price upon the first goods movement in a new posting period as long as the validity date of the planned price has been reached.

The planned prices are handled by the system with the following priority:

  • Marked standard cost estimates
  • Future valuation prices

Actual Costing:

Inventory and material movements are generally valuated either at Standard price (S) which is constant over a period of time or Moving average price (MAP) which gets adjusted (calculated) automatically based on every Goods receipt or Invoice receipt. Both of these two methods have their own pros and cons. Actual costing combines the advantages of standard price with advantages of using MAP.

ML captures all price variances (like purchase price variances, production variances etc) and allows (as optional period end activity) revaluation of ending inventories at period end and releases it as standard price (generally) for next period. Actual costing is optional in S/4 HANA.

Activate Actual Costing:

2016-08-01_105428

2016-08-01_105341

Depending on which activation type is chosen

  • Actual consumption is updated in the quantity structure but not considered by price determination.

You can use this setting if you simply want information about the complete actual quantity structure. You can assign variances between the plan price of the cost center/activity type or process, and the actual price calculated at period end to the particular cost object at period-end closing using the function ‘Revaluation at Actual Prices’.

  • Actual consumption is updated in the quantity structure and taken into account for the price determination.

If you choose this setting, the variances between the plan price and the actual price are adjusted subsequently. The cost center or the process is then credited and the material associated with the consumption is debited. In the context of multi-level price determination, these variances can be rolled up through the production structure up to the finished product in the same way that material price variances are rolled up.

If you choose this setting, you cannot use the function ‘Revaluation at Actual Prices’ at period closing in Cost Object Controlling, as the variances from the cost centers/processes are debited to the material direct. If you do use the function ‘Revaluation at Actual Prices’ at period closing, the cost centers/processes are credited twice and the materials are debited twice.

We have to keep below mentioned points during Migration of Material Ledger Customizing:

Key Points:

  • The material ledger is required if you are using SAP S/4 HANA Materials Management – Inventory Management (Simplified Logistics).
  • You need to migrate the material ledger even if you are already using SAP Simple Finance (that is, you are migrating from SAP Simple Finance to SAP S/4 HANA Inventory Management).
  • You need to migrate the material ledger even if you are already using the material ledger in your source system.

Document number ranges in S/4 HANA sFIN

Document number ranges in S/4 HANA sFIN

Since the system now writes only one journal entry for all of the components G/L,
CO, AA, ML, one document number is sufficient from a business point of view. The
journal entry consists of a header (BKFP) and items {ACDOCA). The respective
document number (BKPF-BELNR/ACDOCA-BELNR) must obey the legal rules of
Financial Accounting. As a consequence, the document number is dependent on
the fiscal year and the company code.

2016-04-14_142900

CO document numbers have not been year dependent. Material ledger document ACDOCA numbers have not been dependent from the DOCLN
organizational unit (e.g. company code). ooooo1 Both numbers did not have a legal ooooo2 relevance. Moreover, ACDOCA has a 6 digit …
field for the document line, whereas COEP oo1o82 has only a 3 digit field. This is still used in 001083 many user interfaces and reports. For compatibility reasons, SAP offers a new 001130transaction number for every 999 documen lines.

The new universal journal entry replaces the Financial Accounting (FI) document and the Controlling (CO) document with a universal document. A journal entry is created for every business transaction in one of the following application components:

  • General Ledger Accounting (FI-GL)

  • Asset Accounting (FI-AA)

  • Controlling (CO)

    Exception: Costing-based Profitability Analysis (CO-PA)

  • Material Ledger (CO-PC-ACT)

Changes in S/4 HANA sFIN Document types and Number ranges:

2016-04-14_151701

In this activity, you define your document types. Document types are used to differentiate the business transactions and to manage how document are stored. This documentation describes the special procedure for setting up document types for New General Ledger Accounting.

2016-04-14_151825

Here, you make the settings specifying the document type for postings to non-leading ledgers.

Under Define document types for Entry View, you make the document type settings for postings in the entry view that effect all ledgers and for postings to the leading ledger.

2016-04-14_152000

SIMGSIMG_CFMENUORFBFBN1

In this IMG activity you create number ranges for documents. For each number range you specify (among other things):

  1. a number interval from which document numbers are selected
  2. the type of number assignments (internal or external)

You assign one or more document typesto each number range. The number range becomes effective via the document type specified in document entry and posting. You can use one number range for several document types. This means you can differentiate documents by document type but combine them again for filing the original documents, provided you store your original documents under the EDP document number.

Integration of Controlling with Financial Accounting:

New Settings for customizing Controlling in S/4 HANA sFIN

2016-04-14_150055

In this activity, you can create new Document types for posting in Controlling, example you can create a document type that you can use for the manual reposting of primary costs.

2016-04-14_150630.jpg

2016-04-14_151033

In this activity, you define a mapping variant that maps CO business transactions to document types. This mapping must be done for all CO business transactions that do actual postings.

Upgrades: The migration of the ledger Customizing generates a default mapping variant in which all CO business transactions are mapped to the document type that was entered in the variant for real-time CO-FI integration.

2016-04-14_151259

You place your mapping of FI documents to CO transaction / document types here

2016-04-14_151441