Thank you very much

Thank you very much!

Steps for Creating Package

How to create transport package in R/3?

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

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.



SE09 - Transport Request Release

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.

SAP Installation Procedure on WIN 2k Adv Server

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

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

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.

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.

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

KOr>; this file is for cross-client data

KTr>; this file is for client-specific data

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

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?

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