Interview Questions for SAP Basis

What is private mode? When does user switch to user mode?

Private mode is a mode where the heap data is getting exclusively allocated by the user and is no more shared across the system. This happens when your extended memory is exhausted.

What is osp$ mean? What if user is given with this authorisation?

OPS$ is the mechanism the <SID>adm users uses to connect to the database .

Why do you use DDIC user  not SAP* for Support Packs and SPam?

Do _NOT_ use neither DDIC nor SAP* for applying support packages. Copy DDIC to a separate user and use that user to apply them.

Can you kill a Job?

Yes - SM37 - select - kill

If you have a long running Job,  how do you analyse?

Use transaction SE30.

How to uncar car/sar files in a single shot?

on Unix:  $ for i in *.SAR; do SAPCAR -xvf $i; done

When we should use Transactional RFC ?

A "transactional RFC" means, that either both parties agree that the data was correctly transfered - or not. There is no "half data transfer".

What is the use of Trusted system. I know that there is no need of UID and PWD to communicate with partner system. In what situation it is good to go for Trusted system ?

E. g. if you have an R/3 system and a BW system and don't want to maintain passwords. Same goes for CRM and a lot of other systems/applications.

Let me know if my understanding below is correct: 1) By default the RFC destination is synchronous 2) Asynchronous RFC is used incase if the system initiated the RFC call no need to wait for the response before it proceeds to something else.

Yes - that's right.

But keep in mind, that it's not only a technical issue whether to switch to asynchronous. The application must also be able to handle that correctly.

Which table contains the details related to Q defined in SPAM? Is there a way to revert back the Q defined? If yes, How?

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.

What is a developer key? and how to generate a developer key?

The developer key is a combination of you installation number, your license key (that you get from http://service.sap.com/licensekey) and the user name. You need this for each person that will make changes (Dictionary or programs) in the system.

What is XI3.0 ? EXPLAIN XI = Exchange Infrastructure - Part of Netweaver 2004.

SAP Exchange Infrastructure (SAP XI) is SAP's enterprise application integration (EAI) software, a component of the NetWeaver product group used to facilitate the exchange of information among a company's internal software and systems and those of external parties. Like other NetWeaver components, SAP XI is compatible with software products of other companies. 

SAP calls XI an integration broker because it mediates between entities with varying requirements in terms of connectivity, format, and protocols. According to SAP, XI reduces integration costs by providing a common repository for interfaces. The central component of SAP XI is the SAP Integration Server, which facilitates interaction between diverse operating systems and applications across internal and external networked computer systems. 

How to see when were the optimizer stats last time run? We are using win2k, oracle 9, sapr346c.

Assumed DB=Oracle

Select any table lets take MARA here but you should do the same for MSEG and few others to see whether the dates match or not.Run the following command on the command prompt:-

  select last_analyzed from dba_tables where table_name like '%MARA%';

SAP Basis FAQ

Automatic CTS

Even though SAP does not recommend automatic imports, it is the most practical way of moving transports from a development system to a QA environment or to a special development system (although I wouldn't recommend auto imports to a production system for obvious reasons).

There are various methods for doing this. The most effective and simple method is using an OS script (shell/perl etc.) scheduled using cron for user sidadm. There are a couple of steps you need to take before setting up automatic imports.

1. Your entire project team should agree upon the overall strategy, frequency of imports etc.2. Resolve any issues with transport approvals (many shops don't care about traffic between DEV

and QA)3. Who is responsible for watching for errors and corrective actions (an email to the developer

works in this case)

Configuring outbound SAP to Internet mail Gateway (R/3 4.0 and above)

Step 1 (UNIX SETUP) Logon to your <DB_SERVER> as sidadm Change directory to /sapmnt/SID/global (or any directory globally available across all application servers) Create the following entries in file SAP_EMAIL_GATEWAY.sh and save the file#!/bin/sh GWCONFIG=/sapmnt/SID/global/SAP_EMAIL_GATEWAY.cfg export GWCONFIG /sapmnt/SID/exe/mlunxsnd $*Execute the  command: mlosmadm SAP_EMAIL_GATEWAY.cfg (enter the following information)System name : SID Client        : 200 Username : MAILADM Password : initpass Language : E Loadbalancing : Y Message Server : <central_instance_host_ Group name : LOGON GROUP1 Using SAPROUTER : N Trace Level (inBoound) : 0 Sendmail Command : <accept default> Codepage : <accept default Trace Level (Outbound) : 0 Update file : YStep 2 (SAP SETUP)

Logon to SAPSYSTEM (SID) via SAPGUI

Transaction SU01, create user MAILADM and password initpass, usertype CPIC Transaction SM59, Click Create

RFC Destination : SAP 4.5 INTERNET MAIL GATEWAY Connection Type : T Description : INTERNET EMAIL GATEWAY Hit RETURN Click EXPLICIT HOST Enter /sapmnt/P21/global/ SAP_EMAIL_GATEWAY.sh Save your entries

Transaction SCOT, click Edit--> CREATE NODESNode : EMAIL Description : SAP CONNECT NODE FOR EMAIL (continue) RFC DESTINATION: (choose SAP 4.5 INTERNET MAIL GATEWAY from the pull down menu) Choose radio button Internet Address area : *DOMAIN  (your intranet domain) Ccontinue Format : DOC, DAT, R3F, TXT, RAW,PPT,XLS (continue) Continue Set further address types : N Minimum waiting : 5 minutes Check both Node is in use', Node can resolve path references Continue Choose Goto--> Schedule Background Job Enter name for the job & save

Configuring outbound SAP to Internet mail Gateway (Upto R/3 3.1I)

SAP can be configured to send and receive emails from different sources. This section explains how to integrate SAPOffice with an external email system. This is in no way supplementing the online documentation available on the online documentation CD supplied by SAP but simplyfies the process to the bare Internet email must be configured and running prior to this. Email from SAP is forwarded to the users external email client  such as Eudora, Outlook etc.

You can configure inbound and outbound forwarding. Outbound flow forwards a SAP message (eg:update termination) via UNIX sendmail to the intended recepient. Inbound accepts a message from sendmail and places it in the users SAPOffice inbox. Many SAP shops prefer to configure outbound only.

Configuring outbound forwarding

SAP configuration

1. Create your RFC destination for outbound email using transaction SM59

RFC Destination         :  SAP_INTERNET_GATEWAYConnection Type         : TDescription             : SAP internet mail gatewayClick on 'Explicit Host' if you want on demand gateway dameon invocation.

Program                 : /sapmnt/SID/exe/mlunxsndTarget Host             : Enter hostname that runs your central instance.Click 'Test Connection' and you should see a successfull message.

Choose menu Tools-->Administration-->Management-->Process Technology-->Office-->Office Settings

Click Internet Gateway

Gateway Destination             : SAP_INTERNET_GATEWAYPath for configuration file     : /sapmnt/SID/exe/sap_mailSID.cfgReturn Address                  : <your company domain>.com

5. Click Internet Settings and fill in the following fields6. Save the settings7. Click Back8. Choose menu Office-->Addresses-->Communication Types9. Type in INT   over the Comm. type and Internet Mail over description.10. . Check Maintain and Send checkboxes  and Save your entries.

   

UNIX configuration

11. . cd /sapmnt/SID/exe12. .mlosadm sap_mailSID.cfg13. Client 00014. Username : MAILADM15. Password  : MAILADM16. Language : E17. System name : SID18. System number : <instance_number>19. Hostname  : <hostname>20. Gateway hostname: <central_instance_hostname>21. Gateway server sapgw<instance number>22. Sendmail Command : <path_to_sendmail_command>23. Update file : Y

Testing

1. Logon to SAP2. Execute transaction SO013. Write a message and send it to <your_internet_email_address>

If you don't see the mail in your internet mailbox, go back and review steps 1-12

FTP from ABAP

There are 2 ways of executing FTP from an ABAP (online or batch mode),

Initiated from the operating system. A script is available in the utility repository that explains how to do this very easily.Initiated from the ABAP itself  An example is given below.

1. Create a logical OS command 'zftp'  using transaction SM69. Make sure that you enable 'comand line parameter allowed' checkbox

2. Create a shell script called 'zftp' with the following lines

RMTHOST=`echo $2 | tr '[A-Z]' '[a-z]'`ftp -v $RMTHOST << EOF > /out/zftp.$$ 2>&1lcd /output $1byeEOF

3. Use the SXPG_COMMAND_EXECUTE function module to call this script (zftp) with the filename you want to transfer as the parameter. Eg:

call function 'SXPG_COMMAND_EXECUTE'exportingcommandname =tablesexec_protocol =exceptionsno_permission = 1command_not_found = 2parameters_too_long = 3...

Enable web based online documentaion (R/3 4.0 or above)

1. Install Netscape webserver or use an existing web server (requires administrators privelege)2. Create a directory called SAPDOCS4 under your web server document root.3. Mount the CDROM containing online documentation on your PC or your UNIX server.4. Recursively copy all files under /cdrom/docs/ to the SAPDOC4 directory under the web server

root.5. Create the following entries in your /usr/sap/SID/SYS/profile/DEFAULT.PFL

eu/iwb/installed_languages = EN eu/iwb/help_type=2 eu/iwb/server_win32=webserver.domain.com eu/iwb/path_win32=saphelp/helpdata

Restart your SAP system

How to access an external database from ABAP via DBLINK (ORACLE)

1. Using transaction SE11, create a table (ZTABLE) with the same fields as the table in the external database, make sure that the type and lengths of the fields are identical.

2. Using transaction SE11, create a view (ZTABLE_VIEW, projection view) using BASIS table ZTABLE

3. Using SVRMGRL>

create dblink REMOTE_DB as connect to remote_user identified by password; (database link created) drop table ZTABLE; (table dropped) create synonym ZTABLE for ZTABLE@REMOTE_DB; (synonym created)

Using transaction SE16 , type in ZTABLE_VIEW and hit RETURN

Enter  value in key fields and hit execute. (displays rows from the remote table)

Tips and Tricks

1. To see the complete text of an error/warning message on the SAPGUI status bar, right click on the message and drag left.

2. To prevent  your spool requests getting deleted from the BASIS cleanup jobs, you need to uncheck the Delete after print checkbox in the print control screen, execute transaction SP01, find your spool#, click on Attributes and change the Delete After date

3. Short cuts using the OK-code box.

%sc Search in page

%pc Download do local file

p+  Page upp-  Page downp++  Top of pagep--  End of page

----------------------------------------------------------|Tcode|Transaktionstext                                  |----------------------------------------------------------|ADOK |AM: System Administration Guide                   ||BALE |Area Menu for Administration                      ||BDMO |ALE CCMS Group Administration                     ||CATSX|Time Sheet Admin.: Initial Screen                 ||CICY |CTI Administration                                ||CJV6 |Maintenance: Version administration               ||CN84 |PS: Archiving project - admin.                    ||COA4 |PP: Archiving order - administration              ||CSADM|Content Server Administration                     ||FC_BW|Administrator Workbench                           ||FDTA |TemSe/REGUT Data Administration                   ||FDTT |Treasury Data Medium Administration               ||FO86 |Change active admin.contract fees                 ||FO8E |Create admin.contract event                       ||FO8F |Change admin.contract event                       ||FO8G |Display admin.contract event                      ||FO8H |Admin.costs acct sttlmnt simulation               ||FOART|REsearch: Administration Web-User                 ||HRCMP|Compensation Administration                       ||HRCMP|Budget Administration: Display                    ||HRCMP|Budget Administration: Change                     ||IM_AR|Admin. of App. Request Archives                   ||KA18 |Archive admin: assess., distr., ...               ||KE72 |Archive Administration: Line Items                ||KE73 |Archive Administration: Totals Recs               ||KPRO |KPRO Administration                               ||OAAD |ArchiveLink Administration Documents              ||OG00 |Personnel Administration Customizing              ||OG01 |Personnel Administration Customizing              ||OMSM |CS MM Set Up Administrative Data                  ||OOCM_|Compensation Administration Settings              ||OOML |Room Administration Mail Connection               ||OOPC |Administration: Personnel No. Check               ||OY22 |Create subadministrator  Customizing              ||OYEA |IDoc administration                               ||PA97 |Compensation administration - matrix              ||PA98 |Compensation Administration                       ||PA99 |Compensation Admin. - Release Report              ||PACA |PF administration                                 ||PAT1 |Personnel Administration infosystem               ||PC00_|CBS survey salary administrations                 ||PC00_|Tax Certificates - Administration 16              ||PP26 |Plan Scenario Administration                      ||PP2D |Administer Payroll Results                        ||PSO5 |PD: Administration Tools                          ||PUCA |PC administration for PF                          ||PVSEA|Administer Search Engine                          ||QD25 |Archiving Notifications: Admin.                   ||S002 |Menu Administration                               ||SA02 |Academic title (cent. addr. admin.)               ||SA04 |Name prefixes (centr. addr. admin.)               ||SA05 |Name suffix (centr. addr. admin.)                 ||SA07 |Address groups (centr. addr. admin.)              ||SA08 |Person groups (centr. addr. admin.)               |

|SA09 |Internat. versions address admin.                 ||SA10 |Address admin. communication type                 ||SARA |Archive Administration                            ||SBPT |Administration Process Technology                 ||SCC4 |Client Administration                             ||SCON |SAPconnect - Administration                       ||SCOT |SAPconnect - Administration                       ||SCUA |Central User Administration                       ||SCUM |Central User Administration                       ||SE78 |SAPscript: Graphics administration                ||SECST|Administration of Secure Memory                   ||SENG |Administration of External Indexes                ||SENGE|Explorer Index Administration                     ||SIAC1|Web Object Administration                         ||SLICE|Administer SAP Licenses                           ||SLWA |Translation Environment Administratn              ||SM14 |Update Program Administration                     ||SP12 |TemSe Administration                              ||SPAD |Spool Administration                              ||SPAT |Spool Administration (Test)                       ||SPHA |Telephony administration                          ||SPHB |SAPphone: System Administration                   ||SSAA |System Administration Assistant                   ||SSCA |Appointment Calendar: Administration              ||SSCA1|Appointment calendar: Administration              ||SSO2 |Workplace Single Sign-On Admin.                   ||SSO2_|Workplace Administration SSO2 Ticket              ||STMA |Proposal Pool Administration                      ||SURAD|Survey Administration                             ||SURL_|Personalization for URL Gen. Admin.               ||SUUMD|Display User Administration                       ||SWDC |Workflow Definition: Administration               ||SWEAD|Event Queue Administration                        ||SWEQA|Event Queue Administration                        ||SWEQA|Queue Administrator Maintenance                   ||SWIA |Selection rep. for work items(admin)              ||SWRK |Administrtation using work areas                  ||SWUF |Administration of Runtime System                  ||SWUL |Customizing: Process Administrator                ||SWUX |SAPforms Administration                           ||SYSAD|System Administration: Task List                  ||S_ALR|IMG Activity: CIC_V_CCMCTIADMIN                   ||S_ALR|IMG Activity: SIMG_EURO_ADMINUSER                 ||S_BCE|IMG-Aktivität: BCDIGSI_ADMIN                      ||S_PH0|InfoSet Query: Administration                     ||S_PH0|InfoSet Query: Administration                     ||S_PH0|InfoSet Query: Administration                     ||S_PH0|InfoSet Query: Administration                     ||S_PH0|InfoSet Query: Administration                     ||TBD0 |Datafeed: Adminster Archives                      ||TBD3 |Datafeed: Market data administration              ||TBD6 |Datafeed: Log file administration                 ||WE46 |IDoc administration                               ||WORKI|Administrtation using work areas                  |----------------------------------------------------------

What the difference between tcode SE09 & SE10?

SE09 transaction is for workbench transport request wherein the developers can track their changes or modifications to the workbench objects . 

Whereas SE10 is a customising transport request transaction.this is used for displaying customising requests. Sometimes this may be restricted to business analysts.

Proper way to delete a SAP client

Here goes: 

1. log into the client to delete  2. go into SCC5 and delete client  3. log into another client and delete entry with SCC4  4. reorg database to recover database space. 

Actually, if you check "on" the little "Delete Entry from T000" checkbox, you can skip step 3.

One other way of deleting a client which could give significant performance gain and save time is at OS level using - R3trans 

To delete a client 200, you have to create a command file "del200" with following entries 

Clientremove  Client = 200  Select * 

Place the command file in /usr/sap/trans/bin 

$ cd /usr/sap/trans/bin 

$ R3trans –w <log file name> -u 1 <command file name > 

e.g $ R3trans -w del200.log -u 1 del200 

To check the progress... 

$ tail -f del200   

Reorg the database post client delete

What is the best way to refresh QA from PRD?

How to make a system copy:

1. Take offline backup of both the server (source and target servers)

2. Verify the backup is successfully done.

3. Run the following command on source system. a. Login as <sid>adm b. svrmgrl c. connect internal d. alter database backup controlfile to trace; e. exit; f. Above command will generate a .trc file in /oracle/P01/saptrance/usertrace directory. g. Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file. h. Copy the controlfile.sql to target system. i. Edit the file and replace the entire source SID to target SID. j. Edit the reuse database command with the set database command

4. Copy the aft generated during the backup file from the source system to target system. (/oracle/<SID>/sapbackup) a. Change all the source <SID> to target <SID>.

b. Only don't change the backup volume name it must be target system <SID>. c. Copy the above aft file name line from the source back<SID>.log to target<SID>.log file.

5. Shutdown the target server instance.

6. From this onwards all the command on the target system only.  a. Login as <SID>adm b. run the SAPDBA  c. select J (Restore/Recovery) d. select B (Full restore and recovery) e. select A (Select backup of type) f. Select the offline backup which you want to restore. g. It will take some time to restore. h. Once the database is restored login as <SID>adm and run the  i. svrmgrl j. connect internal; k. startup nomount (if the database is already mounted shutdown it using the shutdown command) l. run the following command  m. @controlfile.sql (file name of the control file contains the CREATE CONTROLFILE statement) n. After the run the above command it should give the "Statement Processed) o. alter database open resetlogs p. shutdown q. Start the database and SAP services using startup.

7. After this you have to reconfigure the STMS.

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.

Do you have a SAP Basis Question?

Problems in Heterogeneous Setup

We Planning to go for hetrogenius setup.  Development server -  HP-UX11i,oracle9.2,sap47. Production server  -  SUN Solaris with same oracle and sap version My issue is that, will I face any problems in this setup?   Because right now developments are going on HP-UX.

Venkatesh

I am not in a hetro-geneous setup.   But a similar installation I have already visited, which one of the big installation in Bangalore, they used Sun solaris as dev and HP UX as PRD.   But no problems.  Logically SAP system just  looks for where the data is stored and works on TCP/IP. It just does not matter where the database resides for development and production.   The transport mechanism just transports from the development client to productive client. So I assure you 100% you can plan this. This is supported by SAP.   You can even plan NT as development machine. It just works fine.   But some advantages are available if you have similar systems.   1. When updating patches for a particular os/db combination , you have a chance to see how it works, before trying      it on productive system.   2. You learn a lot on installation, sizing, many other related issues at the time of development, so that you can easily       sort it our at the time of installation of  prd system.   The above cannot be told as advantageous, but take a note of these.  After all  it is a matter of cost + convenience!   I am on NT + SQL Server with SAP 4.7 Ent. and its works fantastic without any problems.  

Steps For SAP Client Copy / System Refresh

Before doing a client copy, you need to prepare the following :-

1. Find the source client space with the client size custom program which can be implemented using the rel. note:      Find the space of the client - '0118823'. This will give you the size of the source client. 

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.      Please find the rel. notes related to performance improvements for cluster tables in OSS.

5. Do import and post processing.      Note: Export may take 10 to 20 hr. for 50gb of data      import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on     your system performance. 

Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process. 

Note :-

If it is a fresh installation, do this --

1.  SCC4 --> Create client no. and fill other details. 2.  Logon to the newly created client with SAP* and PASS as password. 3.  SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client <as created just now>. 4.  Preferably do a test run initially to check if it can go well. 5.  As a care check space in databases.

What are step and procedure to create a client & to take a client copy from source to target.

By: Kavitha.G

If you are copying from same system then flow the below steps:

1. Create the client in Tcode scc4. 2. Before that create a logical System in BD54. 3. Login in the newly created client with      user Name : sap*  and password  : pass 4. Use the Tcode sccl to copy the client.if you are not familiar with the client copy.  Try a test run and then schedule it in background. 5. You can select the needed profile. 6. To view the log files use the tcode scc3.

If you are using different system then create a rfc connection in sm59.test the connection and then continue from the 1st step You can also import and export a client.  Use scc7 for importing from the client and scc8 fro exporting from the source client

What is system refresh when and why it is done?

System refresh and client copy can be the same thing.  Normally when you want to refresh a system this normally means refreshing the clients using a client copy like SCCL or SCC8.  

A system "copy" is very different as this is far more involved than a simple "client refresh"

  Imagine you have a DEV and a PRD system and after 6 months the data in DEV is very old so you would perform a client copy SCC8 from PRD to DEV using a profile that copies the application data from PRD to DEV - it actually deletes the data and replaces it with data from PRD.  If however your DEV system died and needed to be completely rebuilt, you would use "Homogeneous System Copy" - you install the OS, Database and SAP and then process the system copy - which makes a complete copy of PRD (all clients)   Client copy - a single client refresh from PRD to DEV - can be just application data, or user data, or configuration or any combination you choose system copy - all clients 100% copied PRD to DEV

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.

The process to carry out the same is as follows:  1. Create a client on quality system using txn scc4

 2. Create a RFC between Production system and Quality System (need to create on quality system)  3. Login to the newly created client using sap* and pass as a password  4. Txn sccl to start the client copy. You can test the client copy by selecting the test run option. (test run will estimate the time taken for the activity).

Tips by : Shriniwas Yannam, Perala

Copy a Client into a Stand Alone System

How to copy a client into a stand alone system?

The scenario is I have a 2 system landscape. I want to copy an existing client from DEV to a standalone system for some demo purposes.

There is an option for Client TRANSPORT which will help you perhaps:

A client transport differs from a remote client copy in that it does not use RFC. Like a remote client copy, however, a client transport is used to copy data between different R/3 Systems.

A client transport consists of two steps. First, a client export extracts client data from the source client to files at the operating system level. Second, the data is imported from the operating systemfiles into the target client.

To perform a client export, proceed as follows: 

Log on to the source client. From the R/3 initial screen, choose:

*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport*(r) *Client Export*. Select the data to be copied using a profile.

Indicate the target system to which the client will be copied. (The target system must be defined in TMS as part of the transport domain.)

Begin the client export. As copying is a lengthy process, use scheduled background processing. The client export performed in the source system <S-SID>, exports the client data asynchronously bycalling the transport program tp at the operating system level. This export process will generate up to

3 data files at operating system level:

. RT< number >; this file contains client-specific data

. RO< number >; this file contains Cross-client data

. RX< number >; this file contains SAPscript texts

Depending on the type of data selected through the client transport profile, the client copy command

files added to the buffer of the target system are

<S-SID>KO<number>; this file is for cross-client data

<S-SID>KT<number>; this file is for client-specific data

<S-SID>KX<number>; this file is also for client-specific data

The client export change requests are not imported when an Import all takes place. Therefore, you must import these requests into the target client using TMS. You must import the data in the following order: first cross-client data, then client- specific data.

After the import process has completed, post-import activities are required possible for object generation steps. After completing the import, log on to the target client. From the R/3 initial screen, choose: *Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport *(r) *ImportEditing*

To display client transport logs, use the Transport Organizer.During client transport, a Repository consistency check can be performed by clicking the RFC system check button in Transaction SCC8.  If inconsistencies are detected, a list of the ABAP Dictionary tables definitions missing in the target system is generated. This will help your recognize in advance formal problems that may occur during the import of the source data.

SAP Basis Tips by : Jaswant Purba

Copy users from DEV to PRD

1.   Login to the client in your DEV system from where you want to copy.

2.   Execute scc8. Select the profile sap_user.        Specify the target system.       Click on 'schedule as background job'.

3. Specify the background server name i.e. the server name where your DEV system is available.

4. Click on 'schedule job' button.      Verify the things and click on 'continue' button.

5. You will have options to specify the start time.      Specify to suit your convenience.     You can see the log in scc3.

6. Login to the destination client and execute scc6.      Specify the request number which was created during scc8.      You need to specify only one request number. Other(s) will be taken automatically.     Click on 'Prepare import'.

7. Specify the target client and click on 'Import'.      Log can be checked in scc3.  

Best regards, SAP Basis, ABAP Programming and Other IMG Stuff

1. How to lock the client from logon 2. How to see the all the users connected per day (with the activities they have done and resource utilization)

I cannot answer the first straight away, but the second questions, there are many available SAP transactions. 

use STAT very useful and many options available if you use them correctly.  

1. I don't know how how to lock the client, but you can lock the system with "tp locksys <SID>" and unlock it with "tp unlocksys <SID>". You can also stop the service, but then noone can login including yourself.  However, I had problems with tp locksys when applying some Hot Packages and exporting client. It wouldn't work with system locked. I didn't try, but a   simple ABAP that locks and unlocks all the users in table usr02 (with exceptions of yourself, SAP*, DDIC... - ofcourse) might be an interesting idea.

2. STAT transaction  

You can lock the system thro "tp locksys" (Transport Utility). Check the other options of "tp" command for locking the specific client under the system thro "tp help".  

With this solution I can lock the whole system, but not specified by client. Send me in more detail....  

There's no way to lock a client. You have to lock all users from loging in of this specified client. The way you do is by user administration setting the lock.  

We can lock a client using SCCR_LOCK_CLIENT and unlock SCCR_UNLOCK_CLIENT functions.

Once we run this functions with a client as input , that client will be locked/unlocked. Actually this function set flag '' Client is locked temporarly for client copy" in client maintanance menu. And the client will be available for users other than DDIC and SAP*. If you try to login in that client as any user , system gives message that ' Client locked temporarly'..  

Is there any t-code to lock a client?

There is no direct tcode to lock a client. the easiest way to lock a client is  1. run tcode SE37 2. type function module name - SCCR_LOCK_CLIENT 3. enter the Client No. 4. execute the function module.

SAP 4.7 Enterprise Install Failure "FRF-00007

SAP 4.7 Enterprise Install Failure "FRF-00007  Unable to open RFC connection"

During the Install of SAP 4.7 Enterprise the installation fails with "FRF-00007  Unable to open RFC connection" when you are prompted to enter the DDIC password.

The solution I found was that you need to stop the install then log ito SAP with the User SAP* with password - "06071992" then change the DDIC password to whatever you want.

Once done restart the install and continue to the stage where you need to install the DDIC password, enter the changed password and the installation will continue without errors.

The only OSS notes related to this was "Press the continue button" and the installation may continue, or restart the installation. 

With Compliments from:

SAP Installation Procedure on WIN 2k Adv Server

With Compliments by: Bhanu Prakash Pogula Email:  bpogula@sify.com

INSTALLING HARD DISK ( IF U ARE TRYING TO LOAD SAP ON A SEPARATE HDD)

Connect HDD with cableWin 2000 installation.1.      Go to bios set up by pressing continuously clicking del on start.2.      change the first bootable device to CD.3.      insert the CD and RESTART system.4.      click any key to boot from CD.5.      click ENTER6.      click ENTER again7.      Click on C ( to continue)8.      click on F8 ( to agree)9.      partitions C: 4197Mb, D 12000Mb, E 6000Mb10.     select C drive11.     click ENTER to install12.     click ENTER again to continueautomatically restarts, set up continues.13.     click on NEXT14.     click on NEXT15.     click on NEXT16.     key RBDC9-VTRC8-D7972-J97JY-PRVMG17.     click on NEXT18.     TYPE no of concurrent connections  919.     click on NEXT20.     TYPE COMPUTER NAME 46IDES21.     click on NEXT22.     remove IIS (deselect)23.     click on NEXT24.     enter date & time25.     click on NEXT26.     finish

WINDOWS CONFIGURATIONCreating partitions for new disk.STARTà PROGRAMMESà ADMIN TOOLSà COMP MANAGEMENTà DISK MANAGEMENT1.      right click on unallocated space.2.      click on CREATE PARTITIONS, 3.      click on NEXT4.      click on NEXT5.      type 11320 (partition size)6.      click on NEXT7.      click on NEXT8.      type file system NTFS9.      click on quick format10.     click on NEXT11.     click on FINISH12.     again right click on unallocated space13.     repeat the exercise from  point 5 but for complete size 

note C drive contains operating systemE/D drive contain 46C softwareS drive contains SAP software..

PERFORMANCEMY COMPUTERà propertiesà advanced à performance optionsàchange,1.      Select S drive.2.      type initial =1600& max =16523.      click on SET    4.      click on OK5.      click on OK6.      click on OK

NETWORK SETTINGSSTARTàSETTINGSà CONTROL PANELà ADD/REMOVE HARD WARE, 1.      click on NEXT2.      click on NEXT3.      select ad a new device4.      click on NEXT5.      select (now I want to select from Hardware list)6.      click on NEXT7.      select network adaptors,8.      click on NEXT9.      select MICROSOFT10.     click on NEXT11.     click on NEXT12.     click on FINISH13.     close all windows14.     right click on MY NETWORK PLACES, 15.     go to properties, 16.     right click on local area connections17.     should be able to see Microsoft loopback adaptor on the screen.18.     select properties19.     select TCP/IP20.     click on properties21.     select ( use the following IP addresses)22.     type IP addresses 198.1.1.123.     subnet mass 255.255.255.024.     click on OK25.     select show icon on Task bar26.     click on OK27.     close all windows.HOST FILE CONFIGURATION1.      go to WINDOWS EXPLORER2.      select C drive, WIN NT, system 32 , DRIVERS, etc3.      double click on HOSTS4.      open with note pad5.      go to end of the page 6.      type IP address 198.1.1.17.      press TAB once8.      type 46cides9.      press TAB twice10.     click on SAVE11.     click on EXIT12.     RESTART sytemSoftware contains three folders

1.      46cides ( a. KERNEL, b. ORACLE 817, c.ORACLE  PATCHES2.      DB EXPORT3.      SAP GUI

ORACLE INSTALLATION1.      46CIDESàoracle 817à NTài386àsetup run the set up by double clicking2.      click on NEXT3.      source path …………destination path : S:\oracle\ora814.      click on NEXT5.      click on NEXT6.      click on NEXT7.      type GLOBAL DATA BASE NAME : ORACLE8.      click on NEXT9.      click on INSTALL10.     click on OK11.     click on EXIT12.     click on YES13.     close all windows14.     startà programsàadmin toolsà services15.     select ORACLE SERVICES16.     select all ORACLE releated services ONE BY ONE.

ORACLE PATCHES46CIDESà ORACLE PATCHESàPATCHà DISK1à INSTALLà WIN 321.      set up (double click)2.      click on NEXT3.      click on NEXT4.      click on INSTALL5.      click on INSTALL6.      click on EXIT

KERNEL INSTALLATION46CIDESàKERNELàNTà I386à MMC1.      double click on IMMC2.      click on NEXT3.      I agree4.      click on NEXT5.      click on NEXT6.      click on NEXT7.      click on FINISH46CIDESàKERNELàNTà I386à NT PATCH1.      double click on R3DLLINS2.      click on Ok3.      close all windows4.      RESTART46CIDESàKERNELàNTà COMMONà 1.      double click on R3 SET UP 2.      type SAP SYSTEM NAME IND3.      click on NEXT4.      click on NEXT5.      click on NEXT    at 85%6.      click on NEXT    automatically logs off7.      login and control+alt+del

CENTROL INSTANCEStartàprogramsàsap system for INDà install CENTRAL INSTANCE

1.      click on NEXT2.      type instance no OO,3.      click on NEXT4.      click on NEXT5.      click on NEXT6.      click on NEXT7.      click on NEXT8.      click on NEXT9.      click on NEXT10.     click on NEXT11.     click on NEXT12.     type LOCATION OF KERNEL CD   E:\46cides\kernel13.     click on NEXT14.     password AAA           AAA15.     click on NEXT16.     password AAA      AAA17.     click on NEXT18.     select NO LDAP SUPPORTS19.     click on NEXT20.     click on NEXT21.     click on NEXT22.     click on NEXT23.     click on  EXIT when finished

DATA BASE INSTANCEStartà programsà SAP set up system for INDà install database instance1.      click on NEXT2.      click on NEXT3.      click on NEXT4.      click on NEXT5.      click on NEXT6.      click on NEXT7.      click on NEXT8.      click on NEXT9.      click on NEXT10.     click on NEXT11.     click on NEXT12.     click on NEXT13.     click on NEXT14.     click on NEXT15.     click on NEXT16.     type location of CDS  for KERNEL  : E:\ 46cides\KERNEL for EXPORT  : E:\DBEXPORT17.     click on NEXT18.     password AAA      AAA19.     click on NEXT20.     click on NEXT21.     click on NEXT22.     click on NEXT23.     click on EXIT  at 32%24.     log off25.     log in26.     user à ind adm27.     passwordà AAA

28.     OKWINDOWS EXPLORERà C:\USERS\IND ADM\INSTALL\R3 SET UP FILE1.      double clik on R# set up file2.      select database R3S3.      open4.      type pass word AAA         AAA5.      click on NEXT6.      at 91% password AAAAAA7.      at  93% start MMC8.      click on NEXT9.      at 100% EXIT10.     click on STOP MMC11.     restart system

POST INSTALLATIONE:\apgui320\gui\windows\win 32\setup(double click)1.      click on NEXT2.      click on INSTALL        3.      click on FINISH4.      click on SAP logon5.      select NEW6.      type DESCRIPTION : 46CIDES7.      type application server : 46CIDES8.      type system no : 009.      start MMC

10.     close MMC11.     log in SAP12.     client 000, user sap* password 0607199213.     txn code SM28 14.     ENTER ( TO CHECK ERROR)15.     RESULT : NO ERROR REPORTED ( in installation)

STMSDescription à StudentClick on SAVEGo to overviewà transport routesSelect display change mode (second icon)Configurationàstandard configurationà single system ( main menu)Click on EnterConfigurationàdistributeàactivateClick on EnterF3 (to go back)

RZ 10 Utilitiesà import profiles of active serversClick on EnterClick on F3 (to go back)Profile  click on F4Select INDà DVEMGS00à46CIDESSelect EXTEND MAINTà changeSelect create paramaeters9 icon)Type paramter name : rdisp/max-wprun-time Type parameter value ; 3000

Copy iconGo backClick Yes

CREATE PARAMETERParamater name : abap\ field exitValue ; YESSelect COPY icon, go back à YESCreate parameter: login/system-client: 800select copy iconàgo back à yescreate parameter:eu/iwb/installed/languages:ENselect COPY icon – go back à YESagain go backclick on YESclick on SAVEclick on YESclick on ENTERclick on ENTER

(USER CREATION)TXN : SU01user : sapuserselect : create icon

address                 logon datatitle                   go on clicking ENTER no of timesfirst name              initial password : abclast name               repeat pass word : abc

DEFAULTSLogon language          : EnOutput device   ; LP01Select : Out put immediately & decimal

PROFILESType 1. SAP – ALLTYPE 2. SAP – NEWSAVELog off from SAPLogin to SAP

type     user : sapuser     password : abcnew password : abaprepeat password : abap

txn : SALEIMGàerror handlingàbasic work flow settingsSelect AUTOMATIC CUSTOMIZING iconGo backTxn 00w4Select DISPLAY CHANGE MODE iconCreate icon

CREATEPrefix no       978System ID       INDClient          000Click on SaveLocal objectCancel    X

CREATEPrefix no       972System ID       INDClient          800Click on SaveLocal objectCancel    X

TXN SE 38

Program name : Z FIRSTCREATEACCESS KEY : 36687663221261278694TITLE : DEMOTYPE : EXECUTORClick on SAVE

LOCAL OBJECTLog off from SAPLog into SAPClient          : 800User            : sapPass word       : 06071992

RUN txn SU01  for 000 client

Log off from SAPLog into SAPClient                  : 800User                    : sapPass word               : abcClick on ENTEREnter new password : abapLogoff Stop MMC

Steps for Creating Package

How to create transport package in R/3?

By: Venkat

Steps for Creating Package:   1. Run the SE80 T-code in the R/3 system. 2. Click on Edit Objects option on the top of the window. 3. Select "Development Coordination" in the Object selection window. 4. Select "Package" radio button and provide the package name(like any name: "BIDEV"). 5. Click on "Create" icon. 6. Fill the required details ( Short description, Appli.Component, Software Component) 7. Select "SAVE" Icon. 8. It will generate the10 digit New Transport Request: " BI7K900005"  9. Click on Continue.

Menu Path: Go to SE80 -> Edit Object (button) -> Development Coordination Tab -> Enter Package name and then press the create button

Saposcol Is Not Running    

Basis Ticket :

We have the ECC 5.0 installed on the HP UX. Whenever I am trying to run the t-code ST06 for the application server of the production, I am getting one message "SAPOSCOL is busy, try again". I am able to get the run the ST06 for other application servers.  The current version what we have for Saposcol is : Version: COLL 20.87 640 - hpxOscol 07/2003. It will be a great favour if anybody can provide me the steps from the scrach in how to run the SAPOSCOL.

1) login as <sid>adm

2) check if your saposcol is running at unix level ps -ef | grep saposcol

3) go to /sapmnt/NPD/exe

Check if saposcol file is existing Check the owner and the permission of the file

To start SAPOSCOL with the command saposcol (or saposcol -l). 

Saposcol can run independent of the SAP system, so you can try to start it individually using:

Try to start saposcol with command saposcol -l You can know status of the saposcol by saposcol -s and stop it by saposcol -k

---

Try to check, if you have cleaned up Share memory present in /usr/sap/tmp/dev_coll & try to get latest patch of SAPOSCOL.

Shared memory cleanup can be done as follows:

1) Login with the user <sid>adm and perform these steps saposcol -d Collector > clean Collector > quit saposcol -k to stop the collector. Before restarting saposcol -d Collector > leave (You should get a message Shared memory deleted) Collector > quit cd /usr/sap/tmp

mv coll.put coll.put.sav cd saposcol

"coll.put" ,if this file contains the old shared memory and should be deleted in order to get a clean start. Please look at the SAP Note 548699 and follow point 7 very carefully:

If you are unsuccessful in clearing shared memory, please try the following commands to clear the shared memory:

2) $ saposcol -kc $ saposcol -f If this doesn't work, then try:

3) cleanipc 99 remove on the O/S level (Check note #548699 first)

4) If not you have to do a OS level restart to fix the issue.

Also check if new saposcol can be applied as per Note 19227

Disable SAP USERS to logon multiple times

How to block a user id being logging in for more than twice?  i.e. I must restrict the user to be logged in at a time not more than twice (Not sessions, Loggins only).

Set the parameter in RZ10.

login/multi_login_users             = set to 1 to activate 

login/disable_multi_gui_login    = you can put a list of users that should be allow to logon multiple times

List the user IDs separated by commas ",".

Do not leave space characters between user IDs.

Restart the R/3 instance to see the changes.

Do you have a SAP Basis Question? 

Hi Basis Sappers,

If you have a SAP Basis Administration question, please feel free to asked it in the SAP Basis forums.

Just send an email (with a relevant Subject Title) to the many helpful SAP Basis Peers in the forum. 

The email for posting a new message is:  sapbasiscomponents@yahoogroups.com 

If you are still not a member, just send a blank mail to: sapbasiscomponents-subscribe@yahoogroups.com 

Maximum No. Of SAP Session Per User

You set this Parameter : rdisp/max_alt_modes in transaction RZ10.

Add in the above parameter in the Instance Profile - Options Extended Maintenance.

Restart the R/3 instance.

The default maximum no. of sessions in 4.6x is set as 6 session per user.

Most company will reduced the number of session per user but not increase it.  

Best regards, SAP Basis, ABAP Programming and Other IMG Stuff http://www.sap-img.com

Suppress Multi Login / Set Minimum Password Length

Suppress SAP Multi Login Message 

You can suppress the multi login message by setting the parameter in the instance profile. 

It is necessary if your company allows a single users to have multiple login and there tends to be cases where users will choose Options 1 which terminates the rest with the same user IDs.  This can result in loss of data as the users may have not click the save button.

Use transaction code 'RZ10'.

Parameter name : login/multi_login_users

In this parameter, enter the name of all the users separated by "," comma for which you want to suppress the message while multi login with the same user IDs.

Take note that the multi login counter still counts even though you have suppress the message.

Currently to login into SAP, minimum password length = 3 characters.  How to define/change the minimum password to be 8 characters?

by: Rajdeep

To change parameter:

1.go to RZ10 2.Select instance profile---->Extended mantainence--->change  3.In next screen click on create parameter,type login/min_password_lng and click on change/display  4.Then it will show the default value  5.In the parameter field put ur parameter.SAVE the changes  6.Reboot the application server .                  

User Administration:

SU01 User MaintenanceSU01D User DisplaySU02 Maintain Authorization ProfilesSU03 Maintain AuthorizationsSU05 Maintain Internet usersSU10 User Mass MaintenanceSMLG Maintain Logon GroupSUPC Profiles for activity groupsSUIM Info system AuthorizationsPFCG Profile GeneratorPFUD User Master Data Reconciliation

Client Administration:

SCC3 Checking Client Copy LogSCC4 Client Administration

SCC5 Client DeleteSCC7 Client Import Post-ProcessingSCC8 Client ExportSCCL Local Client CopySCC9 Remote client copy

Database Administration:

DB01 Analyze exclusive lock waitsDB02 Analyze tables and indexesDB12 DB Backup MonitorDB13 DBA Planning CalendarDB15 Data Archiving: Database Tables

Transport Management System:

STMS Transport Management SystemSE01 Transport and Correction SystemSE06 Set Up Workbench OrganizerSE07 CTS Status DisplaySE09 Workbench OrganizerSE10 Customizing OrganizerSE11 ABAP/4 Dictionary MaintenanceSE16 Data BrowserSE80 Repository BrowserSM30 Call View MaintenanceSM31 Table Maintenance

Background Jobs Administration:

SM36 Define Background JobSM37 Background Job OverviewSM39 Job AnalysisSM49 Execute External OS commandsSM62 Maintain EventsSM64 Release of an EventSM65 Background Processing Analysis ToolSM69 Maintain External OS Commands

Spool Administration:

SP01 Output ControllerSP11 TemSe directorySP12 TemSe AdministrationSPAD Spool Administration

Other Administration Tcodes:

AL11 Display SAP DirectoriesBD54 Maintain Logical SystemsOSS1 Logon to Online Service SystemSALE IMG Application Link EnablingSARA Archive ManagementSICK Installation CheckSM14 Update Program AdministrationSM35 Batch Input MonitoringSM56 Number Range BufferSM58 Asynchronous RFC Error LogSM59 RFC Destinations (Display/Maintain)SAINT SAP Add-on Installation ToolSPAM SAP Patch Manager (SPAM)SPAU Display modified DE objects

SPDD Display modified DDIC objectsST11 Display Developer Traces

Daily monitoring TCodes:

AL08 Current Active UsersSM12 Display and Delete LocksSM13 Display Update RecordsSM21 System LogSM50 Work Process OverviewSM51 List of SAP ServersSM66 System Wide Work Process OverviewST22 ABAP/4 Runtime Error AnalysisST01 System TraceST02 Setups/Tune BuffersST04 Select DB activitiesST05 Performance traceST06 Operating System MonitorST10 Table call statisticsST03 Performance, SAP Statistics, WorkloadSU56 Analyze User Buffer

Other Monitoring Tcodes:

OS01 LAN check with pingRZ01 Job Scheduling MonitorRZ03 Presentation, Control SAP InstancesST07 Application monitorSTAT Local transaction statistics

Other Useful Transactions Codes

AL22 Dependent objects displayBAOV Add-On Version InformationSA38 ABAP reportingSE38 ABAP EditorHIER Internal Application Component Hierarchy MaintenanceICON Display IconsWEDI IDoc and EDI BasisWE02 IDoc displayWE07 IDoc statisticsWE20 Partner profilesWE21 Port definitionWE46 IDoc administrationWE47 Status Maintenance$TAB Refreshes the table buffers$SYNC Refreshes all buffers, except the program buffer

How To Do the TMS Configuration?

We have two systems with version ECC 5.0

The SID is XY1 - Development & Quality                  XY6 - Production

Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?

How can I make thro it?

First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure ------------------ 1. Login to the system with sap* in client 000 2. Goto SE06. 3. Click Post installation activities 4. Goto STMS 5. It will ask for Domain controller name. 6. Enter DOMAIN_<SID> as domain controller name and enter the description.  7. Click Save button

Steps to add the other system with Domain controller ---------------------------------------------------- 1. Login to system with sap* in client 000 2. Goto SE06 3. Click Post installation activities 4. Goto STMS 5. It will ask for Domain controller name. 6. Enter System ID of the Domain controller 7. Enter DOMAIN_<SID> as domain controller name and enter the description.  8. Click Save button  9. Login to Domain controller system  10. Approve the added system.

SAP Basis Tips by : Chandrasekaran

The SID is XY1 - Development & Quality                  XY6 - Production

Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?

How can I make thro it?

First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure ------------------ 1. Login to the system with sap* in client 000 2. Goto SE06. 3. Click Post installation activities 4. Goto STMS 5. It will ask for Domain controller name. 6. Enter DOMAIN_<SID> as domain controller name and enter the description.  7. Click Save button

Steps to add the other system with Domain controller ---------------------------------------------------- 1. Login to system with sap* in client 000 2. Goto SE06 3. Click Post installation activities 4. Goto STMS 5. It will ask for Domain controller name. 6. Enter System ID of the Domain controller 7. Enter DOMAIN_<SID> as domain controller name and enter the description.  8. Click Save button  9. Login to Domain controller system  10. Approve the added system.

Post Installation Steps For ECC 5.0

What are the post installation steps after I have installed the Central Instance and Database instance?

Initial Consistency Check SM28 1.      Logon to the newly refreshed SAP system and run transaction SM28 2.      Ensure that no errors are reported.  Otherwise, take the necessary steps to correct the problems.

Edit Batch Jobs 1.      Set the fields as follows Job name: RDDIMPDP* User name: * Job Status: Released and Ready checked off, all others unchecked Fr:  01/01/0001 To:  12/31/9999 Or after event: * 2.      Press <F8> to execute the query

3.      Highlight the first job in the list and press the <CTRL>+<F11> to change the job. 4.      Examine the Exec Target field. a.      If the box is empty, press <F3> to exit b.      If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save 5.      Repeat Steps 3 and 4 *for* each additonal job listed.

Workbench Organizer Reconfiguration 1.      Logon on to client 000 of the newly refreshed system with DDIC.

SE06 1.      Select the Database Copy or migration option 2.      Press the Post-installation Processing button. 3.      When prompted Do you want to re-install the CTS?, press the Yes button 4.      When prompted *for* the Source System of Database Copy?, make sure that the <SID> of the production system is selected.  Press the checkmark button to continue. 5.      When prompted Change originals from PRD to QUA?, press the Yes button 6.      When prompted Delete TMS Configuration?, press the Yes button 7.      When prompted Delete old TMS configuration?, press the Yes button 8.      When prompted Delete Old Versions of transport routes?, press the No button

TMS Configuration 1.      Logon on to client 000 of the newly refreshed system.

STMS 1.      Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed 2.      The information on *this* screen is automatically filled out from information provided during the SAP installation and should be correct.  If it correct, then enter a description *for* the system and press <CTRL>+S to save.  Otherwise, press the Other configuration button  and manually configure. 3.      From the Overview menu, select Transport Routes 4.      From the Configuration menu, select Adjust with Controller 5.      Press the Yes button when prompted *if* you want copy the transport routes from the controller.

Import Printers 1.      Logon on to the production client of the newly refreshed system.

STMS 2.      Press <F5> to go to the *import* Overview. 3.      Double click on the <SID> of the newly refresh system 4.      From the Extras menu select Other Requests, then Add. 5.      In the Transp. Request box, enter the transport number containing the printer definitions that was exported.  Press <Enter> to save. 6.      Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import. 7.      In the Target client box, enter the productive client of the newly created system.  Press <Enter> to save. 8.      Press the <Yes> button to start the transport.

Client Configuration SCC4 1.      From the Table view menu, select Display -> Change 2.      When warned that the table is cross-client, press the checkmark button. 3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066) 4.      Define client as follows: Client role:  Test Changes and transports *for* client-specific object:  Changes without automatic recording

Client-independent object changes:  Changes to repository and cross-client customizing allowed Protection: Client copier and comparison tool:  Protection level 0 Restrictions when starting CATT and eCATT:  eCATT and CATT allowed 5.      Press <CTRL>+S to save. 6.      Repeat steps 4 through 6 *for* any additional clients

Set System Change Option SE06 1.      Press the System Change Option button. 2.      Set the global setting to Modifiable 3.      From the Edit menu, select Software Components Modifiable 4.      From the Edit menu, select Namespaces Modifiable 5.      Press <CTRL>+S to save.

Import Users STMS 1.      Press <F5> to go to the Import overview 2.      Double click on the <SID> of the newly refreshed system. 3.      Press <F5> to refresh the list of transports 4.      Locate the transport in the list containing the user exports done before the start of the refresh. If the transport is NOT in the list, then from the Extras menu, select Other requests then Add.   Enter the transport number and press <Enter>.  Then press the Yes button to add the transport. 5.      Highlight the transport and press the Import request icon . 6.      At the client *import* screen, enter the target client and then press the Import button 7.      Press <Enter> to confirm that the *import* will proceed

SCC7 1.      Run the Post Client Import Processing 2.      The transport number should be the same as that of the transport started in STMS 3.      Schedule the job to run in the background.  Do NOT schedule it to run immediately.  We need to modify the job before it can be released. 4.      Press <CTRL>+S to save.

SM37 1.      Set the fields as follows Job name: CLIENTIMPORT* User name: * Job Status: All options checked Fr:  01/01/0001 To:  12/31/9999 Or after event: * 2.      Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job. 3.      Press the Step button. 4.      Select the RSCLXCOP line and press <CTRL>+<SHIFT>+<F7> to modify that step. 5.      In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP). 6.      Press <CTRL>+S to save the changes 7.      Press <F3> to go back to the main job screen. 8.      Press the Start condition button. 9.      Press the Immediate button. 10.     Press <CTRL>+S to save the changes 11.     Press <CTRL>+S again to save all the changes to the job. 12.     Job will start immediately once saved.  Press <F8> to refresh the list of jobs 13.     Continue to press <F8> every once in a *while* to update the status of the job.  Do not *continue* until the job is completed sucessfully.

SCC4 1.      From the Table view menu, select Display -> Change

2.      When warned that the table is cross-client, press the checkmark button. 3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066) 4.      Set the Protection to Protection level 1 5.      Press <CTRL>+S to save. 6.      Repeat steps 3 through 5 *for* any additional clients

Deleting Source System Profiles RZ10 1.      From the Utilities menu, select Import Profiles then Of Active Servers.  (Note:  All application servers of the target system must be started) 2.      If the Display Profile Check Log screen is displayed, press <F3> to leave *this* screen. 3.      Select the Profile field and press <F4> to bring up a list of profiles. 4.      From the list select one of the profiles associated with the source production system. 5.      From the Profile menu, select Delete, then All versions, then of a profile. 6.      When prompted, press the Yes button to delete all version of the profile 7.      When prompted to delete the file at the operating system level, press the No button. 8.      Repeat steps 3 through 7 *for* all additional profiles associated with the source system

Reconfigure Operation Modes RZ04 1.      From the Operation Mode menu, select Timetable 2.      Select Normal Operation and press the Change button. 3.      Highlight 00:00 in the left hand column and press the Delete Assignment button 4.      If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button. 5.      Once all the assignments are deleted, press <CTRL>+S to save. 6.      If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable. 7.      Press <F3> to go back to the main RZ04 screen. 8.      Right click on one of the listed Operation modes and select Delete 9.      Press the Yes button to confirm the deletion. 10.     Repeat steps 8 through 9 *for* any additional operation modes 11.     Press <F5> to create a *new* operation mode. 12.     Enter a name and *short* description *for* the operation mode 13.     Press <CTRL>+S to save. 14.     Press <F6> to create a *new* Instance 15.     From the Settings menu, select Based on current settings, then New Instances, then Set 16.     Press <F3> to go back to the main RZ04 screen. 17.     Press the Yes button to save 18.     From the Operation Mode menu, select Timetable 19.     Select Normal Operation and press the Change button. 20.     Highlight the 00:00 at the top and press <F2> 21.     Highlight the 00:00 at the bottom and press <F2> 22.     Press the Assign button. 23.     Press <F4> to select the operation mode created above. 24.     Press <CTRL>+S to save.

Delete Update Failures SM13 1.       Set the fields as follows Client:  * User: * From data: 01/01/0001 From time: 00:00:00 2.      Press <Enter> to display the list of outstanding update requests 3.      If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.

4.      Press the Continue button to confirm the deletion.

Delete Batch Input Sessions SM35 1.      From the Edit menu, select Select All 2.      Press <Shift>+<F2> to delete all the batch input sessions. 3.      Press the checkmark button to confirm 4.      Press the Yes button to start the delete.

Reorganize Spool SPAD 1.      From the Administration menu select Clean-up Spool 2.      Check all check boxes and enter 0 *for* minimum age 3.      Press the Execute button 4.      Once complete, press <F3> twice to get back to the main SPAD screen 5.      From the Administration menu select Check Consistency 6.      Press the Delete All button.

SP12 1.      From the TemSe database menu, select Consistency check 2.      When the check is complete, press the Delete All button.

Delete Invalid Background Control Objects SM61 1.      Press <F8> to *switch* in to change mode 2.      Press the Cleanup List button.

Restrict Outgoing Email and Faxes

SCOT 1.      Double click on the green Fax entry 2.      From the Supported Address Types area, press the Set button that is beside Fax 3.      In the Address area, ADJUST AS NECESSARY 4.      Double click on the green SMTP entry 5.      From the Supported Address Types area, press the Set button that is beside Internet 6.      In the Address area, ADJUST AS NECESSARY

Adjust RFC connections. SM59 1.      Expand the TCP/IP connections section 2.      Double click on the first entry listed 3.      Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.

Make changes as necessary. 4.      Press the Test Connection button to test the connection 5.      Press Press <CTRL>+S and then <F3> to save and *return* to the list of RFCs. 6.      Repeat steps 1 through 5 *for* each additional RFC connection

Convert Logical Systems Under no circumstances perform *this* procedure on a Production system BDLS 1.      When warned to read the documentation, press the checkmark button. 2.      In the Old logical system name box, press <F4>. 3.      Select one of the production Logical System names that needs be changed (i.e. WIIPRD400) 4.      In the New logical system name, enter what that logical system name should be called on *this* newly refreshed system (i.e.WIITRN400)   Note: Ignore Error/Warning about duplicate system by

clicking on the check mark. 5.      De-select the Test Run and Existence check on *new* names in tables options 6.      From the Program menu, select Execute in background 7.      Press the checkmark button when asked to select a spool device 8.      Press the Immediate button when asked *for* the schedule 9.      Press <Ctrl>+S to save 10.     Use SM37 to monitor the job 11.     When job is complete, repeat steps 2 through 10 *for* any additional logical system names that need to be changed.

Adjust Logical Systems names SALE 1.      Expand Sending and Receiving Systems, then Logical Systems 2.      Click on the execute icon beside Define Logical System 3.      Press the checkmark button to confirm that the change is cross client 4.      …

Allow Certains Settings to be modifiable (Refer to Note 356483 *for* more Details) SM54 1.      Enter V_T001B in the Table/View box. 2.      Select the Generated Objects option. 3.      Press the Create/Change button. 4.      Enter any access keys *if* requested 5.      Change the Recording routine to no, or user, recording routine. 6.      Press <Ctrl>+S to save 7.      Press <Enter> *if* warned that you are changing a function group that doesn't belong to you. 8.      You are prompted *for* transport.  Create a *new* local transport. 9.      Repeat steps 1 through 8 *for* the following objects.  You can specify the same transport you created above. V_T001B_GL V_T093B_01 V_T093B_02

BSI Configuration (R3 HR Systems only) SM59 1.      Expand TCP/IP Connections 2.      Highlight BSI70-US-TAX and press the Change button 3.      Change the program field to \\<hostname>\sapmnt\<SID>\SYS\EXE\RUN\TF60SERVER.EXE 4.      Double check the target host and gateway point to the correct server 5.      Press <CTRL>+S to save 6.      Press the Test connection button to test.  If the connect is not successful, take the necessary steps to resolve the issue.

SE38 1.      In the Program field, enter RPUBTCU0 2.      Press <F8> to execute 3.      Select option BSI version 7.0 4.      Press <F8> to execute 5.      BSI should *return* tax calculations.  If there are errors, take the necessary steps to resolve.

Reconfigure DB13 schedule DB13 1.      Using the print out created before the refresh, recreate the DB13 calendar.

Client Configuration SCC4 1.      From the Table view menu, select Display -> Change

2.      When warned that the table is cross-client, press the checkmark button. 3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066) 4.      Define clients as follows depending on client role

Development Client role:  Customizing Changes and transports *for* client-specific object:  Automatic recording of changes Client-independent object changes:  Changes to repository and cross-client customizing allowed Protection: Client copier and comparison tool:  Protection level 0 Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

Quality Assurance Client role:  Test Changes and transports *for* client-specific object:  No changes allowed Client-independent object changes:  No Changes to repository and cross-client customizing allowed Protection: Client copier and comparison tool:  Protection level 0 Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

Training Client role:  Education Changes and transports *for* client-specific object:  No changes allowed Client-independent object changes:  No Changes to repository and cross-client customizing allowed Protection: Client copier and comparison tool:  Protection level 0 Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

Sandbox Client role:  Test Changes and transports *for* client-specific object:  Changes without automatic recording Client-independent object changes:  Changes to repository and cross-client customizing allowed Protection: Client copier and comparison tool:  Protection level 0 Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

5.      Press <CTRL>+S to save. 6.      Repeat steps 4 through 6 *for* any additional clients Set System Change Option Skip *this* section of the system is a Development or Sandbox System.

SE06 1.      Press the System Change Option button. 2.      Set the global setting to Not Modifiable 3.      Press <CTRL>+S to save.

Release Background Jobs Currently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled).

Where To Find Deleted Transport Request Logs

Is there any way to find out deleted transport requests logs?

If you have deleted from SAP level. Then you need to check at the OS level in /usr/sap/trans/log directory else you can check for the SLOG and ALOG folder also.     If total request has been deleted then you can also do the transport manually at OS level.

or

If you have simply deleted the the requests from import queue through "Extras-> Delete imported requests" in transaction STMS_IMPORT and have not deleted the logs at OS level, then you can check in "Goto-> Import History" in the same transaction to view the requests.

Just double click on the request you want and you enter the "Display Object List" screen for the particular request.  Here you can click on the secong "Spectacles" icon to display the transport steps of the request in each of your SAP system. Just double click on a step, e.g. 'Import', 'Check Version','Export' etc. to display the log for that particular step.

You can also view the logs from operating system in the directory <TRANSDIR>/log. The logs are named in the format:  <Source SID><Step ID><Request no>.<Target SID>, where step ID is a single alphabet denoting a particular transport action.

What is ECC?  Where to find the installation steps of  ECC 5/6.0 with SQL as database and on windows platform with the steps including Solution Manager installation?

http://service.sap.com/instguides

ECC means Enterprise Central Component.

There are all the relevant installation guides. You NEED SAPNet access because without a registered and licensed SolMan installation number you will not be able to generate the SolMan key for the ECC installation.  

Upgrade to 4.7

Have you gone through an upgrade to 4.7?  What are the difference or changes associated with 4.7.  If you are currently on 4.6C and are inching forward to upgrading to 4.7 then this information might be useful to you.

There is very little difference between 4.6 and 4.7, the only "steps" you should need are steps in SU25 ( skip step 1) Then go through all your role and perform a merge old new to bring in the new authorization objects 

Just to forewarn you of a potential problem which have been encounter at the point of writing.

After updating/ modifying roles in step 2C, when going back into 2C to make sure all roles are now green, 70% have gone back to red! 

The maintenance done is ok, but there seems to be a problem while trying to go back into the roles again to re-generate. 

SAP recognizes them as needing "adjustment", so you cannot pick them up in mass generate in PFCG as they do not come in, even though the authorizations tab is red. 

This problem is currently with SAP and it is confirmed that nothing have been done wrongly. 

Generally, the work is quite manageable in the upgrade, but don't be surprised at how big the upgrade is when compared to upgrading from 46b to 46c.  

If we have full software of 46c and 47E is it possible to upgrade 46c to 47E or there is a seperate 47E upgrade software need to be requested from SAP?

Where I can get the document with upgrade steps on the service market place?

It is of course possible and supported:

http://service.sap.com/inguides

--> SAP Components --> SAP R/3 Enterprise --> (choose your version) at the bottom there is an "Upgrade guide" for Windows and Unix.

For Upgrades it is recommended to read ALL the notes mentioned in the  upgrade guide and to make sure one is using

- the correct version of the "tp" program - the correct version of the "R3trans" program - the correct version of the "R3up" program

All that is explained in the upgrade guide and in the corresponding notes.

If this is your first upgrade you should take a person, that has some experience on doing that for the first time.  

Installation of SAP R/3

Currently we are going to install SAP on a new IBM server from the existing COMPAQ server. Where can I get the steps for that. 

Configuration is :    OS - windows 2003 server

   DB - Oracle 9i    SAP 4.7

http://service.sap.com/instguides

--> SAP Components --> SAP R/3 Enterprise --> SAP R/3 Enterprise Core 4.70 / Ext. Set 2.00 (SR1) --> Inst. Guide - R/3 Enterprise 4.7 x 2.00 SR1 on Win: Oracle

The above url is the SAP Service Marketplace with all the information you need to install, configure and run system. You need to be a valid licensed customer with a user ID and PASSWORD to use that.

Without access you won't be able to successfully run any SAP systems because it has notes, patches etc.

 

Transport of ABAP Query

 

I am involved in this upgrade project to 4.7  The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that. 

I remember a similar problem upgrading to 4.6C from 4.5B ......  Take a look at OOS note 672784. 

You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.  You download the infosets, queries etc into a file and load them into whichever system you wish.

Just wanted to share my experience of transporting queries: I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.  When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR. 

Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.  (System includes these in an automatically created transport request) 

Step 2. Release this transport and request it be transported to 'new' system.  (This results in the entries being populated in transport table AQTDB in 'new' system). 

Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.  (RSAQR3TR gives the message that stuff has been imported OK). 

Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'. 

(Now my queries etc were available in new system). 

Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.

 

SAP Message : TP_CANNOT_CONNECT_SYSTEM

 

Using spam, trying to import SPAM UPDATE, I get the above message together with TP_INTERFACE_FAILURE.  1. tp works fine when I am doing transports (tp import devk90000 qas client=400 u1 or addtobuffer).  2. niping -t SELFTEST works fine

I worked through notes 44946 and 96907, but could not resolve the issue.

The support packages have been uploaded from the DEV box into the QAS queue. The DEV and QAS boxes are in the same centre on the network, by fibre. I am working on QAS.

I get this message in QAS:- "SAP system is waiting for the inclus. in transport domain"

When trying to update the config from DEV client 000, I get this message:-

System DEV is unknown in the Transport Management System

Diagnosis An error occurred in the TMS communication layer.

System: QAS.DOMAIN_DEV(000) Function: TMS_CI_CHECK_ACCESSTOKEN Error: UNKNOWN_SYSTEM (DEV)

System Response The function terminates.

Procedure Log this system on to the Transport Management System.

If this error occurs in the function TMS_CI_CHECK_ACCESSTOKEN, then the TMS configuration was deleted in the R/3 System QAS.DOMAIN_DEV(000).

Configure the TMS in this R/3 System again.

You need to:

1. logon to the transport domain controller with admin user in client 000.  2. Run STMS  3. System overview  4. select QAS  5. Menu line option "SAP system" --> "Approve"  6. Distribute configuration

When you are logged on the transport domain server and run STMS --> System Overview. Is QAS listed? If so, select it and perform the checks under "SAP Systems" in menu line.

If they are not successful you might want to try the following to configure the TMS on QAS from scratch.

First delete QAS from system overview on the domain server.

Then do the following steps...

In your QAS system in client 000. Run tcode SE06 --> Database copy or Database migration --> Perform post-installation actions. Then confirm that you want to delete all old CTS/TMS config and type in QAS as source system for the database copy.

Then run STMS again and type in the correct data for the transport domain controller. Logon to the transport domain controller in client 000. Run STMS. Open system overview. Choose the SID of the QAS system and click on "SAP System" in the menu and choose Approve. This will add the QAS system to your TMS config again. Perform the checks from menu line "SAP Systems" again.

It seems like a lot maybe, but it only takes a couple of minutes to perform.

We are in the process of implementing SAP for our overseas sales offices.   However, the Server will be situated at our country. We want our overseas sales office to connect to our SAP Server through VPN. What should be the optimum internet bandwidth that they should use at their place to connect to our SAP server? Does SAP recommend any standard bandwidth for this process? 

From our experience, there is no general rule that one can follow, as several factors will affect the connectivity

1. No of hops between your ISP and that of the remote site, the more hops the poorer the performance, even having large bandwidth may not improve the performance by much if there are numerous hops in between.

2. Is the Internet connectivity solely used for your VPN or other purposes such as web surfing, email etc, other traffic can consume large amount of traffic thus causing your SAP performance to be poorer

3. ISP's bandwidth to the public internet - If the ISP is heavily over subscribed, and has limited bandwidth connecting to the international network, you will find that you will not be able to get the international throughput you subscribed for as such, performance may be poor even you have paid for a line with a large bandwidth

4. No of users at your remote office using the VPN - In general the lines we use are 64kbps for sites with approx 3-5 users, we are also using ADSL lines with 512kbps connectivity and they enjoy close to local Lan performance for SAP.

 

See from which network IP address and host name a user has logged on

 

To see the network IP address from which a user has logged on, 

perform the following steps: 

Call transaction OS01, 

click "Presentation Server" button, "Change View" button.   

If you are using Citrix, you will not be able to view the user individual IP address as it will be the same Citrix IP address.  

To check the speed and quality of the user's network connection, 

select the desired presentation server and click "10 X Ping" button. 

11/22/2007

No System name and transaction code in SM04

If you have more than one application server, use AL08 instead of SM04.

or

It is because they are at the logon screen which has established a connection.

You will notice that the transaction code shown when there is no user name is SESSION_MANAGER.

This shows you which workstations out there have the login screen up but have not yet entered a user name and password.

The transaction column shows the Last executed transaction code. 

Sometimes your users will have multiple sessions open. If they do, to the system, it is the same as multiple logins as it relates to the resources used etc. 

So the user name will show up more than once in AL08.

Under the application server they are logged into, each instance of that user name on that application server represents a session open. 

For instance if you run AL08, you will have your name show up at least twice on the application server you are logged into. 

One will show AL08 and the other will not have a transaction next to it. 

Then you will notice your user name showing up on all other application servers with no transaction. This is because you are using AL08. 

Monitor and Administrate 4 SAP Systems

If there are 4 systems installed SAP, how should I connect all of them in one network so that I can administrate the 4 systems with one among them as main server.

A D V E R T I S E M E N T

This should help you:

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, first customize the alert monitor by choosing Tools > CCMS > Configuration > Alert monitor or calling transaction RZ21.

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. 

Next, to change your monitor definitions (you can only change your own monitors),   choose Tools > CCMS > Control/Monitoring > Alert monitor or call transaction RZ20.

Activate the maintenance function by choosing Extras > Activate maintenance function. Then, double click on the monitor and choose Monitoring change.  Parameter R3system defines which systems can be monitored by an alert monitor. Change parameter R3system from <CURRENT> (only the current R/3 System can be monitored) to <ALL> (all R/3 Systems defined in RZ21 can be monitored).  Save the changes.

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

 

Brief Description About SAP Basis Implementation

 

Please give a brief description about implementation process carried out.

There is no standard Implementation process, it purely depends on which methodology person have adopted for implementation. I will give you broad view of implementation project... I am just starting from sizing of the servers ...

1.  Identify the no 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    

Solution Manager

What Is The Use of Solution Manager

What is the use of solution manager, and what we can do with solution manager?

A D V E R T I S E M E N T

Now a days solution manager is mandatory.   1. it is used for generating keys and downloading support packages  2. it is used to document  user  requirments and preparing senarios what needs to to be adopted using solution manager, where the blue print is the part of solution manager  3. it is used for reporting, solution desk,to manage the change requests and use to monitor entire landcape Central message processing in the SAP Solution Manager:   - Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA) - Assign processor - Send messages to the creator and other processors - Forward message to other processors or support units - Create documents and URLs - Attach documents - Status assignment and monitoring - Create a worklist with selection conditions                                 

I have a requirement to install SAP Solution Manager Solution Support Enablement Package (SEP) in our solution manager 4.0. This SEP contains, RBE, TDMS, ...etc.,   I checked for the software download at market place but couldn't find the software package, can anyone help me to download this SEP for windows/oracle.   Look at following:

http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> Installations and Upgrades -> SAP Technology Components -> SAP Support Enablement Package - >SAP Support Enabl. Package 1.0

How to configure the service desk on Solution Manger 4.0.  I want to cofigure Solution Manger only for service desk I have install Solution Manger 4.0.   What is the Step please explain.

Check:   http://service.sap.com/rkt-solman   There are tutors, PDFs and powerpoints to guide you through the configuration process.         

If you have 3 or 4 client systems, must you install SAP solution manager for each one of these systems and manage them independently -or- 2. Can you install One Solution manager, that will manage all 3 these systems in one solution manager -or- 3. Do you install 3 Solution managers for each of the systems, then another one linked to the 3 individual solution managers, which then in turn manages the 3 systems in one.

In any System landscape only one solution manager is installated in one system and it will communicate with the other system using the RFC and collect the report from each and every system through (SDCCN).  

Applying SP4 to Windows 2000 Server

You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use. 

A D V E R T I S E M E N T

Once you are at the patches website, you will need to click in the navigation tree:  R/3 -> R/3 + ?Release number? -> Binary patches ->  SAP Kernel + ?Release number? + 32-Bit -> NT/I386. 

Download everything from the database section and everything from the database independent section. 

One of the files you downloaded should start with SAPCAR and end with a *.exe.  Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.  Go to \usr\sap\<SID>\SYS\exe\run and backup the entire directory to some other directory -  I usually create a \usr\sap\<SID>\SYS\exe\backup_run directory. Make sure SAP is down, the database is down, the TNS listener is down, and the SAPOSCOL is down before you do this. 

Uncompress all the files you downloaded by opening a DOS box and typing: 

SAPCAR -xvf <file name>.CAR 

All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\<SID>\SYS\exe\run AFTER that directory has been completely backed up. 

Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup. 

If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.

 

SPAU and SPDD

 

When you apply a package, a large number  of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects. 

SPDD is used to identify dictionary objects 

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes. 

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code. 

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note.  You must check the OSSs note and see if SAP have fixed that note in a hot package. 

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code.  This means that there is no repair flag set against this object again and it is now SAP standard code. 

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

 

How to know the kernel version of a SAP R3 system?

 

-----Original Message----- Subject: How to know the kernel version of a SAP R3 system

Hi all

Could someone tell me how can I find the Kernel version of a SAP R3 system ? example, for those releases SAP R3 4.0B, 4.5B, 4.6B, 4.6D and so on ....

Thanks for your help

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

From any screen choose System-->Status then click the 'other kernel info' icon (between Navigate and Cancel). The same information can be found at OS level in the dispatcher trace file: /usr/sap/<SID>/<instance name>/work/dev_disp. Regards,

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

Hi,

Goto transaction sm51, and click (not double click) on the the Database  server and then click on release notes. there you will see the SAP R/3  kernel and patch level etc.

Regards

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

You can use the System ==> Status and then Other Kernel Info button to get the details about the Kernel Release, Patch levels etc.

Regards,

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

I think an even more convenient way to do this is to use SM51.  Highlight the server you are interested in and click on "Release Information". This provides you a location to view all servers with out logging on to each one.  The answer below will give you information about the server you are connected to only.

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

Also try "disp+work -v"   on server.

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

go to transaction SM51 -->release information

-----End of Message-----

Administration

AL11 Display SAP Directories BD54 Maintain Logical Systems OSS1 Logon to Online Service System SALE IMG Application Link Enabling SARA Archive Management SCC3 Copy Analysis Log SCC4 Client Administration SCC5 Client Delete SCC7 Client Import Post-Processing SCC8 Client Export SCC9 Remote client copy SCCL Local Client Copy SCU0 Customizing Cross-System Viewer SICK Installation Check SM01 Lock Transactions SM02 System Messages SM04 User Overview SM12 Display and Delete Locks SM13 Display Update Records

SM14 Update Program Administration SM21 System Log SM35 Batch Input Monitoring SM50 Work Process Overview SM51 List of SAP Servers SM56 Number Range Buffer SM58 Asynchronous RFC Error Log SM59 RFC Destinations (Display/Maintain) SM66 System Wide Work Process Overview SAINT SAP Add-on Installation Tool SPAM SAP Patch Manager (SPAM) SPAU Display modified DE objects SPDD Display modified DDIC objects ST11 Display Developer Traces ST22 ABAP/4 Runtime Error Analysis SU56 Analyze User Buffer

Alert Monitoring

AL01 SAP Alert Monitor AL02 Database alert monitor AL04 Monitor call distribution AL05 Monitor current workload AL16 Local Alert Monitor for Operat.Syst. AL18 Local File System Monitor RZ20 CCMS Monitoring

Configuration

FILE Cross-Client File Names/Paths RZ04 Maintain Operation Modes and Instances RZ10 Maintenance of Profile Parameters RZ11 Profile parameter maintenance SE93 Maintain Transaction Codes SM63 Display/Maintain Operating Mode Sets SPRO Customizing: Initial Screen SWU3 Consistency check: Customizing

Database Administration

DB01 Analyze exclusive lockwaits DB02 Analyze tables and indexes DB12 DB Backup Monitor DB13 DBA Planning Calendar DB15 Data Archiving: Database Tables

Jobs

SM36 Define Background Job SM37 Background Job Overview SM39 Job Analysis SM49 Execute External OS commands SM62 Maintain Events SM64 Release of an Event SM65 Background Processing Analysis Tool SM69 Maintain External OS Commands

Monitoring

AL08 Current Active Users OS01 LAN check with ping RZ01 Job Scheduling Monitor RZ03 Presentation, Control SAP Instances

ST01 System Trace ST02 Setups/Tune Buffers ST04 Select DB activities ST05 Performance trace ST06 Operating System Monitor ST10 Table call statistics ST03 Performance, SAP Statistics, Workload ST07 Application monitor STAT Local transaction statistics STUN Performance Monitoring (not available in R/3 4.6x)

Spool

SP01 Output Controller SP11 TemSe directory SP12 TemSe Administration SPAD Spool Administration

Transports

SCC1 Client Copy - Special Selections SE01 Transport Organizer SE06 Set Up Workbench Organizer SE07 CTS Status Display SE09 Workbench Organizer SE10 Customizing Organizer SE11 ABAP/4 Dictionary Maintenance SE16 Data Browser SE80 Repository Browser SM30 Call View Maintenance SM31 Table Maintenance STMS Transport Management System

User Administration

PFCG Profile Generator (Activity Group Maintenance) PFUD User Master Data Reconciliation SU01 User Maintenance SU01D User Display SU02 Maintain Authorization Profiles SU03 Maintain Authorizations SU05 Maintain Internet users SU10 User Mass Maintenance SMLG Maintain Logon Group SUPC Profiles for activity groups SUIM Infosystem Authorizations

Other Transactions

AL22 Dependent objects display BAOV Add-On Version Information SA38 ABAP reporting SE38 ABAP Editor HIER Internal Application Component Hierarchy Maintenance ICON Display Icons WEDI IDoc and EDI Basis WE02 IDoc display WE07 IDoc statistics WE20 Partner profiles WE21 Port definition WE46 IDoc administration

WE47 Status Maintenance $TAB Refreshes the table buffers $SYNC Refreshes all buffers, except the program buffer

The recent releases from SAP are:

---> SAP ECC 6.0 SR1 / SR2 /  SR3 IDES with EhP 3

---> SAP R/3 4.7 EE

---> SAP CRM 7.0 / 2007 / 5.0 with Live Cache

---> SAP SCM 7.0 / 2007 / 5.0

---> SAP SRM 7.0 / 2007 / 5.0

---> SAP BI 7.0 with SEM 6.0

---> SAP BIW 3.5 with SEM 3.1

---> SAP PI 7.1 (XI 7.1) / PI 7.0 (XI 7.0)

---> SAP EP 7.0

---> SAP MDM 7.1 / 5.5

---> SAP Solution Manager 7.0 / 4.0

---> SAP Netweaver 2004s / Netweaver7.0

---> SAP IS Utilities 6.0

---> SAP IS Retail 6.0

---> SAP IS Oil 6.0

---> SAP IS Discrete Industries & Mill Products 5.0

---> SAP IS Discrete Industries & Mill Products 4.7

---> SAP IS Campus Management 6.0

---> SAP IS CWM (Catch Weight Management) 6.03

---> SAP IS DFS (Defense Forces & Public Security) 6.03

---> SAP WEB AS (Web Application Server) 6.20

---> SAP Net Weaver Composition Environment (CE) 7.1

---> SAP Enterprise Services Repository for SAP Net Weaver CE 7.1

---> SAP Supply Network Collaboration 2007 (SNC)

---> SAP TDM (Test Data Migration Server) 3.0

---> SAP Business Objects

---> SAP Business One

---> SAP GRC Tools 5.3

---> SAP BPC 7.0 NW

---> SAP AFS 6.0

---> Oracle Applications 12i / 11i

---> ECC 6  <->  BI 7.0 with Integration

---> ECC 6  <->  PI 7.0 with Integration

---> ECC 6  <->  EP 7.0 with Integration

---> ECC 6  <->  SCM 5.0 with Integration

---> ECC 6  <->  CRM 6.0 with Integration

---> ECC 6  <->  SOLMAN 7.0 with Integration

---> ECC 6 with ESS  <->  MSS Configuration

---> SAP BPC 7.0 Installation and Configuration