Procedure: Migration to S/4HANA~ match various phases to relevant activities: (Start pre-check programs.
Create a blueprint for process redesign and reporting.
Customer-Vendor Integration, Sizing and Custom Code Analyzer.
Perform reconciliation, period-end activities, and gather reporting snapshots). (Install SAP S/4HANA.
The system backs-up index and totals tables automatically). (Customize General Ledger Accounting.
Customize and activate Asset Accounting (new).
Customize Controlling (account based CO-PA) and Material Ledger.
Customize House Bank Accounts and Credit Management (if necessary)). (Migration of financial data -GL/AP/AR/CO/FI-AA/ML/CM,
Migrate House Banks Accounts,
Reconciliation & checks within and after migration and set migration to complete). (Transfer backup table data to historic database area (optional).
Update due dates and offsetting account).
In the project preparation phase, the system activities are as follows: Pre-check if SAP S/4HANA can be installed on the current system setup «Check Customizing Settings Prior to Upgrade to S/4HANA». Run special check report for FI-AA installed. Perform period-end closing activities and financial reporting. Run reconciliation reports to ensure consistent data. Perform S/4HANA customer vendor integration. Open the posting periods. Execute and save financial reports to allow comparison of financial KPIs after migration. Customize code analyzer for simplification list.
A system administrator performs which of the following steps to install SAP S/4HANA: Creates the backup tables for totals and index tables. Replaces the totals and application index tables or redirects them by DDL SQL views, or compatibility views (CDS views). Related data is secured into backup tables. Replaces existing programs with new programs and updates transaction codes where needed.
Customizing for Migration after Installing S/4HANA include the following activities: General ledger: Update ledger configuration, verify accounting principles, check valuation area, and so on. New asset accounting: Customize and migrate all active charts of depreciation. Controlling: Update settings for account based CO-PA. Material ledger: Migrate material ledger customizing. House bank accounts: Update settings for number ranges. Credit management: Migrate customizing if using credit management (FI-AR-CR).
System Steps Executed in Data Migration Phase-The system steps you need to execute at the Data Migration phase are as follows: Migration of cost elements. Migration of material ledger. Enrichment of data. Migration of line items. Migration of balances. Reconciliation and comparison of migrated data. Migration of house bank accounts. Migration of credit management. Set migration as complete and release productive system.
Steps to Complete in the Post Processing Phase-The system steps you need to complete at the Post Processing phase are as follows: Test processes in test environment. Complete post migration activities, for example, fill the offsetting account in FI documents. Create cold partitions for the backup tables of the indexes if using data aging.
The following authorization object is required to execute SAP S/4HANA migration activities. FINS_MIG. S4HANA_FINS_MIG. FINS_S4_MIG.
Which statements are INCORRECT. Migration can be started at any point after all prerequisites have been met. Customer vendor integration is necessary for SAP S/4HANA. The sequence of steps is very important. SAP S/4HANA is installed at the system level. SAP S/4HANA is installed at the client level. Migration can be started at any point in time.
New SAP customers starting with SAP S/4HANA take over their legacy data using other tools. True False.
SAP S/4HANA migration tools only work for existing customers and systems. True False.
You can migrate either directly from classic G/L to SAP S/4HANA or (first migrate from classic G/L to new G/L and from there to SAP S/4HANA, only advisable if you need to implement document splitting and/or parallel ledgers immediately). True False.
What are the High Level System Prerequisites for Migration, choose correct ones. Uses SAP Business Suite. Uses SAP HANA database. Uses SAP ERP ECC 6.0 at least EhP7.
Only one fiscal year can be open in Asset Accounting during migration and the last year cannot be reopened after migration. True False.
Scope of changes in GL Accounting due to Migration to SAP S/4HANA, choose correct statements: Migration can be executed at the end of any year-end. It is more a technical migration. Most errors can not be adjusted by business departments. It is supported by a migration guide and monitor. Changes to coding blocks, external interfaces, security, and so on, are mandatory. Consider whether data archiving makes sense.
Scope of changes in GL Accounting due to Migration from a General Ledger Perspective, choose correct statements: G/L accounting in SAP S/4HANA is different to the new G/L in SAP ERP. It provides the same capabilities as new G/L and leverages existing capabilities. It is further optimized for SAP HANA, for example, universal journal, no totals tables, convergence with CO, and better reporting.
Scope of changes in GL Accounting with respect to classic GL customers, choose correct statements: As part of the migration, classic G/L data is automatically transferred to the new data structures. Existing EC-PCA (profit center), EC-CS (consolidation), and SL (special ledger) functions and features remain. Subsequent optimization (such as adoption of parallel ledger or document split) is always a recommended option and is not possible during migration. Customers already running a migration project to new G.L in SAP ERP should continue this project. The same goes for customers urgently requiring document splitting.
Scope of changes in GL Accounting with respect to classic GL customers, 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 Migration 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.
Functions Affected by the Migration to SAP S/4HANA Foreign currency valuation In new GL / SAP S/4HANA-you need to define valuation areas to conduct foreign currency valuation. The valuation postings are made to the ledger group defined per valuation area. Reconciliation between controlling and financial accounting-The universal journal is updated directly so no reconciliation ledger is needed.
Functions that Can Be Adopted After the Migration, You no longer need a separate COS ledger. You can store the data directly in the leading ledger in new general ledger accounting. a consolidation staging ledger. You can store the data directly in all ledgers (but it is still possible to use for preparation of consolidation).
The first test does not give a good first impression of what the duration will be and the potential setbacks for the migration project. True False.
Preparation Phase for Asset Accounting. Run special check report RASFIN_MIGR_PRECHECK for FI-AA installed. Check if new asset depreciation is active. If not, enterprise extension EA-FIN must be activated. Perform period-end closing activities in asset accounting. Lock asset accounting via posting periods to avoid further asset transactions as RAPERB2000 asset accounting can no longer be used. RAPERB2000 asset accounting can be used after migration.
The following checks are performed by running special check report RASFIN_MIGR_PRECHECK . New General Ledger (new GL) is active (only a warning as it is not a requirement) Joint Venture Accounting (JVA) is active. Lease Accounting Engine (LAE) is active. Classic Real Estate (RE classic) is active. No requests (with reference to assets) are used in Public Sector Management - Fund Management (PSM-FM). All periodic postings are posted successfully: no update terminations. All relevant depreciation areas for parallel currencies exist.
In Preparation Phase of Asset Accounting: which statement are correct with regards to Additional Currency? For every additional currency type defined on the company code, a corresponding depreciation area needs to be set up. Calculate the plan values for depreciation (transaction AFAR). When using the ledger approach with non-calendar fiscal year variant for parallel valuation.
Enterprise extension EA-FIN is not required for FI-AA (new) and SAP S/4HANA. True False.
The following are the main enhancements provided with extension EA-FIN: Accrual engine. Intercompany reconciliation (cross-system). Depreciation engine in asset accounting (since ECC 5.0).
Which statements are correct regarding preparation phase of S4 HANA Finance implementation. Ensure all balances are carried forward for the current fiscal year
(accounts: FAGLGVTR or F.16, Receivables/Payables F.07, Assets: AJRW). For account-based CO-PA, execute delta upload with delta load. Check if GL and CO configurations and currency settings allow an upgrade to SAP S/4HANA Finance or S/4HANA. Program FINS_MIG_PRECHECK (step in customizing) is part of SAP S/4HANA and can be used before installing SAP S/4HANA software. Check for canceled update requests (transaction code SM13).
Are Postings permitted in the system after installing SAP S/4HANA until the end of migration. Yes No.
As a prerequisite of the SAP S/4HANA conversion project, all customers, vendors, and their contacts must be converted to business partners. True False.
Customer Vendor Integration (CVI) ensures that customer and vendor master data tables are updated automatically after a BP is created or changed. True False.
The challenge you face with adoption of the business partner as the single customer or vendor entity is consolidating an often very diverse set of: account groups. number ranges. field assignments. account assignments.
For each number range used for customer and vendor account groups, a number range for business partners also has to be created as long as you want to continue using these intervals. True False.
To allow the customer/vendor numeric numbers to be taken over to the business partner, the numeric intervals of the Business partner number ranges must be set to External initially. Switch back after the successful data synchronization. The numeric intervals of the Business partner must change back to Internal afterwords.
For every customer/vendor account group, a BP grouping must be available. You can only use the same business partner grouping if the customer number is equal to the vendor number in SAP ERP. You can only use the same business partner grouping if the customer number is not equal to the vendor number in SAP ERP.
You need to map the different customer specific values for attributes such as marital status, legal form, legal status, payment cards, industries, number, departments, authority, and so on, of contact persons. True False.
The following mappings are checked, by running check report to ensure all the necessary Customer Vendor Integration (CVI) mappings are done. BP roles are assigned to account groups. Every account group BP grouping must be available. Customer value mapping. Vendor value mapping. Customer and vendor value mapping (BP —> customer/vendor). CVI mapping (check CVI_CUST_LINK / CVI_VEND_LINK vs. KNA1 / LFA1) - post-conversion check. Contact person mapping - post-conversion check.
Which of the following steps are executed automatically by the system during installation of SAP S4 HANA? Create backup tables for the totals tables and index tables in the Data Dictionary that are deleted ( BCK in FI and BAK in CO). Save the totals tables and index tables in backup tables. Keep the original totals and index tables without backup tables. Create SAP HANA views (with the same names) for the totals tables and index tables. Create the new table ACDOCA Universal Journal.
During installation phase of S/4 HANA migration, create backup tables for the totals tables and index tables in the Data Dictionary that are deleted BCK in FI. BAK in CO. BAK in FI. BCK in CO.
After the technical installation of SAP S/4HANA is complete, we need to remember which of the following points? It is not possible to post in Asset Accounting after installation phase using the old logic but can post in new logic. Migration and activation of New Asset Accounting has to be completed. It is no longer possible to return to classic Asset Accounting. Classic Asset Accounting does not exist in the SAP Accounting powered by HANA solution. Balance sheets and account balances cannot be generated anymore (tables are empty).
High Level System View of Migration Sequence: (Start a migration including customizing without transports in a separate copy of the productive environment. This provides an overview of problems and duration). (Start the migration of the development environment. This is the system mostly without transaction data). (Copy the productive environment to the test environment and import customizing settings from the development environment). (Migrate the test environment and correct errors directly in the productive environment). (Repeat steps 3 and 4 and test new functionalities after a second migration). (Migrate the productive environment after 2-3 successful test migrations).
|
