Asset Accounting under in SAP Accounting on SAP HANA. New Asset Accounting is the only asset accounting solution. Classic Asset Accounting is still available. Configuration and activation is on the client level. Configuration and activation is on the company code level. Both multiple valuation approaches are possible: Ledger Approach and Account Approach. Usage of the new Depreciation Calculation Engine is mandatory (based of extension EA-FIN).
Actual items under Assets Accounting in SAP Accounting on SAP HANA. Actual data of ANEP, ANEA, ANLP, ANLC is now stored in table ACDOCA. ANEK data is stored in BKPF. Header data stored in ANEK. Compatibility views FAAV_<TABLENAME> are provided to enable non-disruptive reporting on old tables. After migration, access to the content of old tables is still possible via views FAAV_<tablename>_ORI.
Non-actual items under Asset Accounting in SAP Accounting on SAP HANA. Statistical Line Item in Asset Accounting (for example, calculation for tax purposes) are now stored in table FAAT_DOC_IT. Planned Depreciations and Revaluations (previously ANLP and ANLC) are now stored in FAAT_PLAN_VALUES. Year-dependent attributes for depreciation are now stored in FAAT_YDDA.
The Universal Journal integration provides the following benefits under SAP HANA for Asset Accounting: No redundancy in data storage. Reconciliation between G/L and AA is ensured by design. No reconciliation step in financial close required. All non-statistical items are updated as Universal Journal Entries. Reporting for previous fiscal years is not possible after migration. Transparent assignment of depreciation area to accounting principle. Depreciation posted with all details: accumulated depreciation and depreciation cost by asset.
The simplification of Posting Logic provides for Asset Accounting under SAP HANA, the following benefits: Independent and complete depreciation areas of equal power Each depreciation area per valuation necessary. No further depreciation areas (Delta areas) necessary to portray a parallel valuation. Simple close, fast close, soft close. Transparency throughout the period. Asset balances in real time - APC posting run no longer required. Plan values in real-time - updated with every master data change and every asset transaction. Fast depreciation posting run due to simple processing logic, new data structures and parallel processing Posting to different periods not possible (Restriction: The beginning and end of FY must be equal). Elimination of reconciliation steps.
With regards to the Posting Logic in Asset Accounting under S/4 HANA.
For an integrated asset acquisition posting, the system divides the business transaction into an operational part a valuating part.
Only relevant accounting principles are represented on the asset (or on the asset class) by their corresponding depreciation areas. Yes No.
If a certain accounting principle is not represented on the asset by depreciation area, which posts APC online to general ledger, the posting is re-directed to Account for Operating Expense. Right Wrong.
If no accounting principle is represented on the asset by an area, which posts APC online to G/L, the system issues an error. This error notification can be changed into a warning, in which case the statistical areas in FI-AA are updated. Right Wrong.
For year-end closing for Asset Accounting: there is no separate balance carry forward needed in asset accounting there is separate balance carry forward needed in asset accounting the general balance carry forward transaction of FI transfers asset accounting balances by default. The most current planned depreciation values is calculated automatically for the new year after performing the balance carry forward.
The determination of the depreciation values of an asset and the posting of depreciation expense takes place in the system asynchronously: Correct Incorrect.
Which of the following customizing steps and checks are required for New Asset Accounting? Check and create accounting principles and ledger groups. Assign accounting principles to ledger groups for both approaches: (Ledger Approach and Account Approach) Chart of Depreciation adaptation. Account approach: Define Asset Balance Sheet Accounts of Parallel Valuation as Reconciliation Accounts. Define Technical Clearing Account account for integrated asset acquisition.
In Asset Accounting (New): The system must ensure that all ledgers in which the company code updates its balances in the general ledger are also updated via Asset Accounting. For every additional currency type defined on the company code, a corresponding depreciation area must be set up.
In New Asset Accounting: All depreciation areas representing the same accounting principle are assigned to the same accounting principle (and ledger group). Assign an accounting principle to each depreciation area, even to non-posting depreciation areas or to delta depreciation areas that are only for reporting. The accounting principle can be initial (blank). The same accounting principle can be assigned to several depreciation areas, as long as the areas represent the same valuation.
It is possible to indicate a different document type to be used by the system for the automatically generated accounting principle specific documents in asset accounting on the client level. Yes No.
For an integrated asset acquisition posting, the system divides the business transaction into an operational part and a valuating part. Which part posts to all ledger groups? Choose the correct answer. Operational part (technical clearing account against vendor invoice) Valuating part (asset against technical clearing account).
Which statements of the following statements about the integration of asset accounting tables in the universal journal are true? Choose the correct answers. No redundancy in data storage. Reconciliation between G/L and AA is necessary. No reconciliation-step in financial close. Statistical items are updated as Universal Journal Entries. After migration, reporting for previous fiscal years is not possible. Planned depreciations and revaluations are now stored in ACDOCA.
Which of the following reports are obsolete and deleted? Choose the correct answers. Periodic APC postings: RAPERBxxxx Post depreciation: FAA_DEPRECIATION_POST Reconciliation postings: RAABSTxxxx Fiscal Year Change: RAJAWEOO Post depreciation: RAPOSTxxxx.
With embedded analytics in SAP S/4HANA, everything is on the same technical stack and uses the same user interface. This structure improves the time to customer (TCO) and helps the user to be more efficient. The embedded analytics are available inside the business processes, making the processing more efficient. The simplified data model reduces the redundancy of data and so more space is available to keep a longer data history. The simplified data model reduces the number of tables, making it easier to create Virtual Data Models.
SAP S/4HANA blends transactions and analytics allowing operational reporting on live transactional data. True Wrong.
Match purpose with SAP solution provided by Data Consumption Tools under S4 HANA. Discovery and analysis - Discover. Predict. Create:
• Discover areas to optimize your business.
• Adapt data to business needs.
• Tell your story with beautiful visualizations. Dashboards and apps - Build engaging experiences:
• Deliver engaging information to users where they need it.
• Track key performance indicators
and summary data.
• Build custom experiences so
users get what they need quickly. Reporting - Share information:
• Securely distribute information
across your organization.
• Give users the ability to ask and
answer their own questions.
• Build printable reports for
You want to provide your analysts with a tool for powerful visualizations and exploration. Which of the following would you recommend? SAP BusinessObjects Web Intelligence. SAP Lumira. SAP Crystal Reports Enterprise.
Using SAP Lumira, which of the following can you create? Analytic Views. Datasets. Stories. Universes.
Central Finance offers a non-disruptive step towards system consolidation. It helps companies report on financial figures sourced from same SAP systems. Source systems must be running on New G/L. Source systems may have different customizing settings and diverse master data such as Chart of accounts, Controlling Areas, Operating Concerns, Material Numbers, Product Hierarchies, and so on. Reposting through the Accounting Interface to a Central Finance system harmonizes data but also retains line item-based detail.
A Central Finance instance can only be established on-premise. Right Wrong.
Through SLT there are three interfaces that feed data from the source systems into the Accounting Interface of the target system: An interface for reposting FI/CO postings. An interface for reposting CO postings. An interface for replicating certain cost objects.
SAP Cash Management powered by SAP HANA has three major components and are part of Cash and Liquidity Management. Cash Operations. Liquidity Management. Bank Account Management. Electronic Bank Statements.
SAP Cash Management powered by SAP HANA provides the major functionality of centralized bank account management, daily cash operations, cash position, liquidity forecast, actual cash flow analysis, and rolling liquidity planning. The whole solution provides an instant insight by leveraging SAP HANA to the end users as part of the suite. It provides intuitive user experience to support different devices like laptops, iPads, and smartphones. The solution can be deployed on-premise only. The solution can be deployed in cloud or on-premise.
SAP Cash Management powered by SAP HANA Benefits: Bank Account Management Cash Operations Liquidity Management New Fiori user interface, and
KPI cockpit Integrated with: .
By using Bank Account Management, Customers can also manage the life cycle of bank accounts, for example, opening bank accounts, changing,
reviewing and closing bank accounts. The bank account master data is no longer configured - that means the master data for the banks account can be fully changed by the business users instead of the seeking support from IT colleagues in the future. The customer has a centralized bank account management platform to manage all the bank accounts within the company especially for the heterogeneous system landscapes comprising of SAP and non-SAP systems.
In cash operations, it provides short term cash position analysis from the same application. the Cash Manager can make or track bank transfers directly. the Cash Manager can not make or track bank transfers directly.
In Liquidity Management, it provides mid term and long term liquidity forecasts with dimensions for analysis of liquidity and actual cash flow analysis to identify the use and source of actual cash movements. True False.
Fiori (a HTML5 user interface) and the KPI cockpit - SAP Smart Business for Cash Management record. This solution is aimed at manager who perform high-level analysis. The solution is also integrated with FI, SAP Fiori, BCM and IHC components. if you perform transactions in the TRM component, the cash relevant information is created immediately in the cash management site and is displayed in the cash position. if you perform transactions in the TRM component, the cash relevant information is not created immediately in the cash management site and is displayed in the cash position.
Functions of Centralized Bank Account Management under Cash management powered by SAP HANA: Plenty of attributes reflecting controls on both bank and company sides are provided. Customers also have the flexibility to extend attributes according to their own special requirements. The solution provides bank hierarchy to reflect the bank structures. There is also a free style bank account group in which to group the bank accounts according to different views of the end users. The signatories maintained in the new Bank Account Management master data can be integrated with BCM payment approval simplifying signatory management. For the approval process for opening, changing, and closing bank accounts, workflow to manage the approval process in the company where customers can change or define the workflow according to their requirements. The bank accounts review process helps the customer to review bank accounts yearly or quarterly. Upload and the Download Bank Accounts to migrate of bank accounts or to perform mass change of bank
accounts. All bank accounts can be downloaded into an Excel file, where the change can be performed. The Excel file can then be uploaded to the system. Bank Account Management BAM Lite for Simple Finance customers who do not purchase the SAP Cash Management powered by SAP HANA, provides the basic functionality of maintaining bank accounts including house bank accounts. Initiating bank transfers and payments.
Functions of Cash Operations under Cash management powered by SAP HANA. Cash Operations for the day to day management of the corporates working capital. Monitoring status of incoming bank statements. Preparing a daily forecast of cash receipts, disbursements and expected closing balances. Overseeing bank risk. Initiating bank transfers and payments. Approving and monitoring payments. The bank accounts review process to review bank accounts yearly or quarterly.
Functions of Liquidity Management under Cash management powered by SAP HANA. Complete lifecycle management of Rolling Liquidity Planning. System provides reference data to help Cash Manager to plan the liquidity precisely and easily. Functionality to plan hedging of operating activities for foreign currencies. Plan/Plan, Plan/Forecast and Plan/Actual comparisons. Overview suspicious plans. Liquidity Forecast. Cash Flow Analysis.
The new Cash Management provides a Rolling Liquidity Plan function with an embedded planning framework. This means: customers do not need to set up a separate and standalone BPC server for planning, nor is it necessary to set up the ETL tool to regularly import the master data and transactional data into the planning application. with the embedded liquidity planning, master data and transactional data are retrieved real time directly from the system.
Bank Account Management is a brand new function in SAP Cash Management powered by SAP HANA. In classic Cash Management, there are House Bank and House Bank Account. However, they are configurations and there is no equivalent function for cash manager to manage bank accounts as master data. In Bank Account Management, cash manager can manage bank accounts as master data.