KEEP In MIND - CHANGES IN S4HANA FINANCE 1709
OSS NOTE
1) Business Partner Hierarchy 2409939 Business Partner hierarchy is removed in SAP S/4HANA to avoid redundancy as customer hierarchy is already available for the applications to consume. The impact this change are Transaction not available in BPH, BPH_TYPE SAP S/4HANA on-premise edition BAPIs not available in SAP S/4HANA on-premise edition
BUHI_ASSIGN_BP_TO_NODE BUHI_CLEAR_BUFFER BUHI_DELETE_BP_FROM_NODE
IMG activity node not available in SAP S/4HANA on-premise edition
Business Partner Group Hierarchy
BOR Object not available in SAP BUS1006004 S/4HANA on-premise edition
2) Business Partner tax Classification 2455724 In S/4HANA, Tax Classification must be maintained for a Business Partner by using Customer role (FLCU01) as Customer Tax Classification, NOT at the Business Partner level. Hence, Business Partner Tax Classification for all the roles is deactivated.
3) Batch Input for Customer Master/Supplier Master 2492904 Since we follow "Business Partner first" approach in SAP S/4HANA, Batch Input programs will cease to work as classical customer and supplier transactions have been made obsolete.
4) Business Partner Approach 2265093 In SAP S/4HANA, Business Partner is the leading object and single-entry point to maintain Business Partner, Customer and Supplier (formerly known as Vendor) master data. This is to ensure ease of maintenance of the above master data and to achieve harmonization between them. Compared to classical ERP transactions, maintenance of Customer and Supplier master data via Business Partner has multiple advantages. · All vendor / customer related transaction codes are not available in S4HANA
5) Material Number Field Length Extension In SAP S/4HANA, the material number field length has been extended from 18 to 40 2267140 characters. This change was first implemented in SAP S/4HANA, on-premise edition 1511 and affects this release and higher releases.
6) Data Model changes in FIN 2270333 With the installation of SAP Simple Finance, on-premise edition totals and application index tables were removed and replaced by identically-named DDL SQL views, called compatibility views. These views are generated from DDL sources. This replacement takes place during the add-on installation of SAP Simple Finance using SUM - related data is secured into backup tables. The compatibility views ensure database SELECTs work as before. However, write access (INSERT, UPDATE, DELETE, MODIFY) was removed from SAP standard, or has to be removed from custom code - refer to SAP note 1976487.
7) Replaces Transaction Codes and programs in FIN 1946054 With the installation of the SAP Simple Finance on-premise edition, certain transaction codes and programs in the application areas of AC, CO, FI, AA and FIN - compared to EhP7 for SAP ERP 6.0 - have been replaced with newer transactions, programs, or WebDynpro applications.
8) SAP Working Capital Analytics / DSO & DPO 2270383 Working Capital Analytics is not available within SAP S/4HANA. These reports for DSO and DPO analysis are available, covering the most important aspects of DSO and DPO analysis in SAP Working Capital Analytics.
9) Integration with FSCM Biller Direct (FI-AR) 2270384 The integration of SAP Accounts Receivable (FI-AR) with FSCM Biller Direct functionality is not considered as the target architecture. The Customer can still continue to use the functionality to make the system conversion to SAP S/4HANA, onpremise edition 1511 less disruptive (Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional equivalent is not available yet.). The integration of SAP Accounts Receivable (FI-AR) with FSCM Biller Direct it is possible to offer to end-customers the convenience of receiving invoices, viewing account status, and making payments online as a self-service.
10) Integration with FSCM Biller Direct (FI-AP) 2270386 The integration of SAP Accounts Payable (FI-AP) with FSCM Biller Direct functionality is not considered as the target architecture. The Customer can still continue to use the functionality to make the system conversion to SAP S/4HANA, on-premise edition 1511 less disruptive (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional equivalent is not available yet.). With the integration of SAP Accounts Payable (FI-AP) with FSCM Biller Direct it is possible to offer to end-vendors the convenience of uploading invoices, monitor the corresponding account movements online as a self-service.
11) Asset Accounting: Changes to Data Structure 2270387 We have been using classic Asset Accounting until now and will be using new Asset Accounting in SAP S/4HANA. If we were using classic General Ledger Accounting before the conversion to SAP S/4HANA, new General Ledger Accounting is activated automatically with the conversion. During conversion actual values from tables ANEP, ANEA, ANLP, ANLC are saved in table ACDOCA in new Asset Accounting. The values from table ANEK are saved in tables BKPF and ACDOCA in new Asset Accounting. The Asset Accounting tables ANEA, ANEP, ANEK, ANLC and ANLP are no longer updated in SAP S/4HANA. We can use our existing reports and developments with the help of compatibility views.
12) Asset Accounting: Parallel valuation and journal entry 2270388 The delta depreciation areas are no longer required and are no longer supported. Now we can record the leading valuation of Asset Accounting in any depreciation area of new Asset Accounting. The system now posts both the actual values of the leading valuation and the values of parallel valuation in real time that means the posting of delta values has been replaced. In New Asset Accounting makes it possible to post in real time in all valuations. Since Assets accounting posting is based on universal Journal, hence no reconciliation, no period posting run for APC values. The programs for reconciliation that existed until now (RAABST01, RAABST02 and FAA_GL_RECON) are therefore no longer available in SAP S/4HANA. The new assets accounting comes with new transactions codes, these are: AB01L, ABAAL, ABAKL, ABAOL, ABAVL, ABAWL, ABGFL, ABGLL, ABIFL, ABMAL, ABMRL, ABNAL, ABNEL, ABNKL, ABSOL, ABSTL, ABUML, ABZEL, ABZOL, ABZPL, ABZUL.
13) Integration to Lease Accounting Engine (LAE) 2270391 The LAE (Lease Accounting Engine) does not support the new Asset Accounting which is automatically activated in S4H.
14) Joint Venture Accounting (JVA) 2270392 With SAP S/4HANA, on-premise edition 1511 (or SAP S/4HANA Finance Edition 1503 SPS2, or higher releases of this add-on), Asset Management transfers in Joint Venture Acccounting are no longer supported.
15) Reference and Simulation Costing 2349294 The creation of cost estimates with reference to base planning objects is no longer supported in SAP S/4HANA. Instead you are recommended to use transaction CKECP to prepare ad-hoc cost estimates and CKUC to prepare multilevel material cost estimates where BOMs and routings are not available for the material in question.
16) Summarization[1] Hierarchies in Controlling 2349282 The layers of the hierarchy are created using transaction KKR0 (Create Summarization Hierarchy). These hierarchies are summarization hierarchies, order hierarchies, or project hierarchies. The top node of the hierarchy is always the controlling area. The next layers might be company code, plant, product hierarchy and material. In SAP ERP the totals for each node in the hierarchy were calculated using a data collection run (transaction KKRC) that typically ran at period close and calculated the totals for each material, each product group, each plant and each company code in the above example and updated these values to the CO totals tables (COSP and COSS) as summarization objects (object type VD). SAP S/4HANA offers a new transaction KKBC_HOE_H that uses the hierarchy structure defined using transaction KKR0 but aggregates the order values on the fly and displays the results by node immediately. In SAP S/4HANA does not calculate target costs or variances on the fly. We must run transaction KKS1 or KKS1H to calculate target costs and variances before executing the new transaction.
17) Technical Changes in Material Ledger with Actual Costing 2354768 With S/4HANA the data model for material ledger data has been changed significantly, especially when actual costing is active. There is no default Material Ledger Type ‘0000’ anymore. Separate currency customizing of Material Ledger (transactions OMX2 / OMX3) has become obligatory, Material Ledger is acting on a subset of the currencies defined for Financials. It is not allowed to use a ML Type that references to currency settings defined in FI or CO (flags ‘Currency Types from FI’ resp. ‘Currency Types from CO’). Instead you have to define explicitly the currency and valuation types that are relevant for Material Ledger. The new Material Ledger Document tables MLDOC and MLDOCCCS replace most former periodic tables (MLHD, MLIT, MLPP, MLPPF, MLCR, MLCRF, MLKEPH, CKMLPP, CKMLCR, MLCD, CKMLMV003, CKMLMV004, CKMLPPWIP, CKMLKEPH).
18) Technical Changes in Controlling 2270404 In SAP S/4 HANA the totals records for primary and secondary costs have been removed and the universal journal includes all actual cost postings, both primary and secondary. The former tables COEP, COSP, and COSS are replaced by views of the same name, socalled compatibility views. CO standard transactions are adapted in a stepwise manner to access the new universal journal table (ACDOCA) directly instead of using compatibility views.
19) Profit and Loss Planning, profit center planning, cost center planning, order 2270407 planning, and project planning From SAP S/4HANA 1610 it is possible to store the results of planning in a new table, ACDOCP, that has the same structure as the universal journal (ACDOCA). Plan/actual reporting is provided by comparing the entries in the two tables. Integration to SAP Analytics Cloud is also via the new table. CO-OM planning, P&L planning, and profit center planning are now covered by SAP BPC for S/4HANA Finance. If you do not want to use SAP BPC for S/4HANA but classic FI-GL and CO-OM planning functions instead, you can continue to use the classic planning transactions.
20) Activity-Based Costing 2270408 The delta versions needed for parallel calculation are no longer supported in SAP S/4HANA. Activity-Based Costing using version 0 (Integrated Activity Based Costing in the controlling area settings) is still supported. Activate Operational Activity Based Costing. Check existing roles and adjust assigned transactions if necessary.
21) General Cost Objects and Cost Object Hierarchies[2] 2270411 General Cost Objects and Cost Object Hierarchies are not available within SAP S/4HANA, on-premise edition 1511. These hierarchies are created by using transaction KKR0 and are aggregated at runtime by using transaction KKBC_HOE_H. Note that this transaction behaves like transaction KKBC_HOE but does not require a data collection run to pre-aggregate the data for each hierarchy node. Where the cost object hierarchy is used to collect costs at an aggregate level and then distribute them to the associated manufacturing orders, it is recommended that transaction CKMDUVMAT be used to distribute material usage variances and CKMDUVACT to distribute activity usage variances.
22) Transfer Prices / COGM / ABC using Delta Versions 2270414 The transfer pricing capabilities are now delivered in the universal journal using a more streamlined and consistent approach than was possible in previous releases. With the merge of FI and CO into the Universal Journal, a new approach for parallel valuations was implemented: (1)Transfer prices can be updated within a ledger containing all valuation views or alternatively with separate ledgers per valuation view. (2) Parallel delta versions for actuals in Controlling are used for statistical line items updating table COEP only. (3) All other actual line items updating table ACDOCA use the new data model.
23) ALE Scenarios 2270416 This note is relevant if you are using ALE scenario for master and transactional data. In S/4HANA system you have a consistent data model for FI and CO and Accounts and Cost Elements are merged.
24) Account/Cost Element 2270419 There is no separate cost element master data maintenance. Account master record includes new field for cost element category which classifies GL accounts. Default account assignments for cost elements can be set in transaction OKB9 rather than in the cost element master. The cost element attribute mix does not exist any longer. Field status groups can remain unchanged. To allow postings in specific periods ensure that postings are allowed for the appropriate accounts in GL and in parallel for the appropriate CO business transactions (transaction OKP1). Cost element groups are still available to group accounts of type primary or secondary cost element for selection and reporting.
25) Reporting/Analytics in Controlling 2349297 The universal journal brings together the account assignments traditionally considered to be part of Controlling (cost center, order, WBS element, and so on), Profitability Analysis (products, product groups, customers, customer groups, regions, and so on) and Enterprise Controlling (profit center). with SAP S/4HANA you have more flexibility and can report on any of the dimensions listed above. To use the new reports, you will have to activate the relevant Fiori apps, and in some cases the embedded BW content within SAP S/4HANA to enable these reports. There are Fiori apps for reporting on cost centers, internal orders, projects, and sales order items. All existing reports in Report Writer/Painter, drill-down reporting and ABAP List Views (ALV) will continue to work using compatibility views but will not provide insight beyond what was already available in SAP ERP. 26) Profitability Analysis 2349278 The universal journal (ACDOCA) is the heart of Accounting and includes all Profitability Analysis (CO-PA) characteristics in order to allow multi-dimensional reporting by market segment. There are also no reconciliation issues between the general ledger and Profitability Analysis.
27) General Ledger 2270339 General Ledger in S/4H is based in the Universal Journal; the line items are stored in the new database table ACDOCA, optimized to SAP HANA. You can migrate Ledgers of New General Ledger of the Business Suite or the Classic General Ledger GL to the Universal Journal in S/4H. Please note, that the number of Ledgers and the configuration of its currency will stay; it is not possible to introduce new ledgers or new currencies during the migration to S/4H. If Classic General Ledger was used, the ledger '00' is migrated to the new leading ledger '0L' of the universal journal. As Controlling is now part of the Universal Journal as well, now all CO internal actual postings are visible in General Ledger as well. The secondary cost elements are part of the chart of accounts. There is no longer a need for Co realtime integration for transfer of secondary CO postings to NewGL or the Reconciliation Ledger of Classic GL. 28) Closing Cockpit with S/4HANA OP 2332547 The Business Functions FIN_ACC_LOCAL_CLOSE, FIN_ACC_LOCAL_CLOSE_2, FIN_ACC_LOCAL_CLOSE_3 (requiring a license for SAP Financial Closing cockpit) are flagged as obsolete in S/4HANA OP. If any of the Business Functions listed above are active, consider to use the Add-On Financials Closing Cockpit 2.0 instead.
29) Currencies in Universal Journal 2344012 With the universal journal and the common line item table ACDOCA for FI and CO, there is also a central currency configuration for the universal journal. As the currency configuration depends on the universal journal ledgers, there is a combined view cluster for ledgers and currencies, tx FINSC_LEDGER.
30) Credit Management 2270544 Credit Management (FI-AR-CR) is not available as part of SAP S/4HANA. The functional equivalent in SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR).
31) Technical Changes in Material Ledger 2332591 The content of most of the former Material Ledger database tables is now stored in table ACDOCA which allows simpler and faster (HANA optimized) access to the data. The attributes of the ML data model that are relevant for the inventory subledger functionality are now part of table ACDOCA. Separate currency customizing of Material Ledger (transactions OMX2 / OMX3) is now mandatory. The Material Ledger acts on the currencies defined for the leading ledger in Financials.
32) Conversion to S/4HANA Material Ledger and Actual Costing 2352383 In SAP S/4HANA, the material ledger is mandatory. Therefore, migration of the material ledger is required in the following scenario: (1) Migration from SAP ERP to SAP S/4HANA 1610 or higher; (2) Migration from SAP Simple Finance to SAP S/4HANA 1610 or higher 33)
Changes
Related OSS Notes
1. Business Partner (No Customer / No Vendor). BP is the single point of entry to 2265093 create, edit, and display master data for business partners, customers, and vendors.Only SAP Business Suite customer with C/V integration in place can move to SAP S/4HANA, on-premise (Conversion approach). It´s recommended but not mandatory that BuPa ID and Customer-ID / Vendor ID are the same. As a result, we may not see few transactions codes relevant for maintenance of customer / vendor master data. SAP strongly suggest to run pre-conversion check for business partner ( OSS Note 2211312) 2) Extension of Material Master Number - SAP S/4HANA can support a material number 2267140 with 40 characters. The appropriate related SAP development entities (domains, data elements, structures, table types, and transparent tables, external and internal interfaces, user interfaces, and so on) have been adapted accordingly. 3) Credit Management - Credit Management (FI-AR-CR) is not available as part of SAP S/4HANA. The functional equivalent in SAP S/4HANA is SAP Credit Management (FINFSCM-CR). if we are using FI-AR-CR, then we need to migrate to FIN-FSCM-CR. This migration includes several elements and SAP provides a tool for such migration in one-system landscape environment. In SAP Credit Management FIN-FSCM-CR, SAP has introduced few new transaction codes by replacing old transaction codes and removed few transaction codes those are relevant to FI-AR-CR. 4) SD Revenue Recognition -ERP SD Revenue Recognition is not available within SAP S/4HANA. The newly available SAP Revenue Accounting and Reporting functionality should be used instead. The new functionality supports the new revenue accounting standard as outlined in IFRS15 and adapted by local GAAPs. Prior to the Conversion to SAP S/4HANA, we need to migrate all sales order and contracts processed by SD Revenue Recognition to SAP Revenue Accounting and Reporting. SAP Revenue Accounting and Reporting has some limitation and does not provide full SD Revenue recognition functionality. Decision Points - If we are using SD Revenue Recognition,we need to evaluate whether a migration to SAP Revenue Accounting and Reporting is possible for our business before we decide to convert to SAP S/4HANA. 5) Finance Tables - With the installation of SAP Simple Finance, on-premise edition totals 1976487 and application index tables were removed and replaced by identically-named DDL SQL views, called compatibility views.The compatibility views ensure database SELECTs work as before. However, write access (INSERT, UPDATE, DELETE, MODIFY) was removed from SAP standard, or has to be removed from custom code refer to SAP note. 6) Configuration - There are mandatory configuration steps in General Ledger, Asset Accounting, Account-Based CO-PA, and Cash Management (if used). IMG -> Preparation and Migration of Customizing for the General Ledger. After migration of configuration, run consistency check( Transaction Code : FINS_CUST_CONS_CHK) to ensure that all inconsistencies removed.
7) Business Process - With the installation of the SAP Simple Finance on-premise edition, 1946054 certain transaction codes and programs in the application areas of AC, CO, FI, AA and FIN - compared to EhP7 for SAP ERP 6.0 - have been replaced with newer transactions, programs, or WebDynpro applications. 8) Architecture - General Ledger in S/4H is based in the Universal Journal; the line items are stored in the new database table ACDOCA, optimized to SAP HANA. We can migrate Ledgers of New General Ledger of the Business Suite or the Classic General Ledger GL to the Universal Journal in S/4H. As Controlling is now part of the Universal Journal as well, now all CO internal actual postings are visible in General Ledger as well. The secondary cost elements are part of the chart of accounts. There is no longer a need for Co realtime integration for transfer of secondary CO postings to NewGL or the Reconciliation Ledger of Classic GL. 9) The functionality of the standard Closing cockpit is not not available in SAP S/4 HANA 1511, 1610 or subsequent release. Thus transaction codes CLOCO, CLOCOC, CLOCOS and CLOCOT are not supported for S/4 HANA OP. In S4 HANA Simple Finance / S4 HANA Finance SAP provides an Add-On Financials Closing Cockpit 2.0. 10) Currency - In ECC we can use to be up to 3 parallel currencies in FI (table T001A / tx OB22) and 2 parallel currencies in CO (TKA01 / tx OKKP): CO area currency and object currency. In case of S4 HANA Fianance Universal Journal currency conversion configuration depends of Universal Journal Ledger. Universal Journal facilitate to store data up to 10 currencies. 11) Assets Accounting - In the migration process, classic assets account will be migrated to New Asset Accounting. We can migrate Classic Assets Accounting to New Assets Accounting menu path IMG -> Preparations and Migration of Customizing for Asset Accounting. 12) Assets Account Tables -Actual data of ANEK, ANEP, ANEA, ANLP, ANLC is now stored in table ACDOCA. ANEK data is stored in BKPF. 13) After installation SAP S/4HANA, SAP Cash Management is the only compatible cash management product to be used. The classic Cash and Liquidity Management (Cash Management and Liquidity Planner) is not officially supported in SAP S/4HANA. 14) Bank Account Master Data - After installation of SAP S/4HANA, the old transactions of maintaining house bank accounts are no longer supported. Instead, we need to manage our house bank accounts in the new bank account master data, using either the Bank Account Management Lite or the full version of Bank Account Management (with SAP Cash Management). As a result, before we go live with SAP S/4HANA, we must migrate house bank accounts if there are any. 15) Controlling Tables - Actual data (COEP) and Actual statistical data are stored in 2185026 ACDOCA tables. COEP, COSP, and COSS are replaced with views of the same name, socalled compatibility views.
16) CO Planning - CO-OM planning, P&L planning, and profit center planning are now 2081400 covered by SAP BPC for S/4HANA Finance (formerly known as Integrated Business Planning). If we don’t want to use BPC, still we can use FL-GL and CO-OM planning after implementing modification indicated in the OSS Note. If we want to use BPC decision needed concerning scope of existing planning processes, requirements for plan/actual reporting and ability to use delivered business content for SAP BPC for S/4HANA Finance. 17) Activity-Based Costing (CO-OM-ABC) using delta versions is not available in SAP S/4HANA. Delta versions in general are not available in SAP S/4HANA, so the option to use Parallel Activity Based Costing (setting in the controlling area) is no longer available. Activity-Based Costing using version 0 (Integrated Activity Based Costing in the controlling area settings) is still supported. 18) Cost elements become part of the chart of accounts. They are maintained in GL account master data. There is no separate cost element master data maintenance. Account master record includes new field Account Types, which classifies GL master data into various types of accounts. Depending on account types GL master data has attributes. Migration process takes care of migration of GL and cost element master data. As a result of integration / consolidation of GL and Cost element master data, transaction codes those are relevant for creation of master data are not available in S4HANA Fianance. 19) New Trial Balance report displays all posting to all GL account i.e. primary and secondary cost elements. 20) The universal journal (ACDOCA) is the heart of Accounting and includes all Profitability Analysis (COPA) characteristics in order to allow multi-dimensional reporting by market segment. The universal journal includes columns for the standard CO-PA characteristics and all additional characteristics included in an organizations operating concern (up to fifty characteristics).
2117481 – Release Information Note: SAP Simple Finance, on-premise edition 1503. 1968568 – Financials add-on for SAP Business Suite powered by SAP HANA 1.0: Release Scope Information. 2012817 – Financials add-on for Business Suite powered by SAP HANA 1.0: Compatibile Partner Products. 1946054 – Smart Financials package 1.0: Transaction codes and programs – Comparison to EHP7 for SAP ERP 6.0. 2142781 – DataSources 0FI_GL_12, 0SEM_BCS_12 and related ones are not updating delta queue.