This action might not be possible to undo. Are you sure you want to continue?
This article explains on how to analyze a long running BW load/job. 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.
Hit Ctrl+F and input our PID# from STEP 5. . STEP 11: Double click on our load process row and you will reach ‘Detail Display‘ screen as shown below. (‘Running’ in present case) and also you can find the current action performed by the process (‘Sequential Read’ on a table) as shown below. This will takes you to our load process row. Here our load status will be displayed. STEP 10: Now you will be in ‘Process Overview‘ screen. 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‘.
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. . When a BW load takes long time to finish and if the ‘Detail Display‘ screen looks like the pic.STEP 12: In the same screen. below. we need to investigate for hanging tRFCs in the system. then our load is progressing well and we can let it run If the process gets stuck with status ‘Stopped’ or ‘Waiting’ forever. In summary: If the load process is active and progressing. SAP BW Production Support Issues – Part 2 (Hanging tRFCs) We learned how to analyze a long running BW load in Part 1 of SAP BW Production Support Issues series in ‘Process Overview‘ transaction ‘Detail Display‘ screen. the ‘Action’ message moves continuously from one table to to another and database read count in STEP 12 progresses. at bottom we can find the detailed information about the database reads/inserts.
Put wild character asterisk ‘*’ in you need to get entire list of tRFC’s in the system as shown below. If a tRFC is held for long time.STEP 1 Go to the long running load monitor (T-code: RSMO) screen and from menu at top navigate to ‘Environment‘ -> ‘Transact. STEP 2 Now we will be in ‘Transactional RFC‘ list selection screen. -> To ‘In the Data Warehouse‘ . STEP 3 Now the screen will list all the tRFCs currently scheduled to execute or held up. if the data source is in same SAP system as of the current load -> To ‘In the source system‘ . These steps will clear the held up BW loads due to hung tRFCs. then we can manually push it by clicking on it from the list and then from menu go to ‘Edit‘ -> ‘Execute LUW‘ or pressing F6 as shown in below pic. . and hit ‘Execute‘ button. RFC‘ and then. Here enter the input parameters. if the data source exists in external SAP system (like R/3) as shown in pic below.
STEP 3 Now you will be in ‘manage’ screen of the ODS. STEP 1 Lets assume that we encountered the long running ODS/DSO step in a Process Chain(T-code: RSPC1) as shown in below pic. STEP 2 Right Click on the ODS activation step in PC and select ‘Administer Data Target‘ from the context menu options as shown below. copy the activation request number ( ODSR_….SAP BW Production Support Issues – Part 3 (Long running ODS/DSO Activation) As part of the Produciton Support Issues of SAP BW series. STEP 4 Now go to Table: ‘RSODSACTREQ’ (T-code: SE16) and input the activation request number (obtained in STEP 3) in ‘ACTREQUEST‘ field selection. as shown in below pic. lets see how to analyze a long running ODS activation step in this post.. Now hit the ‘Number of Entries’ button and the number we obtain is the total number of DataPackets to be activated. Here.) . (1658 in our case.) of the request that is currently in activation status (yellow status) as shown below.
. as shown below) The conclusion can be that the activation step has finished about 835 DataPackets out of 1658 total DataPackets (about half way) and based on the time it took to reach this point. STEP 6 Now look at the ‘DATAPAKID‘ values for non-zero ‘STATUS‘ entries ( DataPackets 836-838 in our case. as shown below. in the same table browser screen. SAP BW Production Support Issues – Part 4 (Object Lock Issues) In this post lets discuss the object lock issues that we sometimes encounter in SAP BW production support role. input ‘status‘ selection condition as ≠0 as shown below and hit ‘execute‘ button at top. STEP 1 Go to lock monitor (T-Code: SM12) screen and put an asterisk(‘*’) in the selection for ‘User name’ and then click ‘List‘ button at the top. we can estimate the how long its going to take to complete the ODS activation. Lets take the below example where the InfoObject(0material) load has failed and the load monitor (TCode: RSMO) looks like this.STEP 5 Now.
If you find an entry in list. So wait until some time and check again for lock on the object. as shown in pic below. . Click the ‘Find‘ button at the top. STEP 4 Now go to the load monitor again and then click on ‘Status‘ button. then look at ‘Lock Argument‘ to find what action/process is locking the object.STEP 2 Now the ‘Lock Entry List‘ screen displays all the locks currently set in the system. In our caste ‘material‘. Generally this could be another request loading into the same object or a load from this object to other objects. If you don’t find any entries in list then we are good to resume our load that has failed earlier. Our load cannot run until the current lock is cleared. as shown in below pic STEP 3 Now in the ‘Find‘ screen enter the object that has failed. Here click on the ‘Total‘ traffic light as shown below.
and is part of part of the ‘Produciton Support Issues of SAP BW’ series. . Here select the ‘Status Not OK‘ (red traffic light) option and hit ‘Save‘ button as shown below.STEP 5 Now we will be in ‘QM status set‘ screen. and if it’s a master data data into and InfoObject this step is not required. Note: STEPS 4. if it’s a transactional load into InfoCube or ODS/DSO then delete the failed request from the data target. STEP 1 The monitor ‘Details’ displays error as shown in below picture when a Masterdata load fails due to duplicate data error. STEP 6 Now. otherwise there is a good chance of missing delta records Now repeat the failed load and should not encounter any lock issues. SAP BW Production Support Issues – Part 5 (Duplicate Records) This post is on working with duplicate data records in Masterdata loads. 5 and 6 are very important in case of delta loads.
Right click on the InfoObject and select ‘Activate master data’ from the context menu as shown below Once the MasterData activation step is complete. These steps will complete successful MasterData load.Reason : Generally this error occurs when MasterData (MD) has been loaded earlier and it is in “modified” status in MasterData table. ‘Activation’ of the data will be carried out by ‘Attribute Change Run’ in a subsequest step either in a ‘Process Chain’ or in ‘Background’ job. back to green. If there is no PSA step or failed data packets are more then: Repeat the failed load. . STEP 3 Now go back to the monitor screen and set the ‘Total’ status of the failed request to red (even if it’s red already!) as shown in below steps. go back to load monitor screen of failed load. resulting in duplicate records error. Unless we execute ‘ChangeRun’ or ‘MasterData Activation’ step. This action will now push the data from PSA to MasterData object. Once this step is successful we can change the ‘Total’ status that we changed earlier to red in STEP 3. If YES. the data remains in “modified” status and is not reportable. Now our current MasterData load fails to insert the latest changes into the same table in “modified” version as the earlier records are still sitting in the table. STEP 2 Create a new session and go to Administrative Work Bench AWB (T-code: RSA1) Then select from menu select ‘Tools’-> ‘Apply Hierarchy/Attribute Change …’ Or (Crtl+F9) Now we will be in ‘Change Run Reporting’ window as shown below Here click on ‘InfoObject List’ button and one of the listed InfoObject should be the MD object which pertains to our current failed load with duplicate records. and only a couple of Datapackets have failed with this error: then right click on that Data Package and select ‘Manual Update’ as shown in below pic. In the ‘Details’ tab here check if the failed datapacket has been loaded succesfully into PSA. STEP 4 Now go to Administrative Work Bench(AWB) and from ‘InfoObjects’ screen find the failed InfoObject.
DATA LOAD FAILURES DUE TO INVALID CHARACTERS: STEP1: Loading was failed due to invalid characters present in the data. . Also you can able to know what are the allowed characters by Clicking on LongText button. to exactly know in which record error has been occured.Click on the InfoCube and go to Manage. STEP3: Now Rt. to delete the failed Request as shown below. STEP2: Click on the Details Button.
Then it popup new window. in that edit the errored Record and Click on Continue.STEP4: Now GoTo T-Code RSMO. to edit the PSA Records as shown below. . Then it popup new window. press continue as shown Now Select the Error Record. Click on the PSA button as shown. and click on edit button as shown.
STEP5: Now Schedule the load.Now Click on the Save Button to save the data in the PSA. . Click on the DataTarget Button to see the content of the InfoCube as shown above. to load the data from PSA to InfoCube as shown screen by screen.
This action might not be possible to undo. Are you sure you want to continue?