SAP Hana Finance Interview Questions And Answers

11. Is it a mandate to run AFAR?
Answer: Any changes required to be made to an asset also requires the plan depreciation values to be revised. During customizing changes is the only period when you still need to run AFAR.

12. What is the most essential assist that SAP Simple Finance does?
Answer: SAP Financial and Controlling module (one of the center modules of SAP from its R/2 days) is a virtually advance presenting with high-quality width and profundity. (Company)SAP Simple Finance offers extreme in-memory-reporting that takes out the limit between (B/W) controlling and cash related reporting, incorporating arranging capacities and enhancing liquidity examination. PWC can bolster the execution of SAP Simple Finance to Finance work flip into a proper enterprise accomplice.

13. Do you have any idea about the transformation rules?
Answer: These are basically the rules which are responsible for managing the source table. All the tasks that are performed on the table depend largely on these set of rules and regulations. A few of these rules are also applicable while handing some replication processes.

14. Why is technical clearing GL account used?
Answer: The new Asset Accounting is extremely flexible as far as its architecture is concerned. Which means that going forward by virtue of utilizing both the approaches of ledger and the accounts, you should be able to parallel work on the valuations of your assets by virtue of utilizing both the approaches of ledger and the accounts.

It is not a mandate now to use the depreciation area 01 for the same. Now the leading valuation can be logged in any of the depreciation area. Both the values of the parallel valuation in real time as well as the actual values of the leading valuation on a real time basis are posted by the system. This results in posting of delta values which is substituted; which refers to the delta depreciation areas and that is not required.

New Asset Accounting enables the posting on a real time in all valuations, which is also applicable for all accounting principles. Through this, the tracking the postings of all valuations is made possible without considering the postings of all the leading valuation, which is quite similar to the case in classic Asset Accounting.

For successful implementation of these features, the architecture had to be modified in such a way that the positing is done for asset accounting of each valuation in a separate document. Therefore, only specific postings are made for certain accounting principles. In technical language, we do ledger-groups specific postings.

In the accounts payable and accounts receivable which are also known as the operational part, the value for each accounting principle is always the same and does not differ. Hence in the operational part postings which are considered valid for all accounting principles are only performed. In this technically only those postings are performed which do not specify the ledger-group.

For dividing the business process between an operational and a valuating document a need for establishing the “technical clearing account for integrated asset acquisition”, arose.

The vendor invoice which constitutes a part of the operational side the system ideally posts a document which is valid for all accounting principles as against the technical clearing account for integrated asset acquisitions. The system generates a ledger-group-independent document for a technical perspective.

For each valuating part (asset posting with a capitalization of the asset), the system generates a separate document that is valid only for the given accounting principle. This document is also posted against the technical clearing account for integrated asset acquisitions. From a technical perspective, the system generates ledger-group-specific documents.

It is imperative to look from the view point of a specific accounting principle. As Per, the accounting Principle, both the operational document as well as the valuation document are balancing to zero.

15. What is the use of Persistence layer in SAP HANA system?
Answer: Persistence layer provides inbuilt mechanism for disaster recovery in HANA system. It ensures that database is restored to most recent state in case of a system failure.

Persistence layer also manages data, transaction and configuration logs and backup of these files. Backups of data and log files are performed at save points and is normally scheduled every 5-10 minutes.

16. What is the use of parameters and variables in Semantic layer?
Answer: Variables are used as an explicit SQL filter directive for view consumers to filter the view data, based on attribute column values specified in variable UI prompt of a BI Client. When you go to data preview, variables allow users to pass the value of attribute defined in the variable.

17. Do you still have the number of characteristics limitation to 50 in COPA?
Answer: Some of the interfaces in CO-PA still check that you are not sending more than 50 characteristics, so SAP still recommends that you limit your operating concern to 50 characteristics. Nevertheless since each of the characteristics becomes a field in the universal journal when you come to build reports you can use attribute views to determine additional fields for example, the material.

18. Can I just increase the memory of my traditional Oracle database to 2TB and get similar performance?
Answer: You might have performance gains due to more memory available for your current Oracle/Microsoft/ Tera data database but HANA is not just a database with bigger RAM.

It is a combination of a lot of hardware and software technologies. The way data is stored and processed by the In-Memory Computing Engine (IMCE) is the true differentiator. Having that data available in RAM is just the icing on the cake.

19. What are the main advantages that attract customers to migrate to SAP S/4HANA?
Answer: The main vision and approach of the SAP are to support customers survive simply in the digital world. In order to deliver this mission, SAP S/4HANA redefining how enterprise software makes value. S/4HANA is mainly designed to power instant value across the business and industry lines with the superior sophistication – Simplicity.

Let us explore the advantages of Simple Finance from the point of business value.

SAP S/4HANA makes the unique chance to redefine business models and power new profits in addition to revenues. With the Simple Finance, companies can easily link to devices, people as well as business networks to present additional value to their clients on any channels. Hence, offers the following benefits:

Big Data and Internet of Things (IOT)becomes accessible to any kind of business.

Companies can simplify their approach, power them in a real world environment and alter them as per their requirement in order to gain new proficiencies. That is, there is no further requirement for the batch processing.
Business users can receive a vision of any kind of data from anywhere, including execution, planning, simulation, and prediction.

Let us explore the benefit of Simple Finance in the view of IT value:

The unique chances created by the SAP S/4HANA simplify the landscape. In addition, support condenses Total Cost of Ownership (TCO) with SAP S/4HANA.

Companies can now lessen their data footprint as well as a task with huge data sets in the seamless system (for instance, CRM, ERP, SCM, SRM, PLM co-deployed) in order to save costs of hardware, the cost of operation as well time.

It also made innovation very simple with the open platform (that is none other than SAP HANA Cloud Edition) in order to power advanced applications like recommending, predicting and simulating while protecting standing investments.

Business users can influence simple as well as role-based experience depending on current design principles that increase training efforts when raising productivity. The simple configuration of the SAP S/4HANA also supports customer by modeling the system.

Enterprise gain opportunity of deployment such as On-Premise, Cloud, and Hybrid to power rapid time-to-value.

20. What is Transport Request?
Answer: It’s a kind of a collection of changes that are made in the development system. The information pertaining to the type of change, the purpose of transport, request category and the target system are all recorded. It is also known as Change Requests.