Proper way to delete a SAP client

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 -u 1

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?

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 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//sapbackup)
a. Change all the source to target .
b. Only don't change the backup volume name it must be target system .
c. Copy the above aft file name line from the source back.log to target.log file.

5. Shutdown the target server instance.

6. From this onwards all the command on the target system only.
a. Login as 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 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.

Problems with Multi-clients in one SAP Production instance

Problems with Multi-clients in one SAP Production instance

You are working on group of companies. They don't want to share any data between companies, simply no integration required, therefore mgt wants to have one client for one company that end up having multi-clients in prod instance. However, one of the SAP local guy told you not to continue with this lanscape.

Some of the potential problem of using multi-clients in one prod instance are:

1. problems affecting one client immediately affect all other clients.
an eg.: 1 client runs a job that fills up a tablespace or file-system.

2. a system problem (system crash) affects all clients immediately. e.g. an Oracle archive stuck will affect all clients.

3. programs/tables are client independant. Invidual customers cannot make changes to common programs/client without affecting the others.

4. Poorly written ABAP's will cause bad response throughout the SAP system, affecting all clients. I shudder to think of a situation where the programmer for 1 customer stuffs up and the other customers demand blood!

5. Taking all of this into account, your change management will turn into a NIGHTMARE! especially considering that each customer probably does no care about the other customers, so EVERY change of theirs is the most important one.

The above are some of the problems if you have multi-client in one SAP instance and there are many more arguments.

Problems in Heterogeneous Setup

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.

Post Installation Task after successful R/3 46c

Post Installation Task after successful R/3 46c

Generally you need to :-

1. import profiles (default, instance, start) into SAP R3
1.1 add/modify instance parameters such as
rdisp/max_wp_run, abap/timeout,
zcsa/system_languages, and so on...

2. update the R3trans and tp tools with the last ones available on sapnet

3. configure TMS (systems,layer and routes).
You can do it with virtual systems if you have only one SAP system

4. update SPAM/SAINT

5. check via Tcde db02 (with refresh option) the available space for TS other
than SYSTEM TS.( for the others %used must be less than 90)
5.1 check to see critical objects (table/index)
5.2 extend (via sapdba tools -> option TS administration) all TS which
shown critical objectsfor example:
PSAPPOOLD + 200M
PSAPPOOLI + 100M ...
You can get necessary via Note 195446 (for language import) and Note 118823 (for client copy)
5.3 refresh again in db02 and check the %used space

6. import language other than the default (DE & EN) if necessary

7. Client copy

8. configure printer (SPAD)

9. create user

10. change system user password such as SAP* , DDIC, and so on ...

Error you might encounter at the end of client copy :-

"there is a window "change and transport system not configured" Status is cancelled.

To rectify the errors :-

You need to configure CTS via tcde STMS for your SAP system.

If it's your only sap system, then:
- configure it as domain controller: run Tcde STMS and accept the default proposed domain
controller which is your system
- define one or two virtual system (Menu overview-->system then Menu
SAP system-->create-->virtual system)
- Menu Environment --> transport routes then press F5 and Menu Edit
Transport layer to create a "Z" layer for example "ZDEV"
Create a transport route between your real sap system and the virtual system
by using the two layers: "Z" layer and "SAP" standard layer
- save and distribute the TMS configuration
That is the main action you have to do to setup CTS.

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

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

Copy a Client into a Stand Alone System

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 , 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<>; this file contains client-specific data

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

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

KO; this file is for cross-client data

KT; this file is for client-specific data

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

Copy users from DEV to PRD

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.

How To Lock SAP Client

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 " and unlock it with "tp unlocksys ". 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 Maintenance transport requests work flow

SAP Maintenance transport requests work flow

An example of a basic principle and flow is:-

1. A request for a change is submitted to support team

2. Change is done in DEV (if approved) and tested by support team (limited testing only due to lack of productive data)

3. Change is transported to TST

4. User testing takes place

5. User approves or rejects (giving reasons)

6. System manager approves the change to go into PRD

7. Change is transported to PRD

All transports are done by the support team.

If a change is urgent it is transported straight away, if not they are batched up and done once a week.

The Workflow can be controlled by a software like a Lotus Notes database so you can have a record of approval at every step.

Note :-

The system manager is the manager of the support team. The system "belongs" to him i.e. it is his responsibility and he has the final say on what goes into the PRD system. 99.999% of the time he will approves the change, this is mainly a way of keeping him informed of what changes are happening in the system.

Many companies uses the core modules MM, PP, FI, CO. The problem with transporting single transports is that if it is a program, the complete program buffer is reloaded therefore giving a performance hit. Therefore you tend to leave them and just have one performance hit per week (although most weeks there are no program changes). When you are in production the number of transports will settle down to a reasonable figure. Maybe about 10 transports a week, and most of those are material groups (which, although they are user data, they are classed as customising). This rises if you are doing any modifications or changing business processes etc, but 10 is about quite normal for most.

What is a Logical system?

What is a Logical system?

-----Original Message-----
Subject: Logical system

Hello !

Does anybody know what "logical system" is ??? I have read help in =
transaction SCC4 already, but I'm confused more than before ... :-))) =
What it is good for ? What is the reason for defining it ?

Give me an explanation, please ...
Thanks !

-----Reply Message-----
Subject: RE: Logical system

Hi,

'logical system' is used to identify an individual client in a system, for ALE
communication between SAP systems. That's why you see a field for 'logical
system' in the client master data in SCC4 (table T000). You use logical systems
in ALE config - this should be documented further in the IMG guide, or SALE and
BALE transactions.

cheers,

-----Reply Message-----
Subject: RE: Logical system

Just a note of warning regarding choosing the Logical System name.

I know of one site where it was chosen such that it depended on the actual
system name and, therefore, had to be changed after copying production back to
acceptance. The process ran for two to three days! I have not examined how the
logical system name is used but it would appear that selection should be made
carefully to avoid the need for this if the architecture can support it.

Perhaps someone with more experience of this object could comment on its usage
and name selection.

-----Reply Message-----
Subject: RE: Logical system

yes - you should use a naming convention for the logical system names which
includes distinct IDs depending on:
System ID (SID), and client number, and maybe also system number if you have
more than one instance per host machine. Hostname would be useful too, but I
think there's only 10 characters in v3.1x (maybe more with long name
functionality in 4.x ??).

eg., in DEV box , sys no 00, client 100, choose something like 'DEV00_100'.

cheers,

-----Reply Message-----
Subject: RE: Logical system

You state that a logical system appears to be nothing more than another label
for a client. I think (certainly cannot say I know!) that it is a little more
than that: I think it is an externally visible label for a client within a
system.

-----Reply Message-----
Subject: RE: Logical system

Thanks,

I had interpreted the term "logical" as meaning it had no relationship to a
specific instance. That's how I would use the term anyway. I take it from your
remarks and others on this thread that it is, in fact, a very instance and
client specific label - really very physical and not at all virtual/logical.

-----Reply Message-----
Subject: RE: Logical system

I know from experience that the logical system must be defined or you get
error messages all over the place during order processing stating the
logical system has not been defined.
The logical system is defined in the IMG. Don't know the transaction
identifier, but in 4.* it is found in the IMG > Cross Application Components
> Distribution ALE > Basic settings > Logical systems > Define logical
systems. Here the entry is just an identifier and a text entry.
As you stated, it is assigned to the Client in Tx SCC4. (The next step in
the IMG)
I went to the IMG for help. Here is the extract at "Logical systems" level:
"Logical Systems.
The distribution of systems ( ALE ) makes it necessary to be able to
identify every system individually within a network. The "logical system" is
used to do this.
A logical system is an application system within which the applications are
coordinated to work in one database. In the SAP sense of the word, a logical
system corresponds to a client.
In the following steps, you must define every client as a logical system by
first of all defining logical systems and then assigning the clients in
question to the corresponding logical systems.
Note:
Assignments must be unique (that is, a client may only be assigned to one
logical system.
Several clients must never be assigned to the same logical system."

Reading this it does seem that it is nothing more than another identifier
for a "Client".

Hope it helps,

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

SAP 4.7 Enterprise Install Failure "FRF-00007

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.

SAP Installation Procedure on WIN 2k Adv Server

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 cable
Win 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 ENTER
6.      click ENTER again
7.      Click on C ( to continue)
8.      click on F8 ( to agree)
9.      partitions C: 4197Mb, D 12000Mb, E 6000Mb
10.     select C drive
11.     click ENTER to install
12.     click ENTER again to continue
automatically restarts, set up continues.
13.     click on NEXT
14.     click on NEXT
15.     click on NEXT
16.     key RBDC9-VTRC8-D7972-J97JY-PRVMG
17.     click on NEXT
18.     TYPE no of concurrent connections  9
19.     click on NEXT
20.     TYPE COMPUTER NAME 46IDES
21.     click on NEXT
22.     remove IIS (deselect)
23.     click on NEXT
24.     enter date & time
25.     click on NEXT
26.     finish

WINDOWS CONFIGURATION
Creating partitions for new disk.
STARTà PROGRAMMESà ADMIN TOOLSà COMP MANAGEMENTà DISK MANAGEMENT
1.      right click on unallocated space.
2.      click on CREATE PARTITIONS,
3.      click on NEXT
4.      click on NEXT
5.      type 11320 (partition size)
6.      click on NEXT
7.      click on NEXT
8.      type file system NTFS
9.      click on quick format
10.     click on NEXT
11.     click on FINISH
12.     again right click on unallocated space
13.     repeat the exercise from  point 5 but for complete size
note
C drive contains operating system
E/D drive contain 46C software
S drive contains SAP software..

PERFORMANCE
MY COMPUTERà propertiesà advanced à performance optionsàchange,
1.      Select S drive.
2.      type initial =1600& max =1652
3.      click on SET  
4.      click on OK
5.      click on OK
6.      click on OK

NETWORK SETTINGS
STARTàSETTINGSà CONTROL PANELà ADD/REMOVE HARD WARE,
1.      click on NEXT
2.      click on NEXT
3.      select ad a new device
4.      click on NEXT
5.      select (now I want to select from Hardware list)
6.      click on NEXT
7.      select network adaptors,
8.      click on NEXT
9.      select MICROSOFT
10.     click on NEXT
11.     click on NEXT
12.     click on FINISH
13.     close all windows
14.     right click on MY NETWORK PLACES,
15.     go to properties,
16.     right click on local area connections
17.     should be able to see Microsoft loopback adaptor on the screen.
18.     select properties
19.     select TCP/IP
20.     click on properties
21.     select ( use the following IP addresses)
22.     type IP addresses 198.1.1.1
23.     subnet mass 255.255.255.0
24.     click on OK
25.     select show icon on Task bar
26.     click on OK
27.     close all windows.
HOST FILE CONFIGURATION
1.      go to WINDOWS EXPLORER
2.      select C drive, WIN NT, system 32 , DRIVERS, etc
3.      double click on HOSTS
4.      open with note pad
5.      go to end of the page
6.      type IP address 198.1.1.1
7.      press TAB once
8.      type 46cides
9.      press TAB twice
10.     click on SAVE
11.     click on EXIT
12.     RESTART sytem
Software contains three folders
1.      46cides ( a. KERNEL, b. ORACLE 817, c.ORACLE  PATCHES
2.      DB EXPORT
3.      SAP GUI

ORACLE INSTALLATION
1.      46CIDESàoracle 817à NTài386àsetup run the set up by double clicking
2.      click on NEXT
3.      source path …………
destination path : S:\oracle\ora81
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      type GLOBAL DATA BASE NAME : ORACLE
8.      click on NEXT
9.      click on INSTALL
10.     click on OK
11.     click on EXIT
12.     click on YES
13.     close all windows
14.     startà programsàadmin toolsà services
15.     select ORACLE SERVICES
16.     select all ORACLE releated services ONE BY ONE.

ORACLE PATCHES
46CIDESà ORACLE PATCHESàPATCHà DISK1à INSTALLà WIN 32
1.      set up (double click)
2.      click on NEXT
3.      click on NEXT
4.      click on INSTALL
5.      click on INSTALL
6.      click on EXIT

KERNEL INSTALLATION
46CIDESàKERNELàNTà I386à MMC
1.      double click on IMMC
2.      click on NEXT
3.      I agree
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      click on FINISH
46CIDESàKERNELàNTà I386à NT PATCH
1.      double click on R3DLLINS
2.      click on Ok
3.      close all windows
4.      RESTART
46CIDESàKERNELàNTà COMMONà
1.      double click on R3 SET UP
2.      type SAP SYSTEM NAME IND
3.      click on NEXT
4.      click on NEXT
5.      click on NEXT    at 85%
6.      click on NEXT    automatically logs off
7.      login and control+alt+del

CENTROL INSTANCE
Startàprogramsàsap system for INDà install CENTRAL INSTANCE
1.      click on NEXT
2.      type instance no OO,
3.      click on NEXT
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      click on NEXT
8.      click on NEXT
9.      click on NEXT
10.     click on NEXT
11.     click on NEXT
12.     type LOCATION OF KERNEL CD   E:\46cides\kernel
13.     click on NEXT
14.     password AAA    
    AAA
15.     click on NEXT
16.     password AAA
    AAA
17.     click on NEXT
18.     select NO LDAP SUPPORTS
19.     click on NEXT
20.     click on NEXT
21.     click on NEXT
22.     click on NEXT
23.     click on  EXIT when finished

DATA BASE INSTANCE
Startà programsà SAP set up system for INDà install database instance
1.      click on NEXT
2.      click on NEXT
3.      click on NEXT
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      click on NEXT
8.      click on NEXT
9.      click on NEXT
10.     click on NEXT
11.     click on NEXT
12.     click on NEXT
13.     click on NEXT
14.     click on NEXT
15.     click on NEXT
16.     type location of CDS  for KERNEL  : E:\ 46cides\KERNEL
for EXPORT  : E:\DBEXPORT
17.     click on NEXT
18.     password AAA
    AAA
19.     click on NEXT
20.     click on NEXT
21.     click on NEXT
22.     click on NEXT
23.     click on EXIT  at 32%
24.     log off
25.     log in
26.     user à ind adm
27.     passwordà AAA
28.     OK
WINDOWS EXPLORERà C:\USERS\IND ADM\INSTALL\R3 SET UP FILE
1.      double clik on R# set up file
2.      select database R3S
3.      open
4.      type pass word AAA
        AAA
5.      click on NEXT
6.      at 91% password AAA
AAA
7.      at  93% start MMC
8.      click on NEXT
9.      at 100% EXIT
10.     click on STOP MMC
11.     restart system

POST INSTALLATION
E:\apgui320\gui\windows\win 32\setup(double click)
1.      click on NEXT
2.      click on INSTALL      
3.      click on FINISH
4.      click on SAP logon
5.      select NEW
6.      type DESCRIPTION : 46CIDES
7.      type application server : 46CIDES
8.      type system no : 00
9.      start MMC


10.     close MMC
11.     log in SAP
12.     client 000, user sap* password 06071992
13.     txn code SM28
14.     ENTER ( TO CHECK ERROR)
15.     RESULT : NO ERROR REPORTED ( in installation)

STMS
Description à Student
Click on SAVE
Go to overviewà transport routes
Select display change mode (second icon)
Configurationàstandard configurationà single system ( main menu)
Click on Enter
Configurationàdistributeàactivate
Click on Enter
F3 (to go back)

RZ 10
Utilitiesà import profiles of active servers
Click on Enter
Click on F3 (to go back)
Profile  click on F4
Select INDà DVEMGS00à46CIDES
Select EXTEND MAINTà change
Select create paramaeters9 icon)
Type paramter name : rdisp/max-wprun-time
Type parameter value ; 3000
Copy icon
Go back
Click Yes

CREATE PARAMETER
Paramater name : abap\ field exit
Value ; YES
Select COPY icon, go back à YES
Create parameter
: login/system-client
: 800
select copy iconàgo back à yes
create parameter
:eu/iwb/installed/languages
:EN
select COPY icon – go back à YES
again go back
click on YES
click on SAVE
click on YES
click on ENTER
click on ENTER

(USER CREATION)
TXN : SU01
user : sapuser
select : create icon

address                 logon data
title                   go on clicking ENTER no of times
first name              initial password : abc
last name               repeat pass word : abc

DEFAULTS
Logon language          : En
Output device   ; LP01
Select : Out put immediately & decimal

PROFILES
Type 1. SAP – ALL
TYPE 2. SAP – NEW
SAVE
Log off from SAP
Login to SAP

type     user : sapuser     password : abc
new password : abap
repeat password : abap

txn : SALE
IMGàerror handlingàbasic work flow settings
Select AUTOMATIC CUSTOMIZING icon
Go back
Txn 00w4
Select DISPLAY CHANGE MODE icon
Create icon

CREATE
Prefix no       978
System ID       IND
Client          000
Click on Save
Local object
Cancel    X


CREATE
Prefix no       972
System ID       IND
Client          800
Click on Save
Local object
Cancel    X

TXN SE 38

Program name : Z FIRST
CREATE
ACCESS KEY : 36687663221261278694
TITLE : DEMO
TYPE : EXECUTOR
Click on SAVE

LOCAL OBJECT
Log off from SAP
Log into SAP
Client          : 800
User            : sap
Pass word       : 06071992

RUN txn SU01  for 000 client


Log off from SAP
Log into SAP
Client                  : 800
User                    : sap
Pass word               : abc
Click on ENTER
Enter new password : abap
Logoff
Stop MMC

Transport a SAP Object From Dev to Pro

What is the steps to transport an object using se01 or se09?

After creating a transport request. To Transport a request go to

SE09 (Workbench Organizer) or SE10 (Customizing Organizer)

In the intial screen Check the boxes

1) Modifable (Which are yet to be released)
2) Released (Already Released)

Then press enter

Now in that screen check for your created request by pressing Ctrl+F .
In that request check if it is having any child nodes or not. If it is having any child node then first release it and then only you will be able to release parent node

Releasing a Transport Request:

Put your cursor on Child node and then press F9 or you can see a truck symbol which means for transport in SAP click on that. In the same way after releasing child node release the Parent node also then ask your basis person to transport that request from Development to Quality or Production.

Transporting from Development to other servers:

Go to the tcode STMS to where you can transport the request from one server to another server. Usually, only the basis person can do this.

Steps for Creating Package

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