ONE 00-Unit 3&4 (Part-1)

Customer is in the Planning Phase to start migration to New GL using SAP New GL Migration service. What are SAP recommendations to install Simple Finance on-premise Edition 1503?. Customer can continue to complete the New GL migration before installing S.Finance Add-On. Customer may go for installing S.Finance Add-On first and then build new functionalities. Simple finance Add-On installation is recommended post completion of New GL migration for the customers who started New GL migration service. Simple finance Add-on installation should be done post completion of New GL migration for the customers who are using classic GL.

What scenarios do not support while migrating from Classic to S/HANA finance?. Implementation of Document Splitting. New implementation of Parallel Accounting. New implementation of Segmental Reporting. Balance sheets at the Profit Center level. Change in Chart of Accounts and Conversion of Chart of Accounts.

Customer is in Analysis & Preparation Phase to migrate to Simple finance. What is correct?. It is necessary to lock posting periods to avoid further asset postings. It is not necessary to lock posting periods to avoid further asset postings. Perform period end closing activities. SAP provided asset accounting special check report. Run reconciliation reports to ensure consistent data. Pre-checks, if Simple Finance can be installed on current system setup. Execute and save financial reports to allow comparison of financial KPI's after migration.

Customer is in Installation Phase to migrate to Simple finance. What is correct?. The steps to install are performed by a system administrator. Creation of the backup tables for totals and index tables. Creation of SAP HANA views, but with the same or different names. New programs replacing old programs, and transaction code links updated where needed.

Which of the following checks, Asset accounting special Check Report performs S/HANA?. All relevant depreciation areas for parallel currencies exist. All periodic postings are posted successfully. Joint Venture Accounting (JVA) is not active. New GL is active. Classic Real estate module is not active. Lease accounting Engine is not active.

Asset accounting special check report validates additional currencies in the preparation phase of migration. True. False.

Customer is in Customization Phase to migrate to Simple finance. What are correct?. Update Ledger Configuration. Verify Accounting Principles. Check Valuation Areas. Update Chart of Depreciation. Update Operating Concern. Update Chart of Accounts.

Customer is in Migration Phase to migrate to Simple finance. What is correct?. Migration of cost elements. Enrichment of data. Migration of line items. Migration of balances. Reconcile and Compare Migrated Data. Finish migration. Migration of Index and Total tables.

Customer is in post processing of Post Migration activities phase to migrate to Simple finance. What is correct?. Test processes in test environment or release productive system. Fill the offsetting account in Fl documents. Migrate House Bank accounts. If using Data Aging, create cold partitions for the backup tables of the indexes.

The authorization object FINS_MIG is Not required to execute Simple Finance On Premise Edition 1503 for migration activities. True. False.

What steps are included in the Migration sequence during Migration Phase?. Start a migration incl. customizing without transports in a separate copy of productive environment. (Step-1). Start migration of development environment. (Step-2). Copy productive environment to test environment and import customizing settings from development environment. (Step-3). Migrate test environment, correct errors directly in the productive environment. (Step-4). Repeat steps 3 and 4 and test new functionalities after a second migration. (Step-5). Migrate productive environment after 2-3 successful test migrations. (Step-6).

The SAP Simple Finance On-Premise Edition 1503 Installation level is at client level. True. False.

As part of migration, classic G/L data is automatically transferred to the new data structures. True. False.

Is it mandatory to initialize valuation differences from currency valuation while migrating from classic GL to Simple finance?. Yes. No. Not applicable.

The following functions are always affected by the migration to Simple Finance from Classic GL: You need to define valuation areas to conduct foreign currency valuation. You still need Reconciliation ledger. You no longer need a separate Cost of Sales (COS) ledger. You no longer need the consolidation staging ledger.

What is correct about depreciation areas and parallel currencies in simple finance?. Every additional currency type defined on the company code a corresponding depreciation area needs to be set up. Number of parallel currencies in FI-AA can be less than number of parallel currencies in G/L. New asset accounting can be activated without parallel currency checks. Parallel depreciation area for each additional currency used in the corresponding ledger of G/L is mandatory.

Enterprise Activation EA-FIN is required for New FI-AA and hence for the Simple Finance On-Premise Edition 1503. What enhancements are provided by EA-FIN?. Accrual Engine. Inter-Company Reconciliation (cross-system). Depreciation Engine in Asset Accounting (since ECC 6.0).

--> What is correct for the Currency valuation from Classic GL to Simple finance?. Field BSEG_BDIFF in open items has to be empty over all years. Valuation differences can be initialized in Simple finance, if not done in classic GL. The new foreign currency Valuation Run after migration has to be in the same reporting period. Initialize valuation differences from currency valuation.

New valuation method is required to initialize stored values (field BSEG-BDIFF) in open items in case of starting with classic G/L. Yes. No.

Postings after installation phase and before/during finishing migration, an error message will occur. The message can be switched from error to information in the test environment but never in a productive system as this will lead to inconsistencies. True. False.

What is correct about document posting in the SFIN migration process?. Normally, document postings are not possible before and during migration process. Document postings are only possible before and during migration process by converting error into information message. Document postings are not possible before and during migration process and error message can not be converted. Document postings are possible before and during migration process without any restrictions.

What is true about SFIN migration preparation phase?. Technical team should check all the technical aspects like programs, table data etc. Technical team is enough for migration phase. Internal and financial auditors involvement may necessary in preparation phase.

--> What are the steps system automatically executed after installation SFIN on premise edition?. System creates backup tables for the total and index tables (*_BCK in FI and *_BAK in CO). System converts Total tables and index tables as views and delete the original tables. System converts Total tables and index tables as views without deleting original tables. It creates universal journal table-ACDOCA. Data transfers from total and index tables to ACDOCA.

What is true about Asset solution in Simple finance?. Client can use Classic Asset accounting and New Asset accounting. Client can use only New Asset accounting. Classic account can be used for Parallel Accounting and New Asset accounting for ledger concept. There is no classic or New Asset Accounting concepts.

--> What is correct about Asset accounting after completion of Technical installation?. Users can post asset transaction in New Asset accounting to correct the errors after Technical installation. It is not possible to post in New Asset accounting after completion of Technical installation. It is no longer possible to return to Classic Asset accounting. Classic Asset accounting exist in the SAP Accounting for technical reasons but can't be used.

What is True about New GL Accounting activation in case of using classic GL?. New GL should not be activated manually. New GL should be activated manually. New GL should be activated automatically. New GL accounting is active by default post installation of SFIN. The Flag for New GL will be automatically activated later on.

What is Correct about Fiscal year variants adoption in simple finance migration?. All controlling areas and co. codes fiscal year variants should be same. Controlling area fiscal year variant can be different than co. code fiscal year variant. There is no fiscal year variant in Controlling area in Simple finance. Classic GL clients can use their existing fiscal year variants as it is, if they use different fiscal year variants. Controlling area and co. codes fiscal periods should be same along with special periods.

What is Correct about Fiscal year variants adoption in simple finance migration?. Controlling area and co. codes fiscal periods should be same along with special periods even though fiscal variant names are different. Controlling area and co. codes fiscal variants, fiscal periods should be same along with special periods. Controlling area and co. codes fiscal variants, fiscal periods should be same and can have special periods.

--> What are the results post execution of migrate general ledger customizing?. The Flag New GL is active will be set automatically in the background. Ledger configuration copied to new Journal entry ledger configuration in the client. Ledger 0L successfully migrated.

Creation of Accounting principles and Valuation areas are mandatory in SFIN concept. Yes. No.

What is correct customizing sequence to use ledger approach?. Ledger->Ledger Group->Accounting Principle->Valuation area-->Valuation Method. Ledger Group->Ledger->Accounting Principle->Valuation area-->Valuation Method. Valuation area->Ledger Group->Ledger->Accounting Principle. Accounting Principle->Valuation area->Ledger->Ledger Group.

What are true about ledger approach?. Valuation areas are linked (assigned) to Valuation method. Accounting principles are linked (assigned) to Valuation areas. Ledger groups are linked (assigned) to Accounting principles. Valuation areas are linked (assigned) to Accounting principles. Ledgers are linked (assigned) to Ledger groups.

What is the correct sequence configuration of Journal entry ledger?. Ledger creation-->Co. code assignment-->Accounting principle assignment. Ledger creation-->Ledger group-->Co. code assignment-->Accounting principle assignment. Ledger creation-->Co. code assignment-->setup Parallel currencies (if required)-->Accounting principle assignment. Co. Code-->Ledger setup-->Accounting principle assignment.

The Journal Entry Ledger (0L) must always be assigned to CO Version 0. Yes. No.

What is Document Type Mapping Variant?. It is used to identify document types for CO transaction postings. It is used to split CO transaction postings as per document splitting logic.

What is correct about document types mapping variant and its functionality?. It is used to assign the document type for postings in Controlling. Doc types can be specified at Co. Code level or CO Business transaction level. You can also enter document type for CO re-postings, if required. Cross company can have separate document types.

Is default ledger group mandatory to assign for postings in CO?. Yes. No.

When no ledger group is entered in Controlling transactions, all ledgers are updated in table ACDOCA (exactly as for Fl transactions). True. False.

--> What options are available for determining the Offsetting account determination type?. Display offsetting account if clearly specified. Always display offsetting account with the highest amount. Always display offsetting account with the lowest amount. There is no special provision provided for offsetting determination in SFIN.

Migration of balances is always co. code and controlling area specific?. Yes. No.

--> What is correct about migration of balances in Simple finance?. Setup source ledger, company code, year, and target ledgers for migration of the balances. The source ledger can be any ledger. Source ledgers can be verified in FAGLFLEXT for New GL and GLT0 for Classic GL. Source ledgers can be verified in FAGLFLEXT_BCK for New GL, and GLT0_BCK for Classic GL.

Customer implemented classic GL in 2006 and migrated to New GL in 2010, and now wanted to migrate to simple finance. What source ledger you configured for migration of balances to ledger 0L?. Source ledger 0 for Year 2006, and Source ledger 0L for Year 2010. Source ledger 0L for Year 2006, and Source ledger 0L for Year 2010. Source ledger 0L for Year 2010.

--> What consistency check of General ledger settings performs in Preparation phase before Migration phase. Currency conversion settings for ledger/Company assignment on the system level. Currency conversion settings for ledger/Company assignment on the client level. Postings are possible or not in General ledger in preparation phase. All the configured settings of the general ledger (FI, CO, ML, FI-AA) are checked again for readiness towards migration.

What is the sequence of New Asset accounting activation at very high level?. Charts of depreciation Migration-->Preparation and Pre-Check-> Customizing New FI-AA-->New posting logic Activation. Preparation and Pre-Check--> Customizing New FI-AA-->Charts of depreciation Migration-->New posting logic Activation. New posting logic Activation-->Preparation and Pre-Check--> Customizing New FI-AA-->Charts of depreciation Migration.

--> Customer is in Customization Phase to migrate to Simple finance. What is not correct?. Update Ledger Configuration. Verify Accounting Principles. Check Valuation Areas. Update Chart of Depreciation. Update Operating Concern. Update Chart of Accounts.