Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member


When there is any data related issue in a DSO e.g. when there is any Incorrect entry loaded to the DSO or if someone has made any modification to existing data in DSO, Change log will help to find out what was changed, when was it changed and by whom it was changed. We can get complete information on all the records that were loaded on a particular date and time.


  • DSO structure must be of type “STANDARD”.

  • Understand the table names related to the DSO for which we need the change log.
  1.      Double click on the DSO and click on “Information-->Dictionary/DB status”

     2.     You can get the Change log table name from Change Log column.


Step # 1: Understand Table Names that are relevant.

Find the Change log table name as discussed in the pre requisites.

Step # 2:

Transaction: SE16.

Enter Change log table name found in step #1: /BIC/B00XXXXXXXXX

Click on ‘Execute’ Icon

Step # 3:

Next window will be selection window. Give the necessary selection criteria. Click on Execute Button

Step # 4:  Next window will show the contents of change log table

Step # 5: To understand, when that particular data was loaded? Find the ODSR # for the request.

Copy the value in Request ID column of the desired data:

In the following example, say ‘ODSR_25NYZ1BM76TQWUY4W2H7OP2L1’ for User CH8958.

Step# 6: Enter the ODSR# in Table ‘RSSTATMANPART’.

Transaction: SE16, Table Name: RSSTATMANPART, enter ODSRNR value picked up in previous step# 5 and click on execute.

Step# 7: The next window would show the request loaded date and time.

Note: This date and time will be in GMT

Scroll to the right:

Troubleshooting of Change Log Table:

Below is an example to check what data has been loaded for a user so far say user: CC8722.

  • Go to tcode SE16 and enter the change log table name  and execute

  • In the next screen enter the user id in TCTUSRNM column and execute.

  • In the next screen you will find all the requests that were loaded in DSO for user CC8722.

  • In the above Change log table, there is a column RECORDMODE which contains N, X and blank space. N refers to New image, X refers to Before image and Blank refers to After image.
  • Here in above screenshot there is N in the RECORDMODE for request ODSR_4RBMMA1IGIZ4LVPURDBZEMEWL. This means new entry has been been loaded for user CH8958.

      In this case, user CC8722 is assigned with entry ZFMR_TCH001 (with validity date between 26.09.2012 to 26.09.2013) for the first time. So the record is      saved as New Record (New Image).

     Note: Whenever an entry is loaded for the first time, record mode will be N.

  • Then, request ODSR_4RY00FS50OXDTX7XA8GX7ZXF9 is loaded for the user and it is repeated twice. Once with record mode X (Before image) and with record mode Blank(After Image).

  • Record mode X (Before Image) denotes how the data was present before data load and Record Mode Blank (After Image) denotes how the data has been changed after data load.

     In request ODSR_4RY00FS50OXDTX7XA8GX7ZXF9, Record mode X shows validity date between 26.09.2012 to 26.09.2013 and Record Mode blank shows      the validity date between 20.11.2012 to 20.11.2013. This means, the validity date of entry ZFMR_TCH001 is changed from 26.09.2012 to 26.09.2013 (Record      Mode X) to 20.11.2012 to 20.11.2013 (Record Mode Blank) for user CC8722 in this request.

  • Similarly in the next request ODSR_4S0HTAKFYBNICDR9KPPVV5JW5, the validity date for the entry was changed from 20.11.2012 to 20.11.2013 (Record Mode X) to 27.11.2012 to 27.11.2013 (Record Mode Blank).

  • And in the next request ODSR_4S10OXH1UGQUEWTLQ21CXV2ET, the validity date for the same entry is changed from 27.11.2012 to 27.11.2013 (Record Mode X) to 29.11.2012 to 29.11.2013 (Record Mode Blank)

Below steps help you identify when the particular request was loaded, who loaded the request and gives more details on the data that was loaded in the request.

  • Go to tcode SE16 and enter RSSTATMANPART and execute.

  • In the next screen click on the Multiple selection icon on ODSRNR column highlighted below

  • Now Copy all the ODSR# request ID’s from change log table and paste it in the next screen and click on copy highlighted below


     Note: If a ODSR# request id is found more than once in change log table, copy only one request id from it and paste it in above selection screen.

  • In the next screen, we can find the request loaded date and time.

  • Now we have the Request load date and time from table RSSSTATMANPART. With this information we can find what data was loaded for a user on a particular date.

     Here in this example, the first request was loaded on 26.09.2012 as you can see in above screenshot. Let us check what data was loaded in each of the      above requests.

  • The first request was loaded on 26.09.2012. Copy the corresponding ODSR# request id (ODSR_4RBMMA1IGIZ4LVPURDBZEMEWL). To check what data was loaded on that particular request we need to go to “Manage” of the DSO.

  • As we are looking for older record, we need to select the suitable date in “Request Display: Date of Update From” column highlighted below and click on Refresh. You may filter the date for which we require the information.

  • Now scroll down to find the request date that we are looking for. Here there are 2 requests that are loaded on the 26.09.2012.

  • The ODSR# request id that we are looking for will be present in one among the above highlighted requests. To find the request corresponding to our ODSR# request id (that we copied in earlier step in table RSSTATMANPART) we need scroll to the right of the screen. The 2nd last column contains the ODSR# request id.

  • Now to find what data was loaded for the user CC8722 in this request, click on monitor icon highlighted below.

  • In the next screen there will be 2 tabs – Header and Details. In the header tab you can get the PSA request ID and the user who loaded the request.

  • In this case the request was loaded by user BG5259. Copy the PSA request id (452841) that we got in the previous screen.

  • Now click on back icon and navigate to RSA1 screen. Expand DSO till its datasource. Right click on datasource and click on manage.

  • PSA table opens in the next screen. Again you need to change the “Requests newer than “  field and refresh as we are looking for an older request. I have filtered the requests from 26.09.2012 to till date

  • There are 2 requests in PSA for 26.09.2012. We have already copied a PSA request id (452841) in previous step.  Find the request id in PSA screen, select its row and click on PSA maintenance icon highlighted below.

  • The next screen will show how many data’s were loaded in the request. Click on the Tick mark highlighted below.

  • The next screen will show the data that was loaded in this request.

     Here in above request, user CC8722 was assigned with entry ZFMR_TCH001.

  • Similarly we can check the data that was loaded for other ODSR# request id’s

     Below are the data’s that are loaded in DSO for user CC8722 in other requests

     ODSR_4RY00FS50OXDTX7XA8GX7ZXF9 (22.11.2012):

     ODSR_4S0HTAKFYBNICDR9KPPVV5JW5 (27.11.2012):

     ODSR_4S10OXH1UGQUEWTLQ21CXV2ET (29.11.2012):

     By this way we can find when a data was loaded to DSO and troubleshoot on data related issues on a DSO.

Labels in this area