STEP 1:
Go to T-code ‘RSMO‘ and identify the long running load. Then find the ‘Request Number‘ of the load as shown in below pic.
STEP 2:
Clicking on the Req. No. pops up a window as shown in below pic. Copy this Req. No.
STEP 3:
Then goto the Job monitor screen (T-code: SM37) in the source system (Same system if source exist in the same SAP system) and enter the Req. No. we got in STEP 2 as shown below, prefixed with an asterisk ‘*’ and then hit ‘Execute’ button.
This will take you to ‘Job Overview screen‘ as shown below.
STEP 4:
Double clicking on the job in above screen takes you to below screen. Here click on ‘Job details‘ button
STEP 5:
From the job details screen note the PID# as shown below
STEP 6:
Now goto T-code ‘sm66‘ screen which give the global work process overview. Hit ‘find’ button (Ctrl+F) and input the PID# we obtained in STEP5
STEP 7:
This will display the status of our load process (In our example ‘Stopped’ as shown below)
STEP 8:
Clicking on the PID # in above screen will put the cursor on our load process, as shown below.
STEP 9:
Now leave the cursor on our process as in STEP 8 and then goto menu bar ‘Goto‘->’Local work processes‘, as shown below.
STEP 10:
Now you will be in ‘Process Overview‘ screen. Hit Ctrl+F and input our PID# from STEP 5. This will takes you to our load process row.
STEP 11:
Double click on our load process row and you will reach ‘Detail Display‘ screen as shown below. Here our load status will be displayed. (‘Running’ in present case) and also you can find the current action performed by the process (‘Sequential Read’ on a table) as shown below.
STEP 12:
In the same screen, at bottom we can find the detailed information about the database reads/inserts.
In summary:
Go to T-code ‘RSMO‘ and identify the long running load. Then find the ‘Request Number‘ of the load as shown in below pic.
STEP 2:
Clicking on the Req. No. pops up a window as shown in below pic. Copy this Req. No.
STEP 3:
Then goto the Job monitor screen (T-code: SM37) in the source system (Same system if source exist in the same SAP system) and enter the Req. No. we got in STEP 2 as shown below, prefixed with an asterisk ‘*’ and then hit ‘Execute’ button.
This will take you to ‘Job Overview screen‘ as shown below.
STEP 4:
Double clicking on the job in above screen takes you to below screen. Here click on ‘Job details‘ button
STEP 5:
From the job details screen note the PID# as shown below
STEP 6:
Now goto T-code ‘sm66‘ screen which give the global work process overview. Hit ‘find’ button (Ctrl+F) and input the PID# we obtained in STEP5
STEP 7:
This will display the status of our load process (In our example ‘Stopped’ as shown below)
STEP 8:
Clicking on the PID # in above screen will put the cursor on our load process, as shown below.
STEP 9:
Now leave the cursor on our process as in STEP 8 and then goto menu bar ‘Goto‘->’Local work processes‘, as shown below.
STEP 10:
Now you will be in ‘Process Overview‘ screen. Hit Ctrl+F and input our PID# from STEP 5. This will takes you to our load process row.
STEP 11:
Double click on our load process row and you will reach ‘Detail Display‘ screen as shown below. Here our load status will be displayed. (‘Running’ in present case) and also you can find the current action performed by the process (‘Sequential Read’ on a table) as shown below.
STEP 12:
In the same screen, at bottom we can find the detailed information about the database reads/inserts.
In summary:
- If the load process is active and progressing, the ‘Action’ message moves continuously from one table to to another and database read count in STEP 12 progresses, then our load is progressing well and we can let it run
- If the process gets stuck with status ‘Stopped’ or ‘Waiting’ forever, then we need to investigate the reasons and may have to kill the our process PID# and delete the failed load from targets and restart the load.
thanq u so much rakesh...i am searching for this step by step process in net from a long time...at last i got it...!
ReplyDelete