Wednesday, 11 July 2012

Tips for SAP testers to find the list of SAP Transaction codes

Tips for SAP testers to find the list of SAP Transaction codes

Where I can find the list of transaction codes and their usage, I heard that there is some table which contains all the transaction codes with their descriptions.

Does anyone know about the Table that consist all the T-Code?

Listed here are the various ways you can find the list of transaction codes and their usage:

Use transaction SE11 - ABAP Dictionary:

Fill in the Database table name and click the Display button. 
- TSTC   table will contain all the Tcodes and 
- TSTCT table will contain all the Tcodes with Texts.

Once you entered the screen, click in Top Menu - Utilities - Table contents - Display

If you want to display all the transaction code (total - 57,048) you have to change the Fields: Maximum number of hits to 99999 (default 500).

or

Simply goto transaction SM01, although this tcode is to Lock/Unlock any transaction code, you can also view all the tcode available in the R/3 system from here.

or

Goto transaction SE93

There are two ways where you can find the list of transaction codes in SE93.

Method 1: 
You must be familiar with the starting characters strings for each of the R/3 application modules.

Assuming you know that most Materials Management transaction codes start with MM.

In the Fields: Transaction code, type in MM* and press the function key F4

The list of transaction code starting with MM will be displayed.

Method 2: 
On the Top Menu, click Utilities - Find - Execute and the first 500 transaction will be display.

If want to display all the tcodes, make sure you remembered to change the Fields: Maximum no. of hits right at the bottom of the screen.

I know a particular T Code and can enter and work on it.  How do I know what is the menu path for that T Code?

Enter Search_SAP_Menu in the command box and when the pop box appears enter, the Tcode and it will give the nodes and menu path. 

This is helpful only in case of SAP Menu not in case of SPRO - ie IMG.....

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.

SAP Testing in a high level terms


SAP Testing in a high level terms


SAP Testing is same as manual testing but here the applications are SAP R/3 and Enterprise portal. Whenever there is change in R/3 and Portal and You need to design test cases according the change request and test the application. 


If you have knowledge in the module (like HR, CRM, SD, SRM), which you are going to test would be helpful to you. 


UAT means USER ACCEPTING TESTING. Suppose end user raised an issues that we solved and send to end used it is working fine. then we get confirmation from him that it is fine. that is call UAT. 


UNIT TESTING - This is done by developer and anyone who did any customizing or any code to ensure what they did is working properly 

INTEGRATION testing - Done by tester by developing some scenarios which are most unlikely and get the result to ensure the integration is correct 

Apart from that, regression testing, functional testing and other cross functional testing are there done by testers 

In realization phase, unit testing are done by developers 
After unit testing, Integration testing and other testing are done by testers/functional depending upon the object to test. 

Testing usually follows two paths. Firstly, System Integration Testing (SIT) which is performed by the SAP team in the development client, and secondly User Acceptance Testing (UAT) which is performed in the QA client after transport from the development client. UAT is performed by end users or the testing team. 

Unit Tests are defined and performed by developers. A process consists usually of several functions. Each of this function usually consists of "sub-functions" corresponding to a single method or a group of methods (if you are developing OO-based). 

Unit Tests could be described as white-box tests whereas a normal tester (which should be not identical to the developer) will test entire functions (black-box tests). 

--- During the entire life cycle of a SAP solution, it is necessary to test the functions and performance of your solution. With the SAP Test Workbench, SAP provides you with an environment for all test phases, which you can use for testing in the following cases: 

• Implementation of SAP solutions 
• Integration of new components and business scenarios 
• Customer developments 
• Function tests 
• Integration tests with other components 
• Upgrades, regression tests 
• Importing support packages 

Integration 
Features 
Test Preparation 
• Creation of manual and automated test cases 
• Management of manual and automated test cases 
• Creation of test plans 
• Definition and management of test series 
Test Execution 
• Execution of mass tests using Extended Computer-Aided Test Tool and Computer Aided Test Tool 
• Integration of test cases and test scripts of non-SAP providers 
• Assignment of work lists (test packages) to individual testers 

Test Evaluation 
• Permanent overview of test progress and test results 
• Complete documentation of test processes in the test plans (test cases, test case descriptions, test results, test case notes, error messages) 
• Detailed tabular and graphical evaluation of all test plans 
• Export of test results to Office applications 
• Message processing 

Testing usually follows two paths. Firstly, System Integration Testing (SIT) which is performed by the SAP team in the development client, and secondly User Acceptance Testing (UAT) which is performed in the QA client after transport from the development client. UAT is performed by end users or the testing team.

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