• 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.

The definition of each package contains an assignment to a transport layer.

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)

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

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)

- 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.

ST04 we can completely do the database related monitoring like backup schedules, locks etc.

• 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.

1. Enter the transaction SMLT.

select from menu LANGUAGE -> CLASSIFY.

Enter Language = Thai and supplementation Language = English (please note this only allow to set ONCE ONLY!!).

Click SAVE disk icon. Highlight THAI then select LANGUAGE -> IMPORT PACKAGE.

Language = Thai

Path = (the CD , must be UNIX path if backend is UNIX server!)

2. Enter the transaction RZ10.
   Set install/codepage/appl_server = 8600 (note: 86=Thai, 00=English)
3. Enter the transaction SE38.

Execute ProgramRSCPINST and click execute icon
Enter Languages -> remove German(DE) & add Thai (TH) {please note ONLY allow TWO languages max)
Click SIMULATE button at top bar (this will tell you if any errors, example Code Page not match)
If simulate OK then click ACTIVATE button on top bar.

FINISH – your language is installed & activated!!!!!!!

]]> http://sappond.wordpress.com/2010/01/05/how-to-install-a-language-into-sap/feed/ 0 echtscorp http://sappond.wordpress.com/2010/01/05/is-it-possible-to-update-support-release-packages-from-os-level/ http://sappond.wordpress.com/2010/01/05/is-it-possible-to-update-support-release-packages-from-os-level/#comments Wed, 06 Jan 2010 03:39:27 +0000 echtscorp http://sappond.wordpress.com/?p=132 ]]> No – you can import them but the full process will require additional steps the tools “tp” and “R3trans” are not aware of. The way is to use SPAM – but SPAM has the possibility to schedule those imports in the background.

SAINT is used to install new addons.

SPAD is for creating printers.

SPDD is for adjusting modification to dictionary objects.

Transport domain controller is a system which has trans directory, and in which the total landscape is designed and  maintained

Next logon to the system where you want that particular role. Go to PFCG-> Role -> upload.
Give the path where the role is saved. it accepts and generates successfully

A part of this area (in the graphic, roll area 1) is allocated a user context at the beginning. Its size is defined in ztta/roll_first. The partial area is for the data that must be contained in the roll area. When a user context is changed, this data is “rolled” (copied) into and out of a work process. If ztta/roll_area is larger than ztta/roll_first, the additional space makes a second part available (roll area 2).

If the user context cannot be allocated more extended memory, this second part of the roll area is available for the dialog processes

There is a “delete” button when you define the queue. If you already started the import it’s no more possible since the system will become inconsistent.

$ for i in *.SAR;

do SAPCAR -xvf $i;

done;

For Windows:

SAPCAR -xvf *.SAR

This happens when your extended memory is exhausted

1. Find out the source client space size.
2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV
   client based on space requirements also.
3. You can do the client copy by remote or export/import client. Remote method is not preferred if you are doing a large client copy. Do a client export/import.
4. To speed up the export/import, use R3trans export/import for the clustered tables.
5. Do import and post processing.

If it is a fresh installation, do this:

1. With transaction SCC4, Create client no. and fill other details.
2. Logon to the newly created client with SAP* and PASS as password.
3. With transaction SCCL, choose any profile (preferably SAP_ALL), source client 000 and target client.
4. Make a test run.
5. Check table space in database and keep checking logs from SCC3.

1. Take offline backup of both the server (source and target servers) and verify if its done successfully.
2. Take backup of control file. Run the following command on the source system SQL prompt:

• Alter database backup controlfile to trace  (This command generates trace file at /oracle/P01/saptrance/usertrace.)
• exit
• Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file
• Copy the controlfile.sql to target system.
• Edit the file and replace the entire source SID to target SID.
• Edit the reuse database command with the set database command.

3. Copy the aft generated during the backup file from the source system to target system. (/oracle//sapbackup)

• Alter database backup controlfile to trace  (This command generates trace file at /oracle/P01/saptrance/usertrace.)
• exit
• Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file
• Copy the controlfile.sql to target system.
• Edit the file and replace the entire source SID to target SID.
• Edit the reuse database command with the set database command.

4. Shutdown the target server instance. (from this onwards all steps to be followed on target system only)
5. Restore database of target system from the database backup you have taken in step 1.
6. Once database is restored, execute the following commands.

• startup nomount (if the database is already mounted shutdown it using the shutdown command)
• @controlfile.sql (file name of the control file contains the CREATE CONTROLFILE statement)
• The above command it should give the “Statement Processed)
• alter database open resetlogs
• Start the database and SAP services using startup.

7. Now reconfigure STMS of target system.
8. All the jobs also you have to reconfigure and reschedule.
9. Reconfigure all the printers
10. If you want to change the Client number then use the local copy tool and remove the original client after successfully import to new client.

1. Log into the client you want to delete.
2. Enter transaction SCC5 and delete the client.
3. Log on to the another client of the same system and delete the entry of the deleted client from SCC4 tcode. (only if you haven’t checked the entry “delete client from T000″.)
4. Reorganize the database to recover database space.

Another way of deleting a client is using R3trans at OS level. This way gives more performance.

1. Make file “abc.bat” at path usr/sap/trans/bin with following commands in it.

Clientremove
Client = 200
Select *

1. Run the following command at command prompt:

R3trans -w abc.log -u 1 abc

To check the progress:

tail -f abc

• Monitoring system availability with NWA.
• Java Application Response Time Management.  (start Visual administrator-> cluster -> server ->services ->performance tracing ->JARM tab ->Component overview)
• Java Management Extensions. (start Visual administrator-> cluster -> server ->services ->Monitoring)
• Generic Request and Monitoring Generator. (GRMG)

]]> http://sappond.wordpress.com/2009/12/03/how-do-you-monitor-nwdi/feed/ 0 echtscorp http://sappond.wordpress.com/2009/12/03/what-is-sap-nwdi/ http://sappond.wordpress.com/2009/12/03/what-is-sap-nwdi/#comments Thu, 03 Dec 2009 20:56:18 +0000 echtscorp http://sappond.wordpress.com/?p=61 ]]> SAP NetWeaver Development Infrastructure (NWDI). NWDI provides an infrastructure for developing Java-based applications on SAP NetWeaver and is responsible for versioning, build and the life cycle management of the applications.

Change Management Service (CMS): You use the CMS to configure the development environment in the JDI and to administer the software logistics. The CMS is responsible for transporting and setting up the logical development landscapes and then for transporting the software changes centrally to various systems or tracks within the development landscape

Design Time Repository (DTR): You use the DTR to administer the source files. The DTR overcomes many of the limitations of file-based versioning systems for all kinds of development objects required in the Java development process.

Component Build Service (CBS): You use the CBS as the central build environment. The CBS is responsible for building the sources that are stored in the DTR and is the central build environment.

System Landscape Directory (SLD) and Name Service: In the SLD, you find the Software Catalog and the landscape description; a Name Service, which guarantees the uniqueness of object names, is also located there.

All NWDI services use a database for data storage. The SLD integrates them into the entire SAP system.

• DI is prerequisite for: SLM, developing web dynpro java application, creating composite application.
• To display the start page of the SAP NetWeaver Development Infrastructure, use the following URL:

http://<host name>:<port number>/devinf

2. Prerequisites for Installation
First, bring SAP Solution Manager up-to-date (as of July 2009, SAP Solution Manager 7.0 SP Stack 20 was recommended). In order to use Maintenance Optimizer application (note 1122966), it is necessary SAP Solution Manager 7.0 with the latest Support Package level in the system landscape.
Note 1165437 describes in detail which Support Packages are required for installing the selected SAP enhancement packages.

3. Select the Software Components
The starting point for the installation is the decision about which new business functions will be used in the system. Therefore, initially make a list of the business functions needed. To help ensure consistency, SAP bundled ABAP components, Java components, portal content, and XI content as “technical usages”.
Note 1165438 describes information about the mapping of business functions to technical usages.

4. Identify and Download SAP Enhancement Packages Using SAP Solution Manager Maintenance Optimizer
Similar to the installation of Support Packages use Maintenance Optimizer to install all needed software components. It is only needed to select the required technical usages.

• * SAP Enhancement Package Installer installs SAP enchancement package 4 for SAP ERP using a system cloning and switch procedure (note that operating two instances in parallel places increased demands on free space in the file system, in the database, and on the system resources).
• * The JSPM tool is used to update Java components and Portal content.
• * The SAINT tool was previously used to update ABAP software components and apply the needed Support Packages.

5. Installing SAP Enhancement Packages across the System Landscape
All activities must be performed in a set sequence:

1. Set up sandbox and perform SAP enhancement package and Support Package installation in one step. Get familiar with the new functionality.
2. Set up temporary maintenance system for the SAP EhP installation project for emergency corrections.
3. Perform installation in DEV.
4. Perform installation in QAS.
5. Perform installation in PRD & go-live.

*** Product version “EhP4 for SAP ERP 6.0/NW7.01″ should be used if all Java-based systems that contain SAP ERP 6.0 product instances can be updated to SAP Netweaver 7.0 EhP1.

You can use Trace function, ST01, you can trace the user activity and from the log you can see the authorization missing.

Start an authorization trace using the ST01 transaction and carry out the transaction with a user who has full authorizations. On the basis of the trace, you can see which authorizations were checked.

What is the difference between role and a profile?

Role and profile go hand in hand. Profile is bought in by a role. Role is used as a template, where you can add T-codes, reports….. Profile is one which gives the user authorization. When you generate a role, a profile is automatically created.

What is the use of role templates?

User role templates are predefined activity groups in SAP consisting of transactions, reports and web addresses.

What is the difference between single role & composite role?

A role is a container that collects the transaction and generates the associated profile. A composite role is a container which can collect several different roles.

Is it possible to change role template? How?

Yes, we can change a user role template. There are exactly three ways in which we can work with user role templates

1. We can use it as they are delivered in sap
2. We can modify them as per our needs through pfcg
3. We can create them from scratch.

For all the above specified we have to use pfcg transaction to maintain them.

Please explain the personalization tab within a role.

Personalization is a way to save information that could be common to users, I meant to a user role… E.g. you can create SAP queries and manage authorizations by user groups. Now this information can be stored in the personalization tab of the role. (I supposed that it is a way for SAP to address his ambiguity of its concept of user group and roles: is “usergroup” a grouping of people sharing the same access or is it the role who is the grouping of people sharing the same access?)

How to insert missing authorization? Ways?

su53 is the best transaction with which we can find the missing authorizations.and we can insert those missing authorization through pfcg.

Someone has deleted users in our system, and I am eager to find out who. Is there a table where this is logged?

Debug or use RSUSR100 to find the info.

Run transaction SUIM and down its Change documents.

How can i do a mass delete of the roles without deleting the new roles?

There is a SAP delivered report that you can copy, remove the system type check and run. To do a landscape with delete, enter the roles to be deleted in a transport, run the delete program or manually delete and then release the transport and import them into all clients and systems.

It is called: AGR_DELETE_ALL_ACTIVITY_GROUPS.

To used it, you need to tweak/debug & replace the code as it has a check that ensure it is deleting SAP delivered roles only. Once you get past that little bit, it works well.

How to compare the roles where created or defined in two different systems?

For role comparison both the roles must be in the same system, in same client

Transaction code SUIM -> Comparison-> Roles

If the roles are in different system, then transport the role into one of the system and do comparison. If no transport connection defined then, you can use the upload and download option in the PFCG

Steps for Role Comparing:

1. Run the t-code SUIM

2. Go To Comparison and select the option of roles

3. Click on Across systems option it will give option to select the sys name under Remote Comparison there enter the SYS ID between which system you want to do comparison and put the role name in compare role section then execute it will give you the result.

4. If there is any difference between the t-codes it will b in red color otherwise in yellow.

What is the procedure for creating new user which have all features define under SAP* user and which could allow me to make the configurations?

Creating new user with superuser authorizations.

1. Goto SU01 –
username : sapuser
|–>Create.

2. In default settings, give
:Mr
first name : sap
last name : user

3. Goto next tab,
give initial password :1234
repeat password : 1234

4. Goto profiles.
type- sap_all (say enter)
sap_new (say enter)
Then save….
See the message in status bar, (user created successfully)

5. Login with the new user. change the password. now this user contains all superuser authorizations

The administrator user cannot be used to log on to the J2EE Engine because it has been locked. How will you correct the situation?

To correct this situation, I had to use an emergency user account.
SAP* user account has full administrator authorizations, but this account doesn’t have a default password. It must be specified when account is activated. Once SAP* is activated, no other user can log in to the system.
Check properties on Config Tool (Edit UME):
- ume.superadmin.activated (set ‘true’);
- ume.superadmin.password (specify a password).
Restart Application Server.
You have all users locked onto ABAP system. How will you deal with this situation?

Make sure your login/no_automatic_user_sapstar profile value is set to 1.

Log on to host system and connect to database.
Use the following query:
- delete sid.USR02 where BNAME=’SAP*’ and MANDT=’xxx’;

Now SAP* user is generated again with default password “pass”.

How would you copy all users from DEV to PRD?

Execute transaction SCC8 and select the profile SAP_USER. Then specify target system and schedule background job. This will export all users from the source system in the form of request.

Now login to the destination system and enter tcode SCC6. Specify the request number generated while exporting and click on “prepare import”.

You can check logs in SCC3 transaction.

How would you start with SAP Implementation as an administrator?

There is no standard Implementation process, it purely depends on which methodology client have adopted for implementation. Starting from sizing of the servers:

1. Identify the number of users and type of users
2. Design the technical system landscape of servers
3. Do the sizing based on users, documents created.
4. Convert your sizing requirement in to Hardware requiremnet
5. Consider the backup procedure also
6. Then start with the setup of development landscape
7. Define client strategy, transport strategy, User management.
8. Fix the support package levels.
9. Tune the system for performence
10. set up the QA systems
11. Define client copy strategy
12. Setup the PROD systems
13. Apply for Pre Golive report
14. Monitor system of db load
15. Apply post golive report

What is SAP Enhancement packages? How it works?

SAP enhancement packages represent a new software delivery strategy that allows to add innovations on top of SAP ERP 6.0 without the need for fully upgrading the current release.

SAP enhancement packages are cumulative from a functional perspective: current SAP enhancement packages contain the entire content of earlier packages.
Few important things about SAP Ehp are:

• New functionality must be explicity switched on to become active in the system. SAP enhancement packages has no impact on existing business processes or user interfaces, as long as no business function has been activated. Once a business function is activated it is not possible to reverse it.
• Techincal usage describes a valid set of software components that must be installed together.
• New functionality delivered in Java software components is automatically active as soon as it is installed in the system. This might imply that in parallel it is necessary to activate a certain business function in the corresponding ABAP backend system when applying the EhP4 Java part. Check note 1160106 for more information.
• SAP ERP enhancement packages must be applied withi one queue, together with to required support packages. They can be installed as a normal maintenance activity together with support packages.

• Number of instances configured for your system
• Number of users working on the different instances
• Response time distribution
• Distribution of workload by transaction steps, transactions, packages, subapplications, and applications
• Transactions with the largest response times and database time
• Memory usage for each transaction or each user per dialog step
• Workload caused by RFC, broken down by transactions, function modules, and destinations
• Number and volume of spool requests
• Statistics about response time distribution, with or without the GUI time
• Optional: table accesses
• Workload and transactions used by users, broken down by users, accounting numbers, and clients
• Workload generated by requests from external systems

Call transaction ST03:

• Switch to advanced mode.
• Choose an analysis period.
• Choose an analysis view.
• Look at the DB time. It should not be more than 40% of the response time.

The following are important analysis views in transaction ST03:

• System load overview: general response time distribution across different task types
• Time profile: How does the response time react over the day? Are there peak times with bad response times?
• Transaction profile: Can you observe response time problems in general or only in certain transactions?

ST03 Workload Overview:

In the Workload Monitor you can also determine which transactions have accessed which database tables and how often. Since the number of statistics records greatly increases by logging table accesses of this type, this option is deactivated by default.

You should only activate it temporarily for individual analyses, and for individual transactions, since performance problems can occur in the statistics collector otherwise.

After installing an R/3 System, you can use transaction RZ20 to monitor the system. To monitor all systems of your system landscape centrally from one system:

1. Customize the alert monitor by choosing Tools > CCMS > Configuration > Alert monitor or calling transaction RZ21.
2. Then, to specify the remote systems by System ID and RFC destination (which must have been created beforehand), choose Technical infrastructure > Create remote monitoring entry.
3. Next, to change your monitor definitions (you can only change your own monitors), choose Tools > CCMS > Control/Monitoring > Alert monitor or call transaction RZ20.
4. Activate the maintenance function by choosing Extras > Activate maintenance function.
5. Then, double-click on the monitor and choose Monitoring change. Parameter R3 system defines which systems can be monitored by an alert monitor. Change parameter R3 system from (only the current R/3 System can be monitored) to (all R/3 Systems defined in RZ21 can be monitored). Save the changes.

It will help you monitor & use some other activities centrally.

What are the daily activities you have to do as SAP administrator?

1. Check that all the application servers are up : SM51 – SAP servers
2. Check that daily backup are executed without errors : DB12 – Backup logs overview
3. Check if SAP standard background jobs are running successfully: SM37 – Background jobs
4. OS monitoring : ST06 – Operating system Monitoring. Check CPU, Memory, Swap, Disk and Lan response time.
5. Extents monitoring : DB02 – Database monitoring. Check for max-extents reached
6. Check work-processes : SM50 Process overview. All work processes with a running or waiting status.
7. Check system log : SM21 System log. Check for errors ,warning, security, message-bends, database events.
8. Review workload statistics : ST03 – Workload analysis & ST02 – Tune summary instance
9. Check for any failed updates : SM13 – Update records
10. Check for old locks : SM12 – Lock entry list
11. Check for spool problems : SP01 spool request screen. Check for spool that are in request for over an hour.
12. Review and resolve dumps : ST22 ABAP Dump analysis
13. Check for users logged in : SM04 / AL08
14. Checking .trc file in SAP trace directory for block corruption on daily basis.
    C:\ORacle\sid\saptrace
15. Archive backup
    brarchive -f force -cds -c
    Insert the archive backup tape
16. Review NT system logs for problem
    -> NT system log- look 4 errors or failures
    -> NT security log- failed logon 2 sap servers
    -> NT Application log -look 4 errors or failures

Name the T-codes used for system monitoring.

ST22 – Check for the core dumps if any and report to the respective consultants and try to know why it happened.

SM21- Check  for errors.

SP01 – Check if any spool jobs have failed.

ST02 – Check if any swaps are happening, swaps are not good for performance.

ST04 – Check Database alert logs and Performance.

ST03 – Check for hit ratios and response times.

SM59 – Check for connectivity testing if there are other systems also connected to your SAP R/3 system

DB13 – Check if the database jobs have run successfully.

DBACOCKPIT – Database administration (includes DB13,ST04, ST06 too)

SM37- Check for any cancelled scheduled job and take action appropriately.

SM12 – Check for any pending locks from the previous days.

SM13 -  for any hanged updates, or updates pending for long or updates in PRIV mode.

What is archiving?

Archiving is a process when you archive old master/transactional records which are not in use any more from long time. You archive those records keep on some backup device. These records can be displayed, and only Display, can never be reloaded in tables again physically.
This will free up the space in tables from those records which are not in use any more but exist in tables physically.

What is reorganization?

Reorganization basically removes deleted data from tables. During different transactions you delete some records, which are deleted virtually but not physically. Even Archive process delete those records virtually.
So you run Reorganization to free up the space consumed by deleted records.

How do you find that an operation mode switch occurred?

• Go to sm50. If the no of dialog work processes or background work processes changes then an operation mode switch took place.
• Go to transaction sm63. Here you can see the time when the operation mode is set. You can guess when the operation mode switch occurs.
• Go to transaction RZ04, here you can see the list of operation modes and their time. You can guess that from here.
• Go to transaction rz03 , here you can see the current operation mode in which the server is running.
• Call transaction Code sm62. Then view system events. If there is an event called SAP_OPMODE_SWITCH then operation mode switch occurred at that time. If you click on activity log you can see the time and date when the event was triggered. It is time and date of operation mode switch

What is system refresh? When and why it is done?

The system refersh is nothing but the deletion of the client and replacing the data from other client. For example : you have clients 100, 200 and 300. Suppose when you want to refresh the client 100 you remove the client 100 and replace it with 200 0r 300 as per your reqiurement. Mostly the refresh of clients will be happen at the time of development stage.

System Refresh is a simplified term to Client Copy. Client Copy means copying the production client on to the quality to test the real data. As recommend by SAP this need to carried out every 3 months.