SAP Tester Roles and Responsibilities
SAP Tester Roles and Responsibilities
Master Data
Company Code
Currency
Only Balances in local currencies
Reconciliation Account Type
Year End Scripts
Re Grouping Receivables / Payables - (F101)
Bad Debts Provisions u2013 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
Reset Clearing
Carry forward
Regrouping
Accounts Receivables
Invoice
Parking
Reversal
Incoming Payments
Manual Clearing
Reset Clearing
Carry forward
Regrouping
Unit Testing
String Testing
One transaction full activity is called string testing . For example Vendor
invoice, goods received and vendor payment.
Integration Testing
Testing for whole database. Bring all the data into another server and do
the testing is called regression.
UAT
While doing the user acceptance testing if we get any problems then
there are some methodologies to be followed according to the company
u2019s policy and normally as a tester we always need to write on Test
Script itself.
Business Blueprint
Once a company decides to buy SAP, a consulting company is being
hired for the implementation. The consulting company analyze the
business process of the company and prepare a blueprint.
Sometimes the business process is reengineered (BPR) to
accommodate SAP's functionalities.
The second step is installation of SAP and setting up three clients
namely development client, test client and production clients.
In the development client the SAP functional and development group
start configuring the SAP based on the blueprint. Once it is completely
configured, it is being transported to test client for testing using real time
data. Once testing is successful, the configuration is being transported to
production client to be used by real-time users.
So this process makes SAP more reliable and robust in production.
Preparation Before Implementing SAP
SAP R/3 implementation is generally a key project for any organization.
It is necessary to do preparation before implementation.
Many organizations speak of "transferring technology." But what does
that mean? Transfer technology involves transfer of the system which
includes the
hardware
software
people
processes
information
organization
structure
synchronization
function and
behavior.
It becomes obvious that the transfer of any part of the system, without
the rest of it, does not transfer technology. In our context, the software
SAP/3 is being changed. In most of the cases the hardware needs to be
changed. The people need training to operate SAP system. But
unfortunately, many organizations fail to understand that they need to
change their processes. SAP is a package & it contains many best
practices suitable to almost each industry. The designer (configuring the
system) must design the system keeping the objective of the business
objective in mind. The user should be prepared to change it’s processes
and ensure that the objective of the processes is met. This should be
done without or minimum distortion of the processes designed by SAP.
This is a big challenge to the designer as well as user. It should noted
that the user representative involved in the system design should be
empowered for low level BPR decisions.
Also the information stored in the system will be in different form than the
legacy system. The user must be prepared & trained for the changed.
The major challenge is behavioral change. Implementation of SAP R/3
system changes relationship of different persons, it gives/denies access
to information which was not available/available to the person, it
changes processes and control functions. This all gives behavioral
issues. To get best out of SAP, these issues must be addressed before
implementation.
SAP R/3 re-engineers many processes and the fear of downsizing and
loosing job hinders free acceptance of SAP in many organizations. This
fear hinders free communication between the end-users and SAP
system designer. The communication is a vital element in successful
implementation of SAP R/3. This issue of 'Fear Of Downsizing' must be
addressed before starting implementation project.
ASAP Implementation Methodology
Any enterprise application software has to cover a broad spectrum of
functionality, yet to be configured enough to meet specific requirements.
SAP achieves this by ASAP methodology & R/3 Business Engineer.
AcceleratedSAP (ASAP) is SAP’s standard implementation
methodology. It contains the Roadmap, a step-by step guide that
incorporates experience from many years of implementing SAP. Quality
checks are incorporated at end of each phase to ensure quality of
deliverables and monitor critical success factors.
ASAP is delivered as a PC based package, so that an implementation
project can begin prior to having an SAP R/3 system installed
ASAP Tools
ASAP Roadmap
ASAP and Business Engineer have compatibility with many third party
modeling tools and packages like MS Excel etc
Creating the Business Blueprint for Implementation Projects
Purpose
To create a Business Blueprint during the implementation of mySAP.com
solution to document the business processes in an enterprise, and to
decide which processes should realize in SAP system.
The use of Business Blueprint in the Solution Manager during the
realization phase (configuration and testing) should continue. It needs to
reuse the project structure created in the Business Blueprint phase, to
configure and generate test plans. One can also display, change and
enhance project documentation created during the Business Blueprint
phase, during configuration.
Prerequisites
You want to implement a mySAP.com solution. You have completed the
Project Preparation: you have defined an implementation project and a
system landscape in the project administration of the SAP Solution
Manager.
Process Flow
...Create a Blueprint structure, using predefined substructures.
Check the Business Blueprint structure, and the business scenarios,
business processes and process steps it contains.
Decide which business scenarios, business processes and process
steps you want to include in the Business Blueprint. You can enhance
the processes and process steps, or adjust the names of individual
processes to suit your company requirements.
Create the project documentation and save it in the Business Blueprint.
Assign transactions to process steps. This specifies which transactions
in the system correspond to the process steps in your enterprise.
Print the Business Blueprint document.
When the Business Blueprint is complete, you can start to set up the
development system landscape.
Result
You have created your Business Blueprint and set up your development
system landscape. You can reuse the Business Blueprint and the project
structure to configure and test your business processes
Business Blueprint
Use
This function documents the business processes in your company that
you want to implement in the system. In a Business Blueprint for
Projects, you create a project structure in which relevant business
scenarios, business processes and process steps are organized in a
hierarchical structure. You can also create project documentation and
assign it to individual scenarios, processes or process steps. You then
assign transactions to each process step, to specify how your business
processes should run in your SAP Systems.
The Business Blueprint is a detailed description of your business
processes and system requirements. You can print it out.
Integration
You can continue to use the project documentation and the project
structure that you create during the Business Blueprint, in the
configuration and test organization phases.
• When you configure your business processes, the system displays the
Business Blueprint project structure. You can use the Business Blueprint
project structure as a point of reference during configuration.
• You can also display and edit the project documentation from the
Business Blueprint phase, during configuration.
• You base all test plans that you create during test organization, on the
Business Blueprint project structure. The transactions that you assign to
process steps in the Business Blueprint are put in test plans during test
plan generation, and run as function tests to test the transactions.
Prerequisites
You have created a project of type implementation, template, or
upgrade, in the project administration.
Features
Scope of the transaction Business Bueprint
Function Tab
Create a project structure Structure
Display the following documentation:
• Documentation delivered by SAP, e.g. scenario descriptions
• Documentats from templates, e.g. from template projects
To be able to edit general documentation, copy it to the Project
Documentation tab. General Documentation
Assign documents to structure elements
Create, Change, Upload user documents Project Documentation
Input administration data, e.g. project status, team members assigned,
planned and actual resources Administration
Assign transactions and programs to structure elements Transactions
Create, Display and Edit messages Messages
Display and Create a process graphic
Create a process graphic Graphic
Where-used list:
• Use in user project
• Use in other projects
• Go to use by double-click • General Documentation
• Project Documentation
• Transactions
General Functions
Function Navigation
Change the sequence, hide or show tabs Settings ® User-Specific
Translate project structure
For further information about translating document names for URLs, in
your project, see Translating a Template
Goto  Translation
Create/print a Business Blueprint document Business Blueprint
 Create Blueprint Document
Assign Document Authorizations
Assign authorizations in the Role (PFCG) and User Maintenance.
Activities
...
1. Create a Blueprint structure in the Structure tab, using predefined
substructures.
2. Check the Business Blueprint structure, and the business scenarios,
business processes and process steps it contains.
3. Decide which business scenarios, business processes and process
steps you want to include in the Business Blueprint. You can enhance
the processes and process steps, or adjust the names of individual
processes to suit your company requirements.
4. Create project documentation to save in the Business Blueprint, in the
Project Documentation tab.
5. Assign transactions to process steps in the Transactions tab. This
specifies which transactions in the system correspond to the process
steps in your enterprise.
6. Print the Business Blueprint document.
7. When the Business Blueprint is complete, you can start to set up the
development system landscape.
Result
You have specified a Business Blueprint. You can reuse the Business
Blueprint and the project structure to configure and test your business
processes.
-
-
Business Blueprint
Definition
A Business Blueprint documents the business process requirements of a
company. In collaborative business processes, several companies are
involved.
Use
The Business Blueprint gives you a general idea of how your business
processes could be mapped in one or more SAP Systems. The Business
Blueprint documents in detail the scope of business scenarios, business
processes, process steps, and the requirements of a mySAP.com
solution implementation.
Structure
A Business Blueprint compises the following structure elements in a
hierarchy:
• Organizational units
• Master data
• Business scenarios
• Business processes
• Process steps
You assign content, for example, project documentation, Business
Configuration Sets, or transactions to individual structure elements, in
the SAP Solution Manager.
You can also create structure elements for organizational units and
master data, below a business scenario. You only use these structure
elements if the organizational units and master data are only relevant to
the business process above them in the structure.
Job Description
Define test cases, perform testing and record results and working
with users to obtain sign off for successful testing.
Carry out fault diagnosis relating to moderately complex problems,
reporting the results of such diagnosis in a clear and concise
manner.
Produce system integration reports as required by the project
integration plan.
Interpret and execute sets of moderately complex test scripts using
agreed methods and standards.
Check test results, and documents test failures and successes
compared with predetermined criteria, in accordance with agreed
standards.
Report test results to supervisor and/or other colleagues in a clear
and concise manner.
Analyze test requirements, designs and builds simple test case
suites, test scripts, and test procedures (with expected results) to
be executed by less experienced colleagues.
Use normal operating facilities, test scripts, diagnostic tools,
technical manuals and systems documentation to identify,
diagnose and report on basic system errors.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
SAP Tester Duties & Responsibilities
To write an effective SAP tester job description, begin by listing detailed
duties, responsibilities and expectations. We have included SAP tester
job description templates that you can modify and use.
Sample responsibilities for this position include:
Integrate SAP and Non-SAP processes using SOLMAN, QTP and
Selenium
Experience in preparation, execution, validation, documentation of Test
Scripts using SAP Solution Manager, QTP, HPQC
Create test automation framework
Review test script developed by test engineers , assessing test quality
Planning Automation test script execution, filing defects, verifying defect
fixes
Leading a team in offshore to generate a vision, establish direction and
motivate team members
Working with testing lead Ensures payroll tests are conducted and
accepted by internal stakeholders and impacted vendors Facilitates
testing execution and develops test evidence Manages daily test status
reporting with testing lead Work with and support the Functional and
Analyst groups in gaining the details to development test scenarios
Manages test exit/entry criteria with testing lead Client is upgrading from
SAP HRP 4.7 to 6.0
Communicating and working with people at all levels in a team
environment
Review Business, Functional, Technical Requirements and Process
Design documents
Gather the requirements in Quality Center Requirements Excel Template
and upload requirements to Quality Center
Our company is looking to fill the role of SAP tester. If you are looking for
an exciting place to work, please take a look at the list of qualifications
below.
Our growing company is hiring for a SAP tester. Please review the list of
responsibilities and qualifications. While this is our ideal list, we will
consider candidates that do not necessarily have all of the qualifications,
but have sufficient experience and talent.
Our innovative and growing company is looking for a SAP tester. If you
are looking for an exciting place to work, please take a look at the list of
qualifications below.
Our company is hiring for a SAP tester. If you are looking for an exciting
place to work, please take a look at the list of qualifications below.