TESTING

Unit Testing
When you test every single document is called unit testing.
String Testing
One transaction full activity is called string testing . For example Vendor invoice, goods received and vendor
payment.
Integration Testing
It is purely with other modules and we have to check whether the FI testing is working with other related modules
or not.
Regression Testing
Testing for whole database. Bring all the data into another server and do the testing is called regression.
UAT
When we test any particular document with the user and if it is ok immediately we have to take the signature on
the document, which is signed off and can be forwarded to the immediate boss. There are some steps to be
followed when we go for user acceptance testing.
Transaction Script Writing Expected Results Compare with Actual Results
TPR (Transaction Problem Reporting)
While doing the user acceptance testing if we get any problems then there are some methodologies to be
followed according to the companys policy and normally as a tester we always need to write on Test Script itself.
Key Features
Understanding the business scenarios
Organization Structure to incorporate the tune of the script.
Preparation of test scripts
Execute and record results to see if it is fine before going to approval.
Make changes to your test script if required.
What is Test Script (Scenario Testing)
Header Data
Step in Process
Transaction Code / Program (FB60)
Menu Path
Description
Field Data and actions to complete
Expected Results
Actual Results
TPR
Closing Period
F.19 Clearing GR/IR Account
F.13 Adjustments GR/IR Account

Using of these above two accounts will help us in clearing the balances and adjustments to those respective
clearing accounts so that the GR/IR account will be zero balance and the balances will appear in respective
reconciliation accounts accordingly the balances will be carried forwarded to next fiscal year.
GR/IR Clears the following Documents
GL Document
Customer Documents
Vendor Documents
Assignment Field is important in any document (ZUONR), Amount (DMBTR)
Foreign Currency Valuation
Lowest Value Method, If we are in loss then only we will account for it.
GL Accounts which are important in Testing
Enjoy Transaction - FB50
Normal Transaction - FB01
Document Parking - FV50
Post with Clearing - F-04
Incoming Payment - F-06
Outgoing Payment - F-07
Document Related
Reset Cleared Items - FBRA
Parking Document Posting - FBVO
Reversal Documents - F-14
Company Code Clearing A/C
(Trial Balance purposes) reversal - (FBUB)
Clearing Account
Partial clearing Invoice - 100 - Open Item
Paid - 70 - Open Item
Balance - 30
In Partial Clearing you can see 100 and 70 are cleared line items and 30 as balance and if it is in Residual you
can only 30 as balance as it creates new line item and you cant see the other cleared line items.
As no company will use residual clearing as it affects on ageing reports.
Open Items in Foreign Currency in all Modules GL/AP/AR - F.05
Master Data
Company Code
Currency
Only Balances in local currencies
Reconciliation Account Type

Year End Scripts

Re Grouping Receivables / Payables - (F101)
Bad Debts Provisions Scripts
We assume that the customer has not paid at the end of the year you doubt whether this receivable will ever be
paid. So you make a transfer posting for the receivables to an account for individual value adjustments using
special GL Indicator E and Transaction Code F-21
Carry forward Balances
Sub Ledgers and General Ledger balances to be forwarded to next Fiscal Year
Accounts Payables
Vendor Down Payments
Invoice
Parking
Reversal
Outgoing Payments
Automatic Clearing
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
Accounts Receivables
Customer Down Payments
Invoice
Parking
Reversal
Incoming Payments
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
- See more at: http://www.saptechies.org/guide-for-testing-sap-financial/#sthash.W0fbU9S2.dpuf

SAP Testing overview

Informative performance test results rely upon sound test development. Each of the following
stages contributes to generating meaningful test results:
Test creation. You create your test by recording a session with the SAP GUI client. Typically, the
recorded session starts when you log on to the SAP R/3 server. You then interact with the
application in order to produce a relevant performance test, and the session ends when you log
out. The recorded session is split into transactions and SAP screens. Response time
measurements and verification points are automatically added to transactions and SAP screens.
Test editing. After recording, you can edit the events in each transaction and SAP screen. With
the SAP Protocol Data view, you can use snapshots of the SAP screen to edit the events. You
can replace recorded test values with variable test data, or add dynamic data to the test. You can
also set verification points on field values or window titles to validate that the test behaved as
expected.
Test validation. Before deploying the test, you can run the test manually as a single virtual user
to make sure that the test runs smoothly and produces the expected results in a nominal
environment with minimal server load. You can experience multiple test editing and validation
cycles before your test is robust.
Workload emulation with schedules. When the test runs repeatedly as anticipated, you specify an
execution schedule and user groups to emulate a workload that is generated by a large number
virtual users. You can add SAP batch input tests to the schedule to simulate a heavy load on the
servers while minimizing virtual tester resources.
Schedule execution. You run the schedule, deploying test execution over virtual users that can
be hosted on remote hosts. Each virtual user runs an instance of the SAP GUI client. Response
time results are provided by the SAP R/3 server and recorded. Verification points are checked
and results are recorded.
Evaluation of results. You evaluate the results produced by the tests through the various reports
that are generated during execution. You can also design custom reports.
Introduction of SAP Test Acceleration and Optimization(Sap TAO) :The SAP Test Acceleration and Optimization (SAP TAO) software streamlines the creation and
maintenance of ERP business process testing.
SAP TAO helps QA Specilists to break down applications into components, which can be

Assembled into test cases through a simple interface using drag and drop

Parameterized for flexible reuse, such as reusing a test that has updated data inputs

Maintained easily and inexpensively, even when screens, flows, or service packs change.
Testing Optimization Benefits:Automated testing with SAP TAO maximizes:

Testing Deployment
SAP TAO, in tandem with HP Quality Center, dramatically reduces the amount of time required to build
and execute test scripts.

Reuse
SAP TAO eliminates the need to create new tests whenever a component changes. If one component
changes in a group of tests, just replace that component and then re-consolidate the tests.

Maintenance
SAP TAO allows you to record component parameters. SAP TAO provides a Microsoft Excel
spreadsheet to save parameters for reuse and maintenance. You can also move components from HP
Quality Center to SAP TAO for additional backup possibilities.
Process Testing with SAP TAO
Below Process describes how to test a simple business process with SAP TAO and HP Quality Center.
It assumes that you can access a SAP back-end server that executes the business process transactions
you are testing, access to HP Quality Center, and a properly installed and connected SAP TAO Client on
your desktop.

1. Discuss the process flow with the subject matter expert.

2. Create a business process test case with detailed steps.

3. Run the steps manually within the test application to make sure the application generates without
errors or warning messages.

4. Open HP Quality Center to view the list of your selected components.

a. Drag and drop the transactions in the order that they occur in the business process.

b. HP Quality Center includes a list of common screen commands, such as Open, Enter, and Exit. Move
the screen commands using drag and drop as needed.

5. Parameterize the data in the Excel spreadsheet or the HP Quality Center database.

6. On SAP TAO, consolidate the data into a single component that consists of the transaction code and
screen operations.

7. In the HP Quality Center, create a second business process script using the single component.

8. Execute the test script and review it for any discrepancies.

9. Save the components in a directory that you can easily access when you need to update a screen or
a transaction.

SAP Testing Interview Questions and Answers

What are SAP Testing Services

To mitigate business risk and to ensure expected results in the complex SAP environment
during the entire SAP solution lifecycle it is imperative to conduct sufficient quality testing.

TSAP testing services uses eCATT as the functional test tool in SAP applications. Some of the
testing services offered are:
Application testing
Performance testing
Regression testing
Testing strategy and management

What is SAP Testing ? Different Types of Testing?how it is different from application testing
SAP Testing is same as manual testing but here the applications are SAP R/3 and Enterprise
portal. Whenever there is change in R/3 and Portal and You need to design test cases
according the change request and test the application.
UAT means USER ACCEPTING TESTING. Suppose end user raised an issues that we solved
and send to end used it is working fine. then we get confirmation from him that it is fine. that is
call UAT.
UNIT TESTING - This is done by developer and anyone who did any customizing or any code
to ensure what they did is working properly
INTEGRATION testing - Done by tester by developing some scenarios which are most unlikely
and get the result to ensure the integration is correct
Apart from that, regression testing, functional testing and other cross functional testing are
there done by testers
In realization phase, unit testing are done by developers After unit testing, Integration testing
and other testing are done by testers/functional depending upon the object to test.
Testing usually follows two paths. Firstly, System Integration Testing (SIT) which is performed
by the SAP team in the development client, and secondly User Acceptance Testing (UAT)
which is performed in the QA client after transport from the development client. UAT is
performed by end users or the testing team.
Unit Tests are defined and performed by developers. A process consists usually of several
functions. Each of this function usually consists of "sub-functions" corresponding to a single
method or a group of methods (if you are developing OO-based).
Unit Tests could be described as white-box tests whereas a normal tester (which should be not
identical to the developer) will test entire functions (black-box tests).
During the entire life cycle of a SAP solution, it is necessary to test the functions and
performance of your solution. With the SAP Test Workbench, SAP provides you with an
environment for all test phases, which you can use for testing in the following cases:
Implementation of SAP solutions
Integration of new components and business scenarios
Customer developments
Function tests

Integration tests with other components

Upgrades, regression tests
Importing support packages
Integration
Features
Test Preparation
Creation of manual and automated test cases
Management of manual and automated test cases
Creation of test plans
Definition and management of test series
est Execution
Execution of mass tests using Extended Computer-Aided Test Tool and Computer Aided Test
Tool
Integration of test cases and test scripts of non-SAP providers
Assignment of work lists (test packages) to individual testers
Test Evaluation
Permanent overview of test progress and test results
Complete documentation of test processes in the test plans (test cases, test case descriptions,
test results, test case notes, error messages)
Detailed tabular and graphical evaluation of all test plans
Export of test results to Office applications
Message processing
Testing usually follows two paths. Firstly, System Integration Testing (SIT) which is performed
by the SAP team in the development client, and secondly User Acceptance Testing (UAT)
which is performed in the QA client after transport from the development client. UAT is
performed by end users or the testing team.

What is GUI Testing of SAP Applications

Test the functionality of your SAP R/3 applications. In minutes you'll understand the power
behind Rational Robot's Object Testing as you quickly record tests that verify:
Properties of SAP screen controls.

Values in application fields.

Integrity of your business process flow.
Robot lets you record functional tests against your SAP R/3 application, regardless of R/3
hardware platform or database server

What is Load Testing SAP Applications?

In executing your business transactions on the Web interface, through integration with the
powerful SAP engine, the SAP WAS system creates a highly complex dialog between the client
machine and the server.
This complexity is not visible to the user or those in charge of deployment, but it is an important
factor when it comes to middleware.
Your load testing tool's ability to take into account the specific nature of this rich and complex
dialog is an essential pre-requisite for performance testing SAP applications. The tool must be
capable of automatically and natively handling SAP Web Application Server (WAS) in order to
efficiently build scripts that cover all your test cases.
Without fully compliant SAP WAS support, you cannot carry out the full range of tests and run
the risk of deploying an application whose behavior under load has not been validated properly
- with possibly damaging consequences. These could include slow-downs for users, or even
blocked access for some users in high load periods, putting in jeopardy not only the success of
the project, but also the company's entire economic foundations, due to the critical importance
of its business services.

What is Testing Orienting Applications?

Software Testing is more Oriented to Detecting the defects or often equated to finding bugs.
Testing is a process of executing a software system to determine whether it matches its
specification and executes in its intended environment under controlled conditions. The
controlled conditions should include both normal and abnormal conditions. Testing should
intentionally attempt to make things go wrong to determine if things happen when they
shouldn't or things don't happen when they should.

What is SAP QA ?
Sap QA: - SAP Application QA involves the entire software development PROCESS monitoring and improving the process, making sure that any agreed-upon standards and
procedures are followed, and ensuring that problems are found and dealt with. It is oriented to
'prevention'.

What is SAP implementation lifecycle?

SAP implementation lifecycle
In the lifecycle of a SAP solution, it is necessary to test the functions and performance of the
solution developed by programmers. Work environment with SAP testing, SAP provides an
environment for all phases of testing, you can use to test in the following cases:
The implementation of SAP solutions:
1) Integration of new components and business scenarios.

2) Client Development.
3) The function tests for all the functions.
4) Integration testing with other components in the integrated environment.
5) Updates/changes regression testing.
6) Import support programs.
Integration Features and Test Preparation:
1) Creation of manual test cases and automated.
2) Management manual and automated test cases .
3) Creation of test plans.
4) Define and manage a series of tests.
Test execution Phase:
1) Test communication with the test tool extended desktop and Computer Aided Test Tool.
2) Integration test cases and test scripts from non-SAP providers.
3) Assign work lists (probes) for individual testers.
Test Evaluation Phase:
1) continuous improvement vision test and test results.
2) Complete documentation of the testing process into test plans (test cases,descriptions of
test cases, test results, notes of test cases, error messages).
3) A detailed evaluation of all test plans in tables and graphs.
4) Export test results of the Office applications.
5) message processing.
Generally testing has two ways, one being, system integration testing, this will be performed by
the SAP development team of the product owner, and the second being, the user acceptance
testing (UAT) is performed on client's team in the client's location. UAT usually performed by
the end user to test the solution is working fine.

Guide for Testing SAP Financial

TESTING
Unit Testing
When you test every single document is called unit testing.

String Testing
One transaction full activity is called string testing . For example Vendor invoice,
goods received and vendor payment.
Integration Testing
It is purely with other modules and we have to check whether the FI testing is
working with other related modules or not.
Regression Testing
Testing for whole database. Bring all the data into another server and do the testing
is called regression.
UAT
When we test any particular document with the user and if it is ok immediately we
have to take the signature on the document, which is signed off and can be
forwarded to the immediate boss. There are some steps to be followed when we go
for user acceptance testing.
Transaction Script Writing Expected Results Compare with Actual Results
TPR (Transaction Problem Reporting)
While doing the user acceptance testing if we get any problems then there are some
methodologies to be followed according to the companys policy and normally as a
tester we always need to write on Test Script itself.
Key Features
Understanding the business scenarios
Organization Structure to incorporate the tune of the script.
Preparation of test scripts
Execute and record results to see if it is fine before going to approval.
Make changes to your test script if required.
What is Test Script (Scenario Testing)
Header Data
Step in Process
Transaction Code / Program (FB60)
Menu Path
Description
Field Data and actions to complete
Expected Results
Actual Results
TPR
Closing Period
F.19 Clearing GR/IR Account
F.13 Adjustments GR/IR Account

Using of these above two accounts will help us in clearing the balances and
adjustments to those respective clearing accounts so that the GR/IR account will be
zero balance and the balances will appear in respective reconciliation accounts
accordingly the balances will be carried forwarded to next fiscal year.
GR/IR Clears the following Documents
GL Document
Customer Documents
Vendor Documents
Assignment Field is important in any document (ZUONR), Amount (DMBTR)
Foreign Currency Valuation
Lowest Value Method, If we are in loss then only we will account for it.
GL Accounts which are important in Testing
Enjoy Transaction - FB50
Normal Transaction - FB01
Document Parking - FV50
Post with Clearing - F-04
Incoming Payment - F-06
Outgoing Payment - F-07
Document Related
Reset Cleared Items - FBRA
Parking Document Posting - FBVO
Reversal Documents - F-14
Company Code Clearing A/C
(Trial Balance purposes) reversal - (FBUB)
Clearing Account
Partial clearing Invoice - 100 - Open Item
Paid - 70 - Open Item
Balance - 30
In Partial Clearing you can see 100 and 70 are cleared line items and 30 as balance
and if it is in Residual you can only 30 as balance as it creates new line item and
you cant see the other cleared line items.
As no company will use residual clearing as it affects on ageing reports.
Open Items in Foreign Currency in all Modules GL/AP/AR - F.05
Master Data
Company Code
Currency

Only Balances in local currencies

Reconciliation Account Type
Year End Scripts
Re Grouping Receivables / Payables - (F101)
Bad Debts Provisions Scripts
We assume that the customer has not paid at the end of the year you doubt whether
this receivable will ever be paid. So you make a transfer posting for the receivables
to an account for individual value adjustments using special GL Indicator E and
Transaction Code F-21
Carry forward Balances
Sub Ledgers and General Ledger balances to be forwarded to next Fiscal Year
Accounts Payables
Vendor Down Payments
Invoice
Parking
Reversal
Outgoing Payments
Automatic Clearing
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations
Accounts Receivables
Customer Down Payments
Invoice
Parking
Reversal
Incoming Payments
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations