Index tables removed Tables removed esis seers FAOLFLEXA tex Got npr nt me sas ne ct Gn wer Recetas 8810 nets NEA rete SAD ae Can (ae ew) nae aaa 88K necro ry an Bax se ae nr esi ne Ot and FAGLBSIS amt Othe wt FAGLBSAS han rot Aw Gt(hewsm) Aggregate tables removed cur me Nae ours Sener ea Papen Comsaon FAGLFLEXT tw one etn Knct ote mie ae tet uct nde ran rates tem Kn Coton mae ttn) Los ee ma ea tr es coss cm tr mon Po cose cmt Een eg There are rare cases, where entries in ACDOCA are written without a respective document header (for example, carry forward, corrections in migration), These entries do not represent standard business processes. ‘The corresponding line items have artificial document numbers beginning with letters, for example, ‘A’. ‘There is 6 digit field for line item numbering and 23 digits for currency fields. Data for COEP, FAGLFLEXA, ANEP, MLIT, and so on, is stored directly in ACDOCA. BSEG is maintained, as it was earlier it is not affected by the new architecture. BSEG is still limited to 999 lines per document but you can summarize those lines and have up to 999.999 analytically at the highest granularity directly in ACDOCA. ‘Transaction apps offer task-based access to tasks like change, create, display (documents, ‘master records), or entire processes with guided navigation Analytical apps provide insight to action, they give you a visual overview of complex topics for monitoring or tracking purposes. Factsheets give you the opportunity to search and explore your data. They provide a 360 degree view on essential information about an object and contextual navigation between related objects.In the SAP Fiori theme designer, you can design custom themes for the launchpad. For example, you can do the following: + Change font color + Change background color + Add images + Assign a new theme to users In SAP Fiori launchpad designer, you can do the following: + Configure tiles for static app launchers, dynamic app launchers, and to configure the target mapping. + Create preconfigured groups and catalogs for the launchpad home page, for assigning to users. + Transport configurations, correction request packages, or the customizing workbench. Figure 30; Migration SAP S'4HANA FinanceMigration to Accounting on SAP HANA from a classic G/L setup does not support the following scenarios: + Implementation of Document Splitting + Balance Sheets at the Profit Center Level © Migra from Special Purpose Ledger to New General Ledger Accounting + New Implementation of Parallel Accounting + New Implementation of Segment Reporting + Implementation of the Ledger Approach for Parallel Accounting + Change in Chart of Accounts and Conversion of Chart of Accounts + Inclusion of Customer Fields + Transfer of Quantities to New General Ledger Accounting Note: > If you have started or are planning to start a migration to new G/L using the SAP General Ledger Migration Service, we recommend that you complete the new G/L migration project before installing the SAP S/4HANA Finance add-on. The new architecture does not support the following features (and vice versa): + Joint Venture Accounting (JVA) (officially released for ledger-solution via Business Function as of EhP6) This feature may be supported in a future support package. See SAP Notes 2199682 and 2137314. + Lease Accounting Engine (LAE) + Real Estate Classie (RE Classic) + Public Sector Management - Funds Management (PS) ‘M) using requests, Itis necessary to check if new Asset Accounting can be used with installed industry components, + Application Link Enabling (ALE): transfer of assets + Transaction Post transfer between depreciation areas (ABU)