Role of SAP Consultant In Testing
1. What is the role of SD 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
1-create 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. 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? 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)
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
