Skip to main content

Unraveling the Secrets of SAP Directories and Parameters in Default.PFL

This list will be updated on demand and need basis , Drop a comment and it will be added.


  1. DIR_HOME: Directory for the home folder of the SAP system.
  2. DIR_EXECUTABLE: Directory for SAP executable programs.
  3. DIR_TRANS: Directory for the transport files.
  4. DIR_GLOBAL: Directory for global data files.
  5. DIR_PROFILE: Directory for the SAP profiles.
  6. DIR_INSTANCE: Directory for instance-specific files.
  7. DIR_PAG: Directory for page files.
  8. DIR_GTP: Directory for global temporary page files.
  9. DIR_REORG: Directory for reorganization files.
  10. DIR_DUMP: Directory for system dump files.
  11. DIR_WORK: Directory for work files.
  12. DIR_DATA: Directory for data files.
  13. DIR_LOG: Directory for log files.



    • Description: Name of the SAP instance.
    • Trade-off: Changing the instance name can impact system identification and require updates to related system configurations.

    • Description: Name of the SAP system.
    • Trade-off: Modifying the SAP system name can affect system identification and require adjustments to related configurations.

    • Description: Hostname of the SAP system.
    • Trade-off: Changing the SAP global host can impact system connectivity and require updates to related network and system configurations.
  4. DIR_CT_RUN:

    • Description: Directory for control and work files.
    • Trade-off: Modifying this directory affects the location of control and work files and may require updates to related system configurations.

    • Description: Directory for EPS (External Program Storage) files.
    • Trade-off: Changing this directory impacts the storage location of EPS files and may require adjustments to related system settings.

    • Description: Directory for home executables.
    • Trade-off: Modifying this directory affects the location of home executables and may require updates to related system configurations.

    • Description: Directory for home log files.
    • Trade-off: Changing this directory impacts the storage location of home log files and may require adjustments to related system settings.
  8. rdisp/mshost:

    • Description: Message server host.
    • Trade-off: Modifying the message server host affects the communication between application servers and clients, and requires updates to related network and system configurations.
  9. rdisp/msserv:

    • Description: Message server service.
    • Trade-off: Changing the message server service can impact the communication between application servers and clients and requires updates to related configurations.
  10. rdisp/wp_no_dia:

    • Description: Number of dialog work processes.
    • Trade-off: Increasing this parameter allows for more simultaneous dialog processes, improving system responsiveness. However, it consumes more system resources, so careful monitoring is necessary to ensure optimal performance.
  11. rdisp/wp_no_btc:

    • Description: Number of background work processes.
    • Trade-off: Increasing this parameter enables more simultaneous background processes, facilitating efficient execution of background jobs. However, excessive background processes can result in resource contention and affect system performance.
  12. rdisp/wp_no_enq:

    • Description: Number of enqueue work processes.
    • Trade-off: Increasing this parameter enhances lock management and improves system concurrency. However, it consumes additional resources, so it should be adjusted based on system requirements and workload.
  13. abap/heap_area_total:

    • Description: Total heap memory available for ABAP.
    • Trade-off: Increasing this parameter expands the overall heap memory available for ABAP programs, allowing for larger memory allocations. This can benefit memory-intensive processes but may require additional system resources.
  14. abap/heap_area_dia:

    • Description: Heap memory available for ABAP dialog processes.
    • Trade-off: Increasing this parameter allocates more heap memory specifically for dialog processes, facilitating better performance for interactive tasks. However, excessive allocation can lead to higher memory consumption.
  15. abap/heap_area_nondia:

    • Description: Heap memory available for ABAP non-dialog processes.
    • Trade-off: Increasing this parameter reserves more heap memory for non-dialog processes, such as background jobs, optimizing performance for non-interactive tasks. However, it may impact memory utilization.
  16. icm/host_name_full:

    • Description: Full hostname of the SAP system for ICM (Internet Communication Manager).
    • Trade-off: Modifying this parameter affects the hostname used by the ICM for communication. It is essential to ensure the correct hostname is specified to establish proper connectivity with external systems.
  17. icm/server_port_<n>: Description: Specifies the port number for a particular ICM server. The parameter <n> represents the server instance number. Each ICM server instance requires a unique port number for communication. Trade-off: Choosing the appropriate port number for the ICM server involves balancing security and accessibility. Lower port numbers (e.g., well-known ports) may be more susceptible to unauthorized access or attacks. Higher port numbers provide more security but can be challenging to manage in complex network configurations.
  18. rdisp/max_alt_modes: Description: Defines the maximum number of alternative modes for a work process. Alternative modes are used to execute non-dialog tasks during peak load times. Each alternative mode represents an additional processing mode for the work process. Trade-off: Increasing the maximum number of alternative modes allows for better load distribution and can help handle higher workloads during peak periods. However, it also consumes additional system resources, such as memory and CPU, which may impact overall system performance.
  19. abap/buffersize: Description: Specifies the buffer size for ABAP programs. A larger buffer size can improve performance by reducing disk I/O operations. It determines the amount of data read from or written to disk in a single operation. Trade-off: Increasing the buffer size can enhance performance by reducing the frequency of disk I/O, which can be a significant bottleneck. However, it also increases the memory consumption of the SAP system, potentially affecting other processes and resource utilization.
  20. icm/keep_alive_timeout: Description: Determines the duration of an idle connection before it is closed by the ICM. This parameter helps manage resource utilization and connection availability. Idle connections consume system resources and can limit the availability of resources for other connections. Trade-off: Setting a shorter keep-alive timeout reduces the duration of idle connections, freeing up resources more quickly. However, it may also lead to more frequent connection establishment and teardown, which can increase overhead.
  21. rdisp/wp_ca_blk_no: Description: Sets the number of dialog work processes used as collision avoidance blocks. These work processes handle specific tasks related to lock management and concurrency control. They prevent multiple work processes from accessing the same data simultaneously, improving system stability and consistency. Trade-off: Allocating more work processes as collision avoidance blocks enhances system concurrency and reduces the likelihood of data conflicts. However, it also reduces the number of available work processes for executing user transactions, potentially impacting system responsiveness during peak load periods.
  22. ztta/roll_area: Description: Specifies the maximum size of the roll area, which is used for storing ABAP program data during execution. The roll area holds the data that exceeds the available memory space and is temporarily stored on disk. Trade-off: Increasing the size of the roll area allows for larger data storage during program execution, reducing the frequency of disk I/O operations. However, it also consumes more memory resources, potentially impacting the overall system performance and available memory for other processes.
  23. rdisp/plugin_auto_logout: Description: Controls the automatic logout behavior for SAP GUI users who are inactive for a specified period of time. When enabled, users who remain inactive for the defined duration are automatically logged out of the SAP system. Trade-off: Enabling the automatic logout feature enhances system security by reducing the risk of unauthorized access to an active user session. However, it may inconvenience users who may need to frequently re-login if they have prolonged periods of inactivity.
  24. gw/acl_mode: Description: Determines the access control mode for the SAP Gateway. It defines how clients are authenticated and authorized to access SAP system resources. Different ACL (Access Control List) modes provide varying levels of security and control. Trade-off: Selecting the appropriate ACL mode depends on the specific security requirements of the SAP system. More restrictive ACL modes provide stronger access control but may also require more administrative effort to manage and maintain authorized client access.
  25. abap/heap_area_nolimit: Description: When set to TRUE, removes the limit on the heap memory available for ABAP programs. This allows ABAP programs to use memory without restrictions. Trade-off: Removing the heap memory limit can provide flexibility for memory-intensive processes and prevent memory-related errors. However, it also increases the risk of memory exhaustion and potential performance degradation if programs utilize excessive memory.
  26. icm/HTTP/logging_0: Description: Configures the HTTP logging level for the ICM. It determines the level of detail captured in the log files, helping with troubleshooting and monitoring. Trade-off: Increasing the logging level provides more detailed information in the log files, facilitating thorough analysis and troubleshooting. However, it also increases the volume of log data, potentially impacting disk space usage and log file management.


You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c