T-Code Naming convention in SAP

The T-Code also called as Transaction Code in SAP has different meaning that depends on the functionality of application and few are customized one according to requirement. There are few standard T-Codes which remains same for most of the applications. example:

Standard T-Code:

SE16

SM37

Customizes T-Codes like:

ZR01

In the above T-Code
SE : System Engineering,
SM : System Maintenance.
The last two numbers assigned in T-Codes are assigned for editing, view, creation, display etc..

Comments

Running Vuser as a Process vs. Running Vuser as a Thread

One common dilemma for performance testers is deciding whether to run Vusers as processes or threads. To make an informed choice, it’s important to first understand the distinction between a process and a thread. 1. Process : A process is an instance of a computer program being executed, with its own dedicated virtual address space. Multiple processes can run simultaneously, but each process operates independently and does not share its memory address space with others. Example : If you open Notepad, you’ll see a process named notepad.exe in the task manager under the Processes tab. Opening another instance of Notepad will create a second notepad.exe process. Each process has its own memory space, and communication between processes happens through mechanisms like inter-process communication (IPC). 2. Thread : A thread exists within a process and shares the process’s memory address space with other threads. Multiple threads within the same process can access shared memory, and when o...

How to troubleshoot high Memory utilization during performance testing

When troubleshooting high memory utilization during performance testing, it's important to identify the underlying causes and take appropriate steps to address the issue. Here are some steps to troubleshoot high memory utilization: Monitor Memory Usage: Use performance monitoring tools to track memory usage over time. Monitor both physical and virtual memory (RAM) to identify if memory consumption is exceeding available resources. Identify Memory-Intensive Processes: Identify the specific processes or components that are consuming a significant amount of memory. Performance monitoring tools can help you identify the memory-hungry processes. Look for any particular application, service, or module that stands out in terms of memory usage. Analyze Code and Memory Allocation: Review your application's code and algorithms to identify any memory leaks, inefficient memory allocation, or excessive object creation. Look for areas where large amounts of memory are being consumed unnec...

How to write a Performance Test Plan

A test plan gives complete information on the testing scope, timeline, and strategy. Here's a step-by-step guide to help you create an effective performance test plan: 1. Define the Purpose and Scope: Start by clearly stating the objectives of your performance testing. What are you trying to achieve, and what aspects of your application will you be testing (e.g., load, stress, scalability, or endurance)? 2. Identify Stakeholders: List all the individuals and teams involved in the performance testing process, including developers, QA engineers, system administrators, and project managers. Define their roles and responsibilities. 3. Set Performance Goals: Define specific performance goals and acceptance criteria. These could include response time thresholds, throughput requirements, error rates, and resource utilization targets. Make sure these goals align with business expectations. 4. Determine Performance Metrics: Select the performance metrics and key performance indicators (KPI...

Performance Testing Tips

Search This Blog