An Introduction to SAP

SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Applications and Products in Data Processing. Over the years, it has grown and evolved to become the world premier provider of client/server business solutions for which it is so well known today. The SAP R/3 enterprise application suite for open client/server systems has established a new standards for providing business information management solutions.

SAP product are consider excellent but not perfect.  The main problems with software product is that it can never be perfect.

The main advantage of using SAP as your company ERP system is that SAP have a very high level of integration among its individual applications which guarantee consistency of data throughout the system and the company itself.

In a standard SAP project system, it is divided into three environments, Development, Quality Assurance and Production.

The development system is where most of the implementation work takes place. The quality assurance system is where all the final testing is conducted before moving the transports to the production environment.  The production system is where all the daily business activities occur.  It is also the client that all the end users use to perform their daily job functions.

To all company, the production system should only contains transport that have passed all the tests.

SAP is a table drive customization software.  It allows businesses to make rapid changes in their business requirements with a common set of programs.  User-exits are provided for business to add in additional source code.  Tools such as screen variants are provided to let you set fields attributes whether to hide, display and make them mandatory fields.

This is what makes ERP system and SAP in particular so flexible.  The table driven customization are driving the program functionality instead of those old fashioned hard-coded programs.  Therefore, new and changed business requirements can be quickly implemented and tested in the system.

Many other business application software have seen this table driven customization advantage and are now changing their application software based on this table customizing concept.

In order to minimized your upgrading costs, the standard programs and tables should not be changed as far as possible.  The main purpose of using a standard business application software like SAP is to reduced the amount of time and money spend on developing and testing all the programs.  Therefore, most companies will try to utilized the available tools provided by SAP.

What is Client? What is the difference between Customization and Configuration?

The difference between cutomizing and configuration is: 
- CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data. 
- CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process. 
- CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance.

Configuration  vs. Customization 
When considering enterprise software of any type, it is important to understand the difference between configuration and customization.The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.        *-

What is SAP R3? 
We know that SAP R/3 is software, it particular it is client-server software. This means that the groups/layers  
that make up a R/3 System are designed to run simultaneously across several separate computer systems. 

When you install Microsoft Excel on your PC, each component of Excel (printing components, graphing components, word processing components, and etc.) is stored, managed, and processed via the hardware of your PC.   When a company installs SAP's software each component (or "layer" in R/3's case) is stored, managed, and processed via the hardware of separate and specialized computer systems. Each of the various layers is capable of calling upon the specialty of any of the other installed layers in order to complete a given task. 

Those components/layers that are requesting services are called "clients", those components/layers that are providing services are called "servers".  Thus the term - "client/server".       

What is meant by SAP ECC?

SAP is an ERP (Enterprise Resource Planning) module, ECC is the version of SAP, like 4.6, 4.6c and 4.7 in that series new version is ECC-6. Its known as Enterprise core component.

Role of a SAP Functional Consultant

Role of a SAP 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 functional 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 knowledge then Business consultant. 

The responsibilities of a support consultant are:

- Primarily responsible for Handling tickets and application support to the end users 
- 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  

For those who wished to know the role of a functional consultant.  Below is one view:

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 said as the result of mapping and gap analysis.

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, methodology, dates and schedules, working hours which have been predicted 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 Methodology, some companies follow typical SDLC steps, ASAP stands for Accelerated 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. 

Tags:

SAP functional consultant roles and responsibilities

SAP business consultant roles and responsibilities

become sap functional consultant

role sap functional consultant

sap functional consultant certification

sap functional consultant resume

sap functional consultant job description

sap functional consultant jobs

sap functional consultant salary

sap functional consultant rates

Roles & Responsibilities of Testing Manager

Roles & Responsibilities of Testing Manager

What are the Roles & Responsibilities description of Tester & Testing Manager in SAP Environment.

Responsibility details- 

Manager's Responsibilities-

• Manage Project Initiation through Closure.
• Resource Mobilization for Projects.
• Implement and monitor processes for Offshore Testing.
• Manage Delivery by Metrics.
• Publish KPIs for all Offshore Testing Projects on weekly, or milestone, basis.
• Submit inputs for Weekly Status Reports to the Onsite Test Coordinator.
• Participate in Weekly Review Meetings.
• Submit inputs for billing of effort.
• Offshore Team Management, Mentoring and Coaching.
• Issue Management.

Offshore Testers-

• Test Requirements Analysis.
• Test Case Development / Updating.
• Test Data preparation.
• Test Execution and Results logging.
• Defect Analysis & Reporting.
• Re-tests for Fixes.
• Submit daily status updates and Metrics to Offshore Leads.
• Peer Reviews.

Example: What are the responsibilities or expections as an SAP-HR tester.

Sap HR tester is good role for sometime.

• Expectation will you need to assist the testers (testing background people).
• People from the sap hr background in the testing projects usually preparing scenarios.
• Helping them to create the test data.
• Analysing the defects.
• Preparing the test cases and scripts (testing tool can be manual or automated).
• Validating the test results against the documents such as BPPs, Blue Prints, Configs etc.
• Execution of test cases preparing the TIRs (test incident reports) and logging them into the tool if it is in place.
• Some cases they will fix the defect also.
• Testing the interfaces, reports (custom and standard) authorisations (positive and negative).
• Integration also tested it depends on the scope of testing.
• Testings can be (system intergration testing, User acceptance testing or User confirmation testings or any other different terminology).

It is good to work as a tester for some time but it can be boring over the long term.

Tags: 

sap tester responsibilities

sap tester job description

sap tester tasks

sap tester work

sap tester job in sap testing

sap test manager responsibilities

sap test manager job description

sap test manager tasks

sap test manager work

sap test manager job in sap testin

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) Tags: sap testing tutorial sap testing methodology sap testing material sap testing interview questions and answers faqs sap testing sap testing tools sap testing process sap testing methodology sap modules sap testing tutorial manual sap testing tutorial pdf performance testing tutorial sap tutorial book sap ecatt tutorials sap testing ebook test cases tab sap library test cases solution manager test cases tab url saving test cases sap test workbench create test package sap sap testing documents sap test case template sap test plan sap test plan template sap test workbench create test package sap test scripts

Re: Introduction and Testing Process of SAP TAO

Introduction and Testing Process of SAP TAO

Introduction of 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/ALM, 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. 

~Venu

Browse for Manual Testing & QC: www.swaretesting.blogspot.com

Browse for QTP: www.qtestpro.blogspot.com

Download Material: www.nuve.info