Hello everybody,

here is ZUSRMON v366+ (27-Aug-2008) for SAP Solution Manager 4.0 Basis Release 7.00 Unicode.
http://www.geocities.com/redchenko/zusrmon.html

This archive consist of four files:

R900030.SMP - Main data of the transport request SMPK900030.
K900030.SMP - Control file for the transport request SMPK900030.
"SMPK900030 - Object list.txt" - Just info about objects contained in the transport request.
readme_ssm.txt  - this file

Extract all files from RAR-archive to local directory on your computer, for example, C:\Temp\


How to import the transport order SMPK900030 to your Test (Sandbox) SAP System.

1. At first, you need to find out where the transport directory of your SAP system is.
To do this, go to transaction AL11 in your test (sandbox) SAP system and look for the parameter DIR_TRANS.
Its value points to the transport directory on application server. Remember its value.

For UNIX-based application server, it usually set to /usr/sap/trans.
For Windows-based application server, it looks like \\servername\sapmnt\trans\.
For instance, I keep in mind that your DIR_TRANS = /usr/sap/trans.

2. Now you need to upload transport files to the transport directory.

Start transaction SE37.
Type name of the function module: ARCHIVFILE_CLIENT_TO_SERVER, then press Test/Execute (F8)

Specify parameters (case sensitive!!):

UPPERCASE/Lowercase = X

PATH = C:\Temp\R900030.SMP
TARGETPATH = /usr/sap/trans/data/R900030.SMP

(
For Windows-based SAP system, TARGETPATH should be like this:
\\servername\sapmnt\trans\data\R900030.SMP
)

Press (F8) to execute.
Result: Main file R900030.SMP has been uploaded to "(DIR_TRANS)\data" directory on application server.

Repeat similar steps with control file:

UPPERCASE/Lowercase = X

PATH = C:\Temp\K900030.SMP
TARGETPATH = /usr/sap/trans/cofiles/K900030.SMP

(
For Windows-based SAP system, TARGETPATH should be like this:
\\servername\sapmnt\trans\cofiles\K900030.SMP
)

Press (F8) to execute.
Result: Control file K900030.SMP has been uploaded to "(DIR_TRANS)\cofiles" directory on application server

3. Now go to the Import Queue of your test (sandbox) SAP system:
Start transaction STMS_IMPORT.

Enter command APRQ directly into Ok-code (or, alternatively, choose menu path  'Extras -> Other requests -> Add')
Type request name: SMPK900030, Confirm with Enter, Yes.

As result, a new entry will be added to the Import Queue:

SMPK900030   ARED              ZUSRMON v366 for Solution Manager (27-Aug-2008) - LIGHT

Select this entry with singleclick then press (Ctrl+F11).

In a popup window specify target client (for this transport, you may
specify client 000 or your current logon client, it does not matter).

To ensure the import will be safe, first execute it in TEST MODE:

On a tabstip "Options" check the first three checkboxes:

X "Leave Transport Request in Queue for Later Import"
X "Import Transport Request Again"
X "Overwrite Originals"

and press the button "Test Import (F8)".
When test import completed, check import logs: Request -> Display -> Logs (Ctrl+F4).

The system will notify you about possible conflicts which may occur during real import.
If there aren't any conflicts, you may do real import.
Go back to the Import queue, place cursor at line with request SMPK900030, press (Ctrl+F11),
specify target client 000, but on the tabstrip "Options" check 1st checkbox only:

X "Leave Transport Request in Queue for Later Import"

and then press Enter. Confirm query with Yes. Import will start.

If import done without any errors, just type /nZU or /nZUX in Ok-code to run ZUSRMON.

Note: This instruction and transport files are valid for SAP Solution Manager 4.0 Basis release 700 Unicode.
Let me know, if you use another version of SAP system (e.g., SAP R/3 4.6C, or SAP BW,
or SAP ERP 6.0). I will try to send you appropriate version of transport files/instructions.

Good luck!

-- 
Best Regards,
Alexander

mailto:redchenko@yandex.ru
