SAP TESTING

MIND-Q

TARAKESH

Role of SAP Consultant In Testing

1. What is the role of Consultant in Testing while implementing the project?
2. What is Unit testing and Integration Testing?
Testing : the core team members along with endusers will test whether the postings done
in SAP is resulting as per the requirements of the organisation. They will test whether
the output documents such as purchase order, invoice document are printed in the
required format and showing the correct data.
Unit testing is refer to the module which are going to implement. SD, MM, FICO etc.
there will be test script based on that testing will be performed.
Integration testing will be cross the modules. MM-SD-FICO for example. Integration
testing is also called SIT ( System integration testing)
Testing mathologies and types: there are 6 types of testings:
1. Unit Testing
2. System Testing
3. System Integration security Testing
4. Performance Testing
5. User Acceptance testing
6. Regression Testing
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we
will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data.
We will not be looking and checking/testing any integration between order and delivery;
delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you
will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and
signoff.
Performance testing is refered to as how much time / second will take to perform some
actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and
not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot
adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed
through the execution of predefined business scenarios, which combine various business
processes. The user test model is comprised of a sub-set of system integration test cases.

SAP TESTING

MIND-Q

TARAKESH

We use different software during testing. Most commonly use are

Test Director: which is used to record requirement, preparing test plan and then
recording the progress. We will be incorporating defects that are coming during these
testings using different test cases.
Mercury Load Runner: is used for performance testing. This is an automatic tool.
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom
program, or interface. the test usually consists of a test data set that is processed
according to the new program. A successful test only proves the developed code works
and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development
(it may follow the technical unit testing) These usually use actual data or data that is
masked but essentially the same as a real data set. A successful test shows that the
development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context
of any other functions that the process, development or functionality will touch or
integrate . The test should examine all data involved across all modules and any data
indirectly affected. A successful test indicates that the processes work as designed and
integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the
entire volume does cause system problems such as network transmission problems,
system resources issues, or any systemic problem, A successful test indicates that the
processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while
running the same processes in the legacy system. A successful test will show identical
results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct
at least one cut over test from the old system to the new and you should probably do
several.
What kind of testings that are carried out in testing server?

SAP TESTING

MIND-Q

TARAKESH

1. Individual Testing ( Individually which we've created)

2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)
The 3 types of testing is as follows:1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
2. Integration testing (where a process is tested that cuts across all areas of SAP).
3. Stress testing (where lots of transactions are run to see if the system can handle the
data)
Tips by: Teresa Pittari, Gregrobinette

What Is Maintaining SLA - Service Level Agreement

What is maintaining SLA in production support?
SLA is an abbreviation for "Service Level Agreement". It means to have guaranteed
reaction or resolving times for incidents (= trouble tickets).
For instance you could have defined the following SLA levels For example:
Gold: Reaction time = 30 minutes, resolving time = 4 hours
Silver: Reaction time = 4 hours, resolving time = 24 hours
SLAs normally are part of a contract between a customer and a service provider.
*Or in details description:*
SLA are Service Level Agreements to resolve the tickets by the market. SLA means
Service Level agreement. It is the service agreement between a Company and a service
provider. For example an IT Organization providing support of SAP / other software /
hardware has a agreement. This can be for example categorized based on criticality of the
incident. High priority incident has to be resolved on 10 hours. Medium priority incident
has a 3 days time to resolve etc
*-- Anu radha
SLA's are nothing but Service level agreements.
These are defined in project preparation phase and client would have made an agreement
with the company for the level of service. The SLA's are applicable in Production as well
as maintanence support projects. For example: if your company follows a ticketing
process(a ticket is nothing but an environment contains complete description of the

SAP TESTING

MIND-Q

TARAKESH

problem which contains Short description, problem, customer contact details, sreen shots
of the error etxc.,) and for each ticket there will be a severity for example business critical
issues or problems may be treated as high or top severitie's. In those case your company
or your team has to deliver the solution to the customer in agreed time limit or otherwise
you might end up missing SLA's.
SLA's has two important time specifications
1. IPRT --- initial problem response time --- this is nothing but time taken to respond to
the problem.
2. PRT --- Problem response time ----- this is nothing but time taken to solve the issue or
problem.
Both IPRT and PRT will be different for different severitie's.
*-- Mahesh

What Are Functional Specification in SAP?

To speak at macro level that is at projet manager or at senior levels. The Functional Spec
(Specification) which is a comprehensive document is created after the (SRS) Software
Requirements Document. It provides more details on selected items originally described
in the Software Requirements Template. Elsewhre organizations combine these two
documents into a single document.
The Functional Specification describes the features of the desired functinality.. It
describes the product's features as seen by the stake holders,and contains the technical
information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area
that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains
in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a
technical description which
a) Ensures that the product feature requirements are correctly understood before moving
into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical
consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any
functionality for the purpose of getting the same functinality designed by the technical

SAP TESTING

MIND-Q

TARAKESH

pepole as most of the times the functionalities according to the requirements of the clients
are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis 3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names 8) Future Impact & Change Assessement
9) Functional Design (Module Wise)
10) Risk Assessement
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Note * This documents are preapared in Vanilla SAP Standards -- Things differ from one
implementation to another, and it always depends on the type of business which is opting
for SAP.
Tips by: Madhuuri, Fahad

Role of a mySAP Functional Consultant

What are the differences between a functional and business consultant?
The difference between Functional consultant and Business consultant are as follows:
1) A funcitonal consultant is able to configure the system unlike business consultant.
2) Functional consultant know more about business process unlike Business consultant.
3) A business consultant will bring business process knowledge and provide it to
functional consultant who in turn used this knowledge to configure the system.
4) Functional consultant has more configuration knolwledge then Business
consultant.
*-- Rocky
The responsibilities of a support consultant are:
- Primarily responsible for Handling tickets and application support to the endusers
- When an issue comes diagnose, analyse and solve the issue
- Responsible for any enhancements
- Writing functional specs and interacting with Abapers to develop any user exits
- Training the end users and preparing end user training material
*-Sistla
For those who wished to know the role of a functional consultant. Below is one view:

SAP TESTING

MIND-Q

TARAKESH

A functional consultant evaluates the demands in talking with the customer's

representatives, transforms the essence into an abstract and algorithmic business model.
Hence, he identifies the use cases and transforms them into logical and technical views.
Then the main task starts: customizing the respective business area and making sure the
system reacts in the manner according to the constraints of the requested use case.
The consultant documents the settings and prepares proper guidelines that allow other
consultants to do further changes or repairs with due efforts.
The consultant takes care that proper training is given to the users and that the system is
usable, performing appropriately and the business flow is complete and correct.
During go live he assists the technical staff by testing the behaviour of the system.
After go live he guarantees that the procedures remain usable and consistent in real live
situation and proposes enhancements.
The main duty of a consultant is to transfer external know-how to the client. It is not
manpower that counts but intelligence, understanding of processes, a feeling for defects
and general a common sense.
Role of a Functional Consultant in an End To End Implementation
When you talk about the role of a Functional consultant in an end to end implementation,
I think it won't be possible for me or anybody to define everything but I will try to
summarize it:
1. Functional consultant is expected to generate knowledge about the current business
process, design current business flows, study current business processes and its
complication, in all we can say getting through with current business setup. Flow
diagrams and DFD are prepared, most of the time in Vision format, all this forms the part
of AS IS document.
2. Everything configured has to be documented as per their categories in the form of
predefined templates, these have to be then approved by the team leads or who ever the
consultant is reporting to.
3. Mapping and GAP analysis is done for each module, I have seen people defining
integration after mapping, gap analysis and configuration is done, but as per my
experience in implementation, it is a simultaneous process.
4. Before starting configuring future business processes in SAP, the DFD/ERD are
prepared, this documentation is called TO BE, which can be also siad as the result of
mapping and gap analysis.

SAP TESTING

MIND-Q

TARAKESH

5. Sometimes Functional consultants are also expected to prepare test scripts for testing
the configured scenarios.
6. End user manual and user training is also expected from F.Consultants.
The project normally starts off with a Kick off meeting in which the team size, team
members, reporting system, responsibilities, duties, methodlogy, dates and schedules,
working hours which have been predicided are formally defined.
ASAP, it won't be possible for me to explain it here, but all I can tell you about it is that it
is SAP standard implementation methodology, which SAP prescribes but is not
mandatory for any company to follow, such as IBM follow some blue Methodlogy, some
companies follow typical SDLC steps, ASAP stands for Accerlated SAP, you can find all
the steps on SAP site, through google, reading it from there won't give you a great
knowledge about ASAP but will obviously get you to know the definitions of various
term.