SAP Testing Process:

The Phases in S/w life cycle:

Initiiantion/Idea
Study
Implemenation
Testing
Documentation
Deployment and maintenance

"standard testing such as unit testing, system testing, uat and performance
testing."
In fact, these are "Testing methodology" .

--unit testing
--system testing
--uat (what does this acronym stands for???)
--performance testing

Testing methodolgies in SAP:

The tools used in ASAP methodology:

AcceleratedSAP (ASAP) methodology, and tools available for AcceleratedSAP such as

The tools used:

--Project Estimator
--ASAP Implementation Roadmap
--Project Plan, etc
--ACAT,
--CCAT i

---------------------

ASAP Methodology

----------------------

what is meant by ASAP methodolgy,

2.Solution manager.
3.LSMW.
4. Report painter/Report wiring.
5. A brief idea about Integration FI with Other modules.

ASAP Methodlogy:

Phase 1 Project Preparation - The primary focus of Phase 1 is getting the project
started, identifying team members and developing a high-level plan.

Phase 2 Business Blueprint - The primary focus of Phase 2 is to understand the

business goals of the company and to determine the business requirements needed to
support those goals.

Phase 3 Realization - The purpose of this phase is to implement all the business
and process requirements based on the Business Blueprint. You customize the system
step by step in two work
Packages, Baseline and Final configuration
Phase 4 Final Preparation - The purpose of this phase is to complete testing, end-
user training, system management and cut over activities. Critical open issues are
resolved. Upon the successful
Completion of this phase, you will be ready to run your business in your productive
R/3 system.

Phase 5 Go Live and Support - Transition from a project oriented, pre-productive

environment to a successful and live productive operation.

LSMW: Legacy System Migration workbench is a data uploading tool used for uploading
master data for various modules.

Solution Manager:

SAP Solution Manager supports you throughout the entire life-cycle of your
solutions, from the Business Blueprint to the

configuration to production processing. It provides central access to tools,

methods and preconfigured contents which you

can use during evaluation, implementation and operational processing of your

systems.

4.Report painter is a tool for creating reports.

5.FI is integrated will alll the modules i.e SD/MM/HR.

--------------------------------------------

Unit Testing and Integration testing

------------------------------------------

What is the Test Case scenaraios? and what is the Unit testing and Integration
testing

Main what is the Difference between Unit and Integration Testing?

Unit Testing - Unit testing is testing a single functionality; it could be testing

a Z-program (say, new report/form) or could be testing a standard SAP transaction
(e.g. FB60, FB70, AS01, FB01, MIRO etc) .

Integration Testing - It is testing the desired functionality encompassing multiple

SAP modules or End-to-end processes. A typical example is P2P (Purchase to Pay) -
which starts from MM (Purchase Requisition) & ends in FI (Payment posting). Make to
Stock, Order to Cash are other scenarios commonly used in Integration Testing.

Test case scenarios are documents with depict 'what needs to be tested' & with what
data.

System testing of software or hardware is testing conducted on a complete,

integrated system to evaluate the system's compliance with its specified
requirements ...

Regression test is a test that is performed to make sure that previously working
functionality still works, after changes elsewhere in the system.

User acceptance is a type of testing performed by the Client to certify the system
with respect to the requirements that was agreed upon.

-------------------------------------------

SAP Testing is based on module. The tools used for testing process they used are
ASAP, HP QC, QTP, SAP TAO, Loadrunner tools for testing SAP. There will be
application testing and process testing.

Usually, Test scenarios are dependent on the business process of the client. Need
to understand the business and then create scenarios and prioritize them.Scenarios
could be End-to-End ,testing with external or legacy systems

Eg:
Test scripts would be based on process. For example for running payroll:
test case 1. log onto SAP
test case 2. goto SE38
test case 3. enter report name RPCALCU0
test case 4. click execute
test case 5. enter pernr
etc. This is just for example.

test scripts both manual and automation which will be maintained in Mercury Quality
Center or QTP for automation.

Once you identify your test scenarios ,scripts should be targetted at testing these
scenarios step-by-step.Like login to the system with correct role,verify
authorizations for the role,navigate to the transaction , process the transaction
and save.Then you should verify the down stream process like tables updated,correct
ammount being calculated based on pricing conditions picked up by the document.

Basically,

Test cases can be written on 2 basis; a) Your business blueprint which gives the
process flow within the module. b) on the requirement given to the Functional
Consultnat by the client.

In an ASAP menthodology of implimentation, the requirements are gathered in the

blueprinting phase and they are address as process flow in the BPP (Business
process Procedure document)

Lets take an example of a process where an employee applies for leave :-

Step 1 - Logon to SAP using the employee logon Expected : Employeee Successfully
logged on Actual: " we will have to fill then while you actually execute this step"

Step2 - Enter Transaction PA30 in the command field Expected: HR Master Data screen
is displayed Actual: " "

Step3- Enter infotype number 2001 in the infotype tab and click create Expected:
Create absences is displayed Actual :" "

Step4- Enter the start and end date of leave and leave type and click save Expected
: Employee has submitted the absence for further approval. Actual: " "

These are 4 simple steps on how we create your test case. we write test case in the
Test Plan tab - pull them accross as sequence in the test lab and execute them.

If we follow these simple steps , it will help to automate them. Defects at every
step executed can be raised at the step level itself - Defects can further be
tracked in the defects menu.

-------------------------------

SAP FI Currency Settings:

--------------------------------

we have the following currency setup in SAP FI

(SPRO > Financial Accounting > Financial Accounting Global Settings > Company Code
> Parallel Curencies > Define additional local currencies) --> TC:OB22

Example: Settings for a German company code:

1st: Currency Type 10 � Company code currency (EUR)

(To meet statutory accounting requirement for each company code, Local GAAP and tax
principles)

2nd: Currency type 30 � Group currency (USD)

(To meet functional currency requirements and group requirements, holding is US-
based)

This company code is based in Germany � currency EUR.

Now, after running our system for a few months, business recognizes that the daily
changing exchange rate leads to differences (especially for Inventories) between
USD and EUR.

The target is to minimize the effect of this posting.

Business intents/wants the following approach: Change leading currency (1 st local

currency to USD). Holding requirement to avoid currency posting differences would
be fulfilled � the statutory requirements in this case would have to be checked
concerning conversion to local currency (EUR) etc.

---------------------------

Functional Specification

-------------------------

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.
Elsewhere organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functionality..
It describes the product's features as seen by the stakeholders, and contains the
technical information and the data needed for the design and development.
The Functional Specification defines what the functionality will be of a particular
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 technical development process.
b) Clearly and unambiguously provides all the information necessary for the
technical consultants to develop the objects.
At the consultant level the functional spec are prepared by functional consultants
on any functionality for the purpose of getting the same functionality designed by
the technical people 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 Assessment
9) Functional Design (Module Wise)
10) Risk Assessment
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Functional spec is then converted into a Technical Spec and Unit Test Plan. The
test plan
becomes part of the String and/or Integration Test Plan to validate the
functions actually work.

-----------------------

Configuration Tesing

------------------------

Configuration Testing:
With the help of your SAP consulting team, you segregate your business processes
into cycles of related business flows. The cycles serve as independent units that
enable you to test specific parts of the business process. You can also work
through configuring the SAP implementation guide (IMG). A tool used to assist you
in configuring your SAP system in a step by step manner.