Transports and Upgrade

Meaning behind those unconditional tp command mode

anyone tell me what's the meaning behind all those unconditional mode U1 or U126
or U148 or anything?
tp import transportrequest <sid> clientxxx U1
tp import transportrequest <sid> clientxxx U126
tp import transportrequest <sid> clientxxx U148
The u stands for unconditional force ( how hard you want to force the request in
to the system - do you want to overwrite without warnings, or softly try to load
the objects).
0: Called a overtaker; change request can be imported from buffer without deleti
ng it and then uncoditional mode 1 is used to allow another import in the correc
t location.
1: If U1 is used with the export then it ignores the correct status of the comma
nd file; and if it is used with import then it lets the user import the same cha
nge request again.
2: When used with tp export, it dictates the program to not to expand the select
ion with TRDIR brackets. If used in tp import phase, it overwrites the originals
.
3: When used with tp import, it overwrites the system-dependant objects.
5: During the import to the consolidation system it permits the source systems o
ther than the integration system.
6: When used in import phase, it helps to overwrite objects in unconfirmed repai
rs.
8: During import phase it ignores the limitations caused by the table classifica
tion.
9: During import it ignores that the system is locked for this kind of transport
.
u128 is combination of 128 OF THE above points.

Transport guide Tips for Different SAP Objects

You may be wondering if you can transport certain SAP objects, and if possible,
how?
Here are tips for different objects:
1

LSMW There are 2 ways for transporting LSMW data from a system to another.

1.1 Export/import This method gives you the opportunity to select the subproject
s or objects you want to transfer. Hence you don't transfer the object a colleag

ue might have created and that should stay in development system. LSMW -> Extras
-> Export project
1.2 Transport request With this method, you can transport a LSMW project in full
(you can not select the objects you want). With this method, the project will b
e transported as any other SAP object in a transport order.
LSMW -> Extras -> Create change request
2 Program variants
If you have several program variants in a development system that you want to tr
ansport, use the following method to transport them:
Execute program RSTRANSP (via se38) and inform the program and/or variant names
(you can transport variant of several programs in one shot).
3 Layout In some transactions, one can save layout of the screen (sort, filter
, ... criteria).
These layouts can be transported: In the required transaction, when your layouts
have been saved, go to Settings -> Layout -> Layout Management. Select the desi
red layouts and go to Layout -> Transport There you can add your layouts in exist
ing TO or create a new one.
DB data
In some unusual cases, you might have to transport data of a SAP table.
Go to transaction SE16, select your entries and go to Table entry -> Transport e
ntries. It's only possible for some tables...
If you cannot do it that way, you have to create a Workbench transport order wit
h transaction SE10. When created, click on it, go in menu Request/task -> Object
list -> Display object list.
Go in modification mode and add a new line with:
PgmID = R3TR
Obj = TABU
Object name = Name of your table
Double-click on the created line and, depending on your need, put '*' in the key
field or double-click on it and select the key you need to transport.
4 Queries
Queries, datasets and user groups can be exported/imported between the systems t
hanks to the program RSAQR3TR.
5 Standard texts
Standard texts used in SAPScript (created with transaction SO10) can be included
in transport orders. You have to create a Workbench transport order with transa
ction SE10. When created, click on it, go in menu Request/task -> Object list ->
Display object list. Go in modification mode and add a new line with:
PgmID = R3TR
Obj = TEXT
Object name = TEXT,,ST,
Example :
R3TR / TEXT / TEXT,YMM_MEDRUCK_MAIN_16_EC,ST,F
You can also copy a Sapscript object (like standard text) with the program RSTXC
PFS.
How to transfer a executable report from dev server to prd server? And that rep
ort contains one user defined view. I want to transfer *the report and the view*

from dev to prd.

At the time of creating the report itself it will ask you to select the PACKAGE.
Here you should select the package instead of $TMP package, which for transporti
ng the objects and create a new request and save it. If you want to give a TCode
for the program that you have created just give SE93 in the GUI Window and give
the TCode name there and enter the Create button. there you should give the nam
e of the object or program that you have created and save it. After completing t
his go to SE09 TCode and select the MODIFIABLE Check box and press DISPLAY Butto
n.
In the next screen you have to select the Request that you have created and clic
k the check syntax icon. If no errors are there then you can press the Release D
irecty icon to transport the request to the Quality system. From there it has to
be transported to the Production System. The latter part BASIS will take care.

Transport Request within same Server Different Clients

I have 3 clients under one SID (dev 130,140,150).

And we have more than 400+ transport requests in client 130. How can we transpo
rt these requests to other clients of 140 & 150. If I want to use tcode SCC1, t
hat can be done only one tran. request at one time.
Do I need to write a script within unix?
SAP 4.6C
Oracle 9.2
AIX 5.2
Try STMS.
Click on the "import overview"
Double click on your target system
Click "refresh"
Click on "import all request" or ctrl+F9
Specify the target client
Execute the transport
Done...
But this will import all request.....thousands of them...
You can use Extended Transport Control.
Extended Transport Control is another way to set up the Transport Route so that
the route is system and CLIENT specific.
In other words, when you release a change request in DEV Client 0XX it will not
only automatically be added to the Import Queue for QAS but also 0X1, 0X2, of DE
V.
To set this up requires the steps below:
1) Open the file TP_DOMAIN_DEV.PFL (located on your transport domain controlle
r such as the DEV box. The file will be in usrsaptrans/bin)

Edit with notepad for each parameter on each system:

DEV/CTC = 0
Change to =1
2)

Next you need to create Target Group before creating the transport route.

Create a Target Group:

Access the initial screen of the graphical or the hierarchical editor in change
mode. STMS > Overview > Transport Routes (the default editor will appear, either
Hierarchical or Graphical, to change the default editor : STMS > Extras > Setti
ngs > Transport Routes. You can also switch to one or the other from Goto > Grap
hical Editor.)
> Configuration > Display Change > (or change icon or F5)
Edit > Transport Target Groups > Create
In the dialog box, Create Target Group:
Enter a name for the target group /GR_QA/ (The name must begin and end with a fo
rward slash /)
...and a description Targets for Consolidation route
Choose "Insert line"
Enter the required target system/client combinations
Use a separate line for each client.
Example:
Target System
Target Client
Client Name
DEV
0X1
Sandbox
DEV
0X2
Testing
QAS
0XX
Quality Assurance System
The idea is that we want to include the clients that will get an addition to the
ir import queue when we release a change request from DEV.
Choose Transfer
Now you have to change the transport route to include the Target Group you creat
ed.
STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes >
Delete
Now create a Transport Route with Extented Transport Control:
STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes >
Create > Extended Transport Control icon at lower left of dialog box. > Consolid
ation route, enter integration system and transport layer. In Target system/clie
nt enter the SID of either an R/3 System and a client or an existing Target Grou

p.
Each System must be specified by System and Client. The Target Group can be used
for the consolidation system.
Distribute and activate the changes as usual by choosing Configuration > Distrib
ute and activate
NOTE: After you set up Extended Transport Control there might be requests in an
import queue that will show a red status in the CTL column. This is because thes
e change requests need a client specified before they can be imported. These are
old requests that were already in the queue.
From Import Queue Screen Mark the change request
Choose Request > Target Client > Set
Enter the Target Client ID and choose Enter.
To change a target client before starting an import:
Import Queue Screen > mark Change request > target client > change > enter targe
t client id and choose enter.

Find transports imported into system by search criteria

To find transports imported in a particlar system log into it,
1. Use transaction se16
A D V E R T I S E M E N T
2. Table name is E070
3. Table contents
4. Enter your search criteria, by Name, Date, Time, etc.
Good to use if you suspect a problem in your system and want to trace back trans
ports that went in that possibly could have caused the fault.
Transporting a Request From OS
To import a transport request from OS .
# cd /usr/sap/trans
# tp addtobuffer <transport request> <SID> pf=<transport profile> # tp import <t
ransport request> <SID> pf=<transport profile>

Find Your SAP Transport Request Number Even If You Forgot

If you happend to be one of those who forgot the transport request number of you
r abap program.

You can easily find it via the Versions Management.

Steps :Transaction SE38
Filled in your ABAP program name.
Then click Utilities -> Versions -> Version Management
SAP system will display this sample list :Versions: Report source ZPROGRAM
Version Cat Fla SAP Rel. Arch Request

Date

Time

Author

Version(s) in the development database:

X activ
SAP

X 46X

01.08.9999 15:21:56

Version(s) in the version database:

X 00002
X 00001 S

46X

ABCD123456

X 46X

01.08.9999 15:52:43 SAP

00.00.0000 00:00:00

Comparing SAP Objects

You can compare the IMG setting between two systems using OY19.
Comparison can be made for individual application components or all the applicat
ion components.

How To Do the TMS Configuration?

We have two systems with version ECC 5.0
A D V E R T I S E M E N T
The SID is XY1 - Development & Quality
XY6 - Production
Now we need to configure TMS between these two systems by assigning XY1 as domai
n controller. I beleive we also need to establish an RFC Connection for this. Al
so 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.
3.
4.
5.
6.
7.

Goto SE06.
Click Post installation activities
Goto STMS
It will ask for Domain controller name.
Enter DOMAIN_<SID> as domain controller name and enter the description.
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 bla
nk 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.
2.
3.

Select the Database Copy or migration option

Press the Post-installation Processing button.
When prompted Do you want to re-install the CTS?, press the Yes button

4.
When
the <SID> of
ontinue.
5.
When
6.
When
7.
When
8.
When
ton

prompted *for* the Source System of Database Copy?, make sure that
the production system is selected. Press the checkmark button to c
prompted
prompted
prompted
prompted

Change
Delete
Delete
Delete

originals from PRD to QUA?, press the Yes button

TMS Configuration?, press the Yes button
old TMS configuration?, press the Yes button
Old Versions of transport routes?, press the No but

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 Tran
sport Domain should be displayed
2.
The information on *this* screen is automatically filled out from inform
ation 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. Otherwi
se, 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 rout
es 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 pr
inter 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 creat
ed 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 custo
mizing 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.
4.
5.

From the Edit menu, select Software Components Modifiable

From the Edit menu, select Namespaces Modifiable
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 req
uests 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 th
e 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 im
mediately. 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 mod
ify the job.
3.
Press the Step button.
4.
Select the RSCLXCOP line and press <CTRL>+<SHIFT>+<F7> to modify that st
ep.
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 o
f jobs
13.
Continue to press <F8> every once in a *while* to update the status of t
he job. Do not *continue* until the job is completed sucessfully.
SCC4
1.
2.
3.
or 066)
4.
5.

From the Table view menu, select Display -> Change

When warned that the table is cross-client, press the checkmark button.
Double click on one of the non-system clients (i.e. not client 000, 001
Set the Protection to Protection level 1
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 leav
e *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 prod
uction system.
5.
From the Profile menu, select Delete, then All versions, then of a profi
le.
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 th
e No button.
8.
Repeat steps 3 through 7 *for* all additional profiles associated with t
he 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 Insta
nces, 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 selec

ting the Update Records menu, then Delete.

4.
Press the Continue button to confirm the deletion.
Delete
SM35
1.
2.
3.
4.

Batch Input Sessions

From the Edit menu, select Select All
Press <Shift>+<F2> to delete all the batch input sessions.
Press the checkmark button to confirm
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.
2.

From the TemSe database menu, select Consistency check

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 besi
de 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 besi
de 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 R
FCs.
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 shou
ld be called on *this* newly refreshed system (i.e.WIITRN400) Note: Ignore Err
or/Warning about duplicate system by clicking on the check mark.
5.
De-select the Test Run and Existence check on *new* names in tables opti
ons
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 log
ical system names that need to be changed.
Adjust
SALE
1.
2.
3.
4.

Logical Systems names

Expand Sending and Receiving Systems, then Logical Systems
Click on the execute icon beside Define Logical System
Press the checkmark button to confirm that the change is cross client

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 do
esn'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 t
he 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\TF60SE
RVER.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 success
ful, take the necessary steps to resolve the issue.
SE38
1.
2.
3.
4.
5.
essary

In the Program field, enter RPUBTCU0

Press <F8> to execute
Select option BSI version 7.0
Press <F8> to execute
BSI should *return* tax calculations. If there are errors, take the nec
steps to resolve.

Reconfigure DB13 schedule

DB13
1.
Using the print out created before the refresh, recreate the DB13 calend

ar.
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 cha
nges
Client-independent object changes: Changes to repository and cross-client custo
mizing 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 cu
stomizing 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 cu
stomizing 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 custo
mizing 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.
2.
3.

Press the System Change Option button.

Set the global setting to Not Modifiable
Press <CTRL>+S to save.

Release Background Jobs

Currently, all background jobs, except *for* system standard jobs have been plac
ed 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 /u
sr/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 lo
gs at OS level, then you can check in "Goto-> Import History" in the same transa
ction 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 step
s of the request in each of your SAP system.
Just double click on a step, e.g. 'Import', 'Check Version','Export' etc. to dis
play 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 alphab
et denoting a particular transport action.

Transport Tables between Clients

Use report RSCLCCOP to transport user master records, profiles and authorizatons
between clients in an R/3 system.
A D V E R T I S E M E N T
Start RSCLCCOP from the target client which the users and authorizations should
be copied.
Do not use this report if the target client contains some users and authorizatio
ns you want to preserve.

Copying table entries from client 000

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I do
n't know how to move the entries.
The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here
select 'adjust',
Then select the client that you want to compare/copy from (you need to have an R

FC destination set up).

This will then show you the contents of the table in both clients and identify t
he status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields
You should be able to scroll down the table, select the entries that you want to
import, then hit the 'adjust' button, then hit the 'copy all' button, then back
out with the green arrow, and save your table.
That should do the job.

SAP Tablespace sizes in large databases

-----Original Message----Robert and others following the thread,

First a little background on extents in our production system. We created the in
stance about 4 months prior to going live. As man of you know, getting down time
during the last few months is nearly impossible, so we saw and let extents grow
. In fact, by the time we went live, we had 2 objects over 450, 5 objects over 3
00, about 50 objects (tables and indices) that were over 100 extents, and we had
hundreds of objects over 10 extents.
I agree to doing both planning for growth and monitoring growth. And the earlier
in your SAP implementation you do this the better - which is something we did n
ot do until after we created our productive instance.
We were very concerned about this situation and spoke to 3 or 4 different SAP co
nsultants. We got the same answer from each - objects in high extents will have
little or no performance impact. Like Sanjay mentioned, the consultants had no s
pecific reason for this.
I do not believe you will find an SAP employed person who will say you should ke
ep extents below a specific value. Also, I cannot definitively give that advice
either.
Over the months we have all our objects below 100 extents. We have not seen a si
gnificant change in database response time. Our goal is to have all objects belo
w 20 extents - which is a corporate standard.
But we will not ask for extra down time to reach this goal.
Good luck trying to keep objects below 10 extents. While data is "pumped" into t
he system during the weeks before going live, whatch the extents, they will take
off. This also occurs after performing a SAP version upgrade.
-----Reply Message----Why not do both? Planning for growth is critical. Monitoring daily can be automa
ted via CCMS can it not? With proper alert thresholds, a system freeze can be th

warted long before extents reach 300 (max extents in my version of Oracle).
My question to you both is, how many extents are to many? I have heard from cons
ultants that SAP says that, for performance reasons 10 is the limit. I do not un
derstand the logic in this. Unless There is alot of fragmentation throughout the
tables, why not 50 or 100? I just completed a Client Copy and have 4 tables in
the BTABD tablespace that are over 17
extents. Is this to many? and should I lose the uptime for a reorg for 17 versus
10 extents?
I guess what I am asking is, since both of you seem to have put some thought int
o this, is there a hard-and fast number when in comes to an acceptable amount of
extents? SAP seems to be overly conservative most of the time - was wondering i
f anyone has good numbers?
Users Profiles and Password
Different methods to Lock or unlock SAP users
A D V E R T I S E M E N T
I want to lock all the users in SAP during MTP. I know using SU10 we can do it.
Any other alternative ways to lock the users.
Is there a way in SAP to unlock a locked user for a limited time, then automatic
ally after x time set the user back to lock status?
You can fill in "valid from" and "valid until", but you cannot say from Monday t
o Friday from 8 - 12:00 for part time workers.
Can we schedule to lock all users?
If users get locked, from SU01 you can unlock them.
Use SU10 to mass lock/unlock the users.
Use address data or authorisation data to get a list of users - select the ones
you want and
click transfer.
Once this is done click on lock or unlock.
You can also use transaction code EWZ5 to mass lock/unlock the users
or
Execute program EWULKUSR in SE38
or
Set a profile parameter (login/failed_user_auto_unlock) to unlock at midnight th
e locked users.
or
Here's an ABAP code, short and simple, isn't it?

REPORT zreusrlock.
DATA: time_limit TYPE sy-datum.
DATA: days TYPE i VALUE 40.
time_limit = sy-datum - days.
UPDATE usr02 SET uflag = 64 WHERE trdat < time_limit.
If you don't want to specify the time in the program, you can use SE38 to schedu
le it as a daily background job with the date and time.
or
Probably the easiest way would be to write a sqlplus SQL script that sets all th
e UFLAG fields in table USR02 to 64 EXCEPT for the BNAMEs you don't want locked.
When you are done, you can do the same again but change the UFLAG field to 0.
The SQL statement would look like:
update SAPR3.USR02 set UFLAG = 64 where MANDT = <client number> and BNAME != <do
n't lock user 1>
AND BNAME != <don't lock user 2>;
You can replace != with <> if you want. To run this from an OS command line, you
would type:
Unix/Oracle 8--->
NT/Oracle 8.0--->
NT/Oracle 8.1--->
Unix/Oracle 9:-->
NT/Oracle 9----->

sqlplus internal @<SQLpath+SQLname>

plus80 internal @<SQLpath+SQLname>
sqlplus internal @s<SQLpath+SQLname>
sqlplus /nolog @<SQLpath+SQLname>
sqlplus /nolog @<SQLpath+SQLname>

In UNIX you can cron the script to schedule it. In NT you can schedule it as a t
ask.
or
This is another method to UNLOCK ALL users.
Start Oracle Server manager (I assume you are on Oracle)
connect internal
update sapr3.usr02 set uflag='0' where mandt='399';
When users are locked, the uflag is set to 64.
Finish, just query to check.
select bname, uflag from sapr3.usr02 where mandt='399';
Please note that unlocking users from low level (like Oracle sqlplus) should be
used as last resort. Frequent use of low level access may tempt you to use on ot
her things. Highly dangerous and your IS auditors will not be too happy.
Is there a way to set a list of users that cannot be locked, even if we try to l
ock them manually, and even if they fail connection ( wrong password )?
Increase this parameter in SAP Instance profile:
login/fails_to_user_lock = 6 (max is 99 wrong attempts, i.e, value 99). Currentl
y you have a value of 3.

login/failed_user_auto_unlock (for your midnight unlocking).

Ask users to remember passwords!! If someone is deliberately login-in with diffe
rent username/password (thereby blocking legitimate access of that user), check
hostname from SM21.
This is considered as DoS (Denial of Service).

Changing the default password for sap* user

You are trying to change the password for sap* user, however when you go into su
01 and enter sap* as the user name, the following message is displayed, user sap
* does not exist.
You can delete the SAP* user using ABAP code :Delete from usr02 where bname = 'SAP*' and mandt = '***';
Where '***' means your client no.
Then login to your client using password SAP* and password PASS
However, if you delete it, then it will automatically created once again with pa
ssword PASS
The userid, SAP*, is delivered with SAP and is available in clients 000 and 001
after the initial installation. In these 2 clients, the default password is 0706
1992 (which is, by the way, the initial date when R/3 came into being...). It is
given the SAP_ALL user profile and is assigned to the Super user group. When I
say it is "delivered" with SAP, I mean that the userid resides in the SAP databa
se; there are actually rows in the user tables used to define userids.
If you delete the userid, SAP*, from the database, SAP has this userid defined i
n its kernel (the SAP executable code that sits at the operating system level, i
.e., disp+work). When this situation exists, the password defined in the SAP co
de for SAP* is PASS. This is necessary when you are performing client copies fo
r example, as the user information is copied at the end of the process. You can
sign into the client you are creating while a client copy is processing using SA
P* with password PASS (but you should have a good reason to do this - don't chan
ge anything while it's running).
Anyway, if the SAP* userid is missing, you can sign in to the client you want an
d simply define it using transaction SU01 and, as I stated above, assign it to t
he SUPER user group and give it the SAP_ALL profile. You define its initial pas
sword at this point. If you've forgotten its password and don't have a userid wi
th sufficient authorization to create/change/delete userid,
then you can use the SQL statements to delete it from the database and then you
can use SAP* with PASS to sign back into the client you want to define it in and
recreate it.
There is also a profile parameter which can override the use of SAP* with PASS t
o close this security hole in SAP (login/no_automatic_user_sapstar). When this
parameter is defined either in your DEFAULT.PFL profile or the instance-specific
profile and is set to a value of '1', then the automatic use of SAP* is deactiv
ated. The only way to reactivate the kernel-defined SAP* userid at this point wo

uld be to stop SAP, change this parameter to a value of 0 (zero), and then
restart SAP.
The default password for SAP* is 06071992. (DDIC has 19920706)

Mass Maintenance of Users Profiles

Goto transaction code SU10

Select your SAP User by Address data or Authorization data.
With the users you want to change selected, click :User -> Change -> Profiles
Filled in the Profiles and click save.
How can I create multiple User Id at Random
We usually created Id though SU01, it only one by one.
Can I create multiple user id having same profile at once.
Yes you can, use tcode SCAT. First, make sure your client setting (SCC4) is enab
led with ' X eCATT and CATT allowed'. Just in case your Production disabled this
.
- Then, you need to create a simulation (test case) of creating new user id by c
alling tcode
SU01 later.
- Test case must start with Z, example ZCREATE_NEW_USER. Create this case, put t
itle and
choose component as BC (basis components).
- Save and choose Local if you dont want to transport it or choose a dev. class
(example ZDEV)
if you want to transport it later.
- Go back and click Change button. Then key -in Object as example SU01, and choo
se Record
button on top. When it prompts to enter Transaction code, key in SU01 (if for
roles,
key-in PFCG) and begin recording. As usual in SU01 create 1 user id, dept fie
ld, password,
roles, group and so on.
- Make sure you press Enter on each field because we want to capture the value/o
bject and
SCAT is a bit stupid if you become familiar later....but still useful...indee
d.
- You will see a clock on the bottom which means the recording process is on goi
ng.
Once done, click Back button and press End button to end the recording.
Note - I noticed you said the profiles are all the same. Then this is much easi
er...no need to enter the roles/profiles, just duplicate this ID and change the
name, dept and password only.
Okay..first stage has finished. Then double click the Object to begin inserting

parameters. Then you will see an object for each fields that you run from SU01.
Choose the right field example user id (BNAME) and choose button 'Insert Import
Parameter (F6)' and you may click Next Screen to 'watch' what have been recorded
and proceed to choose several other objects like password field (PASSWORD1, PAS
SWORD2), roles field (AGR_NAME), group field etc. If you happen to choose the wr
ong object, then you can reset back (Edit -> Reset Parameterization). You may se
e so many junk fields captured and this is because SCAT records every steps/dial
ogs.
Once done, choose Back and save this case. Then you need to click 'Goto -> Varia
nt -> Export' and save it. After that use Ms Excel to open it and begin insertin
g all other user ids. Save and close. Remember to close this file because SCAT w
ill use it.
Then last one, get back to SCAT and click button execute, processing mode chose
Background, choose external file 'the one you created with Excel' and execute. A
t this moment don't use tcode SU01 bcoz you may interrupt the simulation. Wait f
or the logs. If you see reds then error was
happening.
Hoping this will help you. I have done (Sap 4.6C) this to create thousands of us
er ids and also thousands of roles/profiles (pfcg). I heard with Sap 4.7, the SC
AT has so many extra features.....
Correct me if i'm wrong elsewhere.....just shared my experience.