SAP Library - Find your answers

Goto SE37

Execute the report "ocs_reset_queue" and press F8

Checkthe "Uppercase/Lowercase" Box

In the mentioned fields IV_TOOL give the value as "SPAM"

In the IV_FORCE field give the value as "XX" and press F8

Use transactions SMLT to import new Language into the system. SAP supports 17 languages.

However, you can use the same transaction to change any settings also.

To change the automatically generated profile parameters for the transport control program:

Log onto the SAP System functioning as the transport domain controller (the QA or PROD system).

Call Transaction STMS.

Choose Overview -> Systems.

The system overview appears.

Double click on the SAP System you want to change.

In the SAP System, click Configuration -> Change.

The screen Change TMS Configuration: System appears.

Choose the tab Transport tool.

First, all the global parameters are displayed and then all the local parameters.

The global parameters are identical for all SAP Systems in the domain.

To change a global parameter to a local parameter, you must delete the global parameter and enter the new local parameter.

The operating system is only displayed if values exist for this field.

Finally to remove the import all request (big truck) button from STMS

click the Insert Line (button)
Tick Global
Fill in Parameter = NO_IMPORT_ALL, Value = 1.
Save your entries.
If you enter a parameter unknown to the transport control program, or a value that is not permitted, the transport control program ignores this entry in the transport profile.

Export SAP Users and Authorizations

1) Logon to the target SAP system in the client you want to save and go to transaction SCC8.

2) Select the SAP_USER profile and the Target System,

3) Click the Schedule as Background Job button and then check Immediately.

4) Click the Schedule Job button, click Continue.
If this system has more than 1 server, set Background Server to the Central Instance Server

5) Make a note of the KT transport number shown on the next window. The KT transport is for transporting client specific data.

6) The status of the export can be found using transaction SCC3.

7) After the export completes in SCC3, check the transport logs for the KT transport in SE01. The export is not finished until the "export" step shows completed successfully.

8) For systems with more than one client, you will need to follow the above steps on each client to create a transport of the users for each client.

Import SAP Users and Authorizations

Note: This procedure assumes the Users were exported and Transport created before the client copy

1) Import the appropriate user Transport for each Client (i.e. 100, 900, 910 etc) from CMD Prompt .
Import needs to be done from CMD prompt (Not STMS), and while import is running, log off of the system as all IDs will be deleted and recreated with the import.

In the examples below a full system was assumed. If you are only importing users from a Client Copy there will only be one transport.

For All R3 Systems

tp addtobuffer xxxKT0aaaa u1 pf=

tp addtobuffer xxxKT0bbbb u1 pf=

tp addtobuffer xxxKT0cccc u1 pf=

tp addtobuffer xxxKT0dddd u1 pf=

tp import xxxKT0aaaa client pf=

tp import xxxKT0cccc client pf=

tp import xxxKT0dddd client pf=

2) After the import is complete, Logon to the SAP GUI for each Client as SAP*

Execute Transaction: SCC7

If a message pops up that this is a Production Client and protected from Client Copies

Go into SM31 and table T000 and change Client to "Test"

Ensure the Transport that is displayed is the Transport you imported in previous step

Select "Execute in Background"

Monitor to completion in Transaction: SCC3

Repeat this process for each Client Transport Exported/Imported

Change Target Client back to "Production" - If necessary