Posted by echtscorp on October 20, 2011
STMS transaction is executed initially in client 000 with ddic authorization in order to configure TMS. The following changes occur in the system when you execute STMS for TMS configuration:
- Reassign SAP system as transport domain controller
- Create transport domain name (domain_SID)
- Create transport group (group_SID)
- Create system user TMSADM in 000.
- Create TMS RFC destinations
- Setup file domain.cfg in directory bin
- Transport profile for tp is generated TP_<domain>.pfl stored in bin.
Posted in Transport Management | Leave a Comment »
Posted by echtscorp on October 20, 2011
All repository objects are grouped into logical unts called packeges(formerly known as “Dev Classes”).
The definition of each package contains an assignment to a transport layer.
Posted in Transport Management | Leave a Comment »
Posted by echtscorp on October 12, 2011
Transport routes are used to define in which target system you want to consolidate change requests and which SAP systems are forwarded this information automatically.
All the development projects developed in a same SAP system and transported using the same transport route are grouped together to form transport layer.
There are two types of transport routes:
-Consolidation route (usually defined between Dev and QA systems)
-Delivery route (usually defined between QA/Test and Production systems)
Posted in Transport Management | Tagged: consolidation, delivery, layer, route, transport | 1 Comment »
Posted by echtscorp on October 12, 2011
STMS is a transaction used for transport management functionality in SAP landscape.
There are few steps involved to configure TMS before you can use it after system setup:
-Configure transport domain
-Configure transport route
-Choose transport strategy
-Configure QA approval procedure
-Configure transport workflow
Posted in Transport Management | Leave a Comment »
Posted by echtscorp on October 12, 2011
There are four types of transport requests:
1. customizing request (Contains client specific changes recorded in a single client)
2. Workbench request (Contains changes made to the repository objects of ABAP work bench)
3. transport of copies (Allows to transport any sub objects into object list to any other SAP system)
4. relocation (Use this when development system of a complete package is to be changed on permanent basis)
Posted in Transport Management | Tagged: customizing, tranport | Leave a Comment »
Posted by echtscorp on October 12, 2011
There’s nothing like “priority” settings for spool processes. Just define more (profile parameter rdisp/wp_no_spool) processes so people don’t need to wait.
Posted in Daily Administration, Performance Tuning, Printer Administration | Leave a Comment »
Posted by echtscorp on October 12, 2011
The roll area is one of several memory areas, which satisfies the user requests of user programs. For technical reasons, however, the first 250 KB or so of a user context are always stored in the roll area, further data
- up to the roll area limit ztta/roll_first,
- in the extended memory, up to the limit ztta/roll_extension or if extended memory is exhausted, then
- again in the roll area, until the roll area is full, then
- in the local process area, up to the limit abap/heap_area_dia or abap/heap_area_total or until the address space or the
swap space is exhausted.
Posted in Memory Management, Performance Tuning | Leave a Comment »
Posted by echtscorp on October 12, 2011
ST02 is used only to monitor the memory related parameters like (buffer hit ratio, roll area, page area ) which in case on fulfilment will effect the performance of SAP.
ST04 we can completely do the database related monitoring like backup schedules, locks etc.
Posted in Daily Administration, Memory Management, Performance Tuning | Leave a Comment »
Posted by echtscorp on January 5, 2010
If only all Dialog work processes are running,
- Check if there’s a number in the Semaphore column in SM50 or dpmon. If there is, click once on one of the numbers in the Semaphore column to select it and then, press F1 (help) to get a list of Semaphores. Then, search OSS notes and, hopefully, you’ll find a note that will tell you how to fix the problem.
- If it’s not a semaphore (or sometimes if it is), use vmstat on UNIX or task manager on Windows to see if the operating system is running short on memory which would cause it to swap. In vmstat, the free column (which is in 4k pages on most UNIX derivatives) will be consistently 5MB or so and the pi and/or po columns will have a non- zero value. The %idle column in the cpu or processor section will be 0 or a very low single digit while the sys column will be a very high double-digit number because the operating system is having to swap programs out to disk and in from disk before it can execute them.
- In task manager, look at free memory in the physical memory section under the performance tab. If it’s 10MB or 15MB (I think), then the operating system will be swapping.
- when all the dialog work processes are running, you won’t be able to log in via SAPgui and will need to execute the dpmon utility at the commandline level. The procedure is basically the same on UNIX and Windows.
On UNIX:
telnet to server and login as sidadm user.
cd to /sapmnt/SID/profile directory
execute “dpmon pf=SID_hostname_SYSNR” (e.g. PRD_hercules_DVEGMS00) select option “m” and then, option “l”
On Windows:
Click on START, then RUN
Type “cmd” and press enter
change to drive where profile directory resides (e.g. f:)
cd to \sapmnt\SID\profile
execute “dpmon pf=SID_hostname_SYSNR” (e.g. PRD_zeus_DVEGMS00) select option “m” and then, option “l”
- Check for developer trace files in work directory at OS level.
Posted in Daily Administration, Performance Tuning | Leave a Comment »
Posted by echtscorp on January 5, 2010
Roll first -> Extended memory until quota reached -> remaining of Roll area, then Heap memory
Posted in Memory Management | Leave a Comment »
Posted by echtscorp on January 5, 2010
The spool system stores data into TemSe (Temporary Sequential) database.
Posted in Daily Administration | Leave a Comment »
Posted by echtscorp on January 5, 2010
It’s a Message Server process that connects first to the database.
Posted in Daily Administration | Leave a Comment »
Posted by echtscorp on January 5, 2010
It’s from 000 to 999. Total 1000 clients are supported per SAP System.
Posted in Client Administration, Implementations & installations | Leave a Comment »
Posted by echtscorp on January 5, 2010
Access method is the way the output device is connected to SAP system. The access method is specified during the definition of output devices in the SAP System so that the system knows how it should transfer the spool work process data for this output device to the host spool system.
Posted in Daily Administration | 2 Comments »
Posted by echtscorp on January 5, 2010
The Job will continue to run and once it finishes then the Operation Mode Switch will occur.
Posted in Daily Administration | Leave a Comment »