Change log in SU01

Hi all,
Im trying to trace the First name and Last name change in SU01. Hence in SU01, i goto file menu -> Information -> Change documents for users.
But the change log didn't record the First/Last name changes on SU01. This proven by my testing where i change First/Last name for my own ID via SU01. From the change log. the changes are not recroded.
Could you please advice how can i get the change log for First/Last name?
Thanks in advance.

Hi,
SAP provides a special log for changes in user master. As it was mentioned you can get these changes from report RSUSR100. This log does not cover first and last name.
But as it was mentioned by Bernhard SAP has this concept of change documents which are used in various use cases. You can see all change document definitions in transaction SCDO. Here you have object ADRESSE3 which is used for user address. Hence any change in user address generates a record for this object. Both first and last names are covered here. So you can display all changes using report RSSCD100. Just set object class to ADRESSE3.
Cheers

Similar Messages

Change log of field USERTYP

Hi all, is there any way how to find history of changes of the above mentioned field? I am not able to find it via SU01->Change documents for users.

Hi Jaroslav
Sorry for late reply
Standard table USR06 change log is not there as there is no particular object maintained for recording log not allowed as technical settings. Below are some selected of US category for which you can search change log.
USLA04
USR21
USRACL
USREFUS
USOBT
USOBX
USOBT_C
USOBX_C
USMD120C
USMD120C
USR41
Sorry, can't help with standard available
But I have checked there is one Program which you can add in your system and that will help to record the changes in future.
for your reference program code is as below.
REPORT ZUSER_LICENSES_LOG.
TYPE-POOLS: ICON, ABAP, SLIS.
TABLES: ADCP,
        USR02,
        USR06,
        USR21,
        PA0002.
TYPES: BEGIN OF USER_TABLE,
         PERSNUMBER TYPE USR21-PERSNUMBER,
         BNAME      TYPE USR21-BNAME,
         VORNA      TYPE PA0002-VORNA,
         NACHN      TYPE PA0002-NACHN,
         LIC_TYPE   TYPE USR06-LIC_TYPE,
         FUNCTION   TYPE ADCP-FUNCTION,
         GLTGB      TYPE USR02-GLTGB,
         USTYP      TYPE USR02-USTYP,
         CLASS      TYPE USR02-CLASS,
         UFLAG      TYPE USR02-UFLAG,
         PWDSTATE   TYPE USR02-PWDSTATE,
         USRID      TYPE PA0105-USRID,
         PERNR      TYPE PA0105-PERNR,
         LICENSE_AX TYPE I,
         LICENSE_AY TYPE I,
         LICENSE_AZ TYPE I,
         LICENSE_BA TYPE I,
         LICENSE_BK TYPE I,
         LICENSE_OT TYPE I,
       END OF USER_TABLE.
DATA: IT_P2    TYPE STANDARD TABLE OF PA0002 WITH HEADER LINE,
      IT_P0105 TYPE STANDARD TABLE OF PA0105 WITH HEADER LINE,
      IT_TAB   TYPE TABLE OF USER_TABLE WITH HEADER LINE,
      WA_TAB   LIKE LINE OF IT_TAB,
      ITAB     TYPE TABLE OF USER_TABLE.
DATA: GR_ALV        TYPE REF TO CL_SALV_TABLE,
      GR_FUNCTIONS TYPE REF TO CL_SALV_FUNCTIONS_LIST,
      GR_DISPLAY    TYPE REF TO CL_SALV_DISPLAY_SETTINGS,
      GR_COLUMNS    TYPE REF TO CL_SALV_COLUMNS_TABLE,
      GR_COLUMN     TYPE REF TO CL_SALV_COLUMN_TABLE,
      GR_LAYOUT     TYPE REF TO CL_SALV_LAYOUT,
      GR_SELECTIONS TYPE REF TO CL_SALV_SELECTIONS,
      GR_EVENTS     TYPE REF TO CL_SALV_EVENTS_TABLE,
      GR_LINES      TYPE REF TO CL_SALV_FORM_LAYOUT_GRID,
      G_LAYOUT      TYPE SALV_S_LAYOUT_INFO,
      KEY           TYPE SALV_S_LAYOUT_KEY,
      S_KEY         TYPE SALV_S_LAYOUT_KEY,
      COLOR         TYPE LVC_S_COLO,
      RIGHT_ALIGNED TYPE SALV_DE_ALIGNMENT,
      LARGE_HEAD    TYPE SALV_DE_HEADER_SIZE.
DATA: USER          TYPE SY-UNAME,
      USER_SALON    TYPE SY-UNAME,
      LIST_TITLE    TYPE LVC_TITLE VALUE 'Multiple UPC Codes per Article'.
INITIALIZATION.
KEY = SY-REPID.
RIGHT_ALIGNED = 2.   "1=left, 2=right, 3=centered. Must be TYPEd as SALV_DE_ALIGNMENT.
USER = SY-UNAME+0(3).
USER_SALON = SY-UNAME+3(4).
SELECTION-SCREEN BEGIN OF BLOCK BLOCK1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS S_BNAME FOR USR21-BNAME.
SELECT-OPTIONS S_LTYPE FOR USR06-LIC_TYPE.
SELECT-OPTIONS S_TERM FOR USR02-GLTGB.
PARAMETERS P_VARI TYPE SLIS_VARI.
SELECTION-SCREEN END OF BLOCK BLOCK1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
G_LAYOUT = CL_SALV_LAYOUT_SERVICE=>F4_LAYOUTS(
             S_KEY    = KEY
             RESTRICT = IF_SALV_C_LAYOUT=>RESTRICT_NONE ).
P_VARI = G_LAYOUT-LAYOUT.
START-OF-SELECTION.
SELECT USR21~PERSNUMBER USR21~BNAME USR06~LIC_TYPE ADCP~FUNCTION USR02~GLTGB
         USR02~USTYP USR02~CLASS USR02~UFLAG USR02~PWDSTATE "PA0105~USRID PA0105~PERNR
    INTO CORRESPONDING FIELDS OF TABLE IT_TAB
    FROM ( ( ( USR21
    INNER JOIN ADCP
            ON ADCP~PERSNUMBER EQ USR21~PERSNUMBER )
    INNER JOIN USR02
            ON USR02~BNAME EQ USR21~BNAME )
    INNER JOIN USR06
            ON USR06~BNAME EQ USR21~BNAME )
*    INNER JOIN PA0105
*            ON PA0105~USRID EQ USR21~BNAME )
    WHERE USR21~BNAME       IN S_BNAME
      AND USR06~LIC_TYPE    IN S_LTYPE
      AND USR02~GLTGB       IN S_TERM.
IF SY-SUBRC = 0.
    SORT IT_TAB BY BNAME LIC_TYPE ASCENDING.
    CLEAR ITAB.
    CLEAR WA_TAB.
    LOOP AT IT_TAB INTO WA_TAB.
      SELECT SINGLE * FROM PA0105
        INTO IT_P0105
        WHERE USRID = WA_TAB-BNAME.
      IF SY-SUBRC = 0.
        WA_TAB-PERNR = IT_P0105-PERNR.
      ENDIF.
      SELECT SINGLE * FROM PA0002
        INTO IT_P2
        WHERE PERNR EQ WA_TAB-PERNR
        AND ENDDA EQ '99991231'.
      IF SY-SUBRC = 0.
        WA_TAB-VORNA = IT_P2-VORNA.
        WA_TAB-NACHN = IT_P2-NACHN.
      ENDIF.
      CASE WA_TAB-LIC_TYPE.
        WHEN 'AX'.
          WA_TAB-LICENSE_AX = WA_TAB-LICENSE_AX + 1.
        WHEN 'AY'.
          WA_TAB-LICENSE_AY = WA_TAB-LICENSE_AY + 1.
        WHEN 'AZ'.
          WA_TAB-LICENSE_AZ = WA_TAB-LICENSE_AZ + 1.
        WHEN 'BA'.
          WA_TAB-LICENSE_BA = WA_TAB-LICENSE_BA + 1.
        WHEN 'BK'.
          WA_TAB-LICENSE_BK = WA_TAB-LICENSE_BK + 1.
        WHEN OTHERS.
          WA_TAB-LICENSE_OT = WA_TAB-LICENSE_OT + 1.
      ENDCASE.
      APPEND WA_TAB TO ITAB.
      CLEAR WA_TAB.
    ENDLOOP.
    TRY.
        CL_SALV_TABLE=>FACTORY(
                   IMPORTING
                     R_SALV_TABLE = GR_ALV
                   CHANGING
                     T_TABLE = ITAB ).
      CATCH CX_SALV_NOT_FOUND.
      CATCH CX_SALV_MSG.
    ENDTRY.
    TRY.
        GR_FUNCTIONS = GR_ALV->GET_FUNCTIONS( ).
        GR_FUNCTIONS->SET_ALL( ABAP_TRUE ).
        GR_DISPLAY = GR_ALV->GET_DISPLAY_SETTINGS( ).
        GR_DISPLAY->SET_VERTICAL_LINES( ABAP_TRUE ).
        GR_DISPLAY->SET_HORIZONTAL_LINES( ABAP_TRUE ).
        GR_DISPLAY->SET_STRIPED_PATTERN( CL_SALV_DISPLAY_SETTINGS=>TRUE ).
      CATCH CX_SALV_NOT_FOUND.
      CATCH CX_SALV_MSG.
    ENDTRY.
    TRY.
        GR_DISPLAY->SET_LIST_HEADER( LIST_TITLE ).
        GR_COLUMNS = GR_ALV->GET_COLUMNS( ).
        GR_COLUMNS->SET_KEY_FIXATION( ABAP_TRUE ).
      CATCH CX_SALV_NOT_FOUND.
      CATCH CX_SALV_MSG.
    ENDTRY.
    TRY.
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'PERSNUMBER' ).
        GR_COLUMN->SET_LONG_TEXT( 'Person Number' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Pers#' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Pers#' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'BNAME' ).
        GR_COLUMN->SET_LONG_TEXT( 'Login Name' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Login Name' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Login' ).
        GR_COLUMN->SET_ALIGNMENT( RIGHT_ALIGNED ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'VORNA' ).
        GR_COLUMN->SET_LONG_TEXT( 'First Name' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'First Name' ).
        GR_COLUMN->SET_SHORT_TEXT( 'F. Name' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'NACHN' ).
        GR_COLUMN->SET_LONG_TEXT( 'Last Name' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Last Name' ).
        GR_COLUMN->SET_SHORT_TEXT( 'L. Name' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LIC_TYPE' ).
        GR_COLUMN->SET_LONG_TEXT( 'License Type' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License Type' ).
        GR_COLUMN->SET_SHORT_TEXT( 'License' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'FUNCTION' ).
        GR_COLUMN->SET_LONG_TEXT( 'Job Description' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Job Descr' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Job Desc' ).
        GR_COLUMN->SET_ALIGNMENT( RIGHT_ALIGNED ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'GLTGB' ).
        GR_COLUMN->SET_LONG_TEXT( 'Term Date' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Term Date' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Term' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'USTYP' ).
        GR_COLUMN->SET_LONG_TEXT( 'License Type' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License Type' ).
        GR_COLUMN->SET_SHORT_TEXT( 'License' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'CLASS' ).
        GR_COLUMN->SET_LONG_TEXT( 'Class' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Class' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Class' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'UFLAG' ).
        GR_COLUMN->SET_LONG_TEXT( 'Login Staus' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Login Staus' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Login OK' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'PWDSTATE' ).
        GR_COLUMN->SET_LONG_TEXT( 'Password Status' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Pswd Status' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Pswd OK' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'USRID' ).
        GR_COLUMN->SET_LONG_TEXT( 'Employee Login' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Empl Login' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Empl.' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'PERNR' ).
        GR_COLUMN->SET_LONG_TEXT( 'Employee Number' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'Employee#' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Empl#' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LICENSE_AX' ).
        GR_COLUMN->SET_LONG_TEXT( 'License AX' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License AX' ).
        GR_COLUMN->SET_SHORT_TEXT( 'AX' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LICENSE_AY' ).
        GR_COLUMN->SET_LONG_TEXT( 'License AY' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License AY' ).
        GR_COLUMN->SET_SHORT_TEXT( 'AY' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LICENSE_AZ' ).
        GR_COLUMN->SET_LONG_TEXT( 'License AZ' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License AZ' ).
        GR_COLUMN->SET_SHORT_TEXT( 'AZ' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LICENSE_BA' ).
        GR_COLUMN->SET_LONG_TEXT( 'License BA' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License BA' ).
        GR_COLUMN->SET_SHORT_TEXT( 'BA' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LICENSE_BK' ).
        GR_COLUMN->SET_LONG_TEXT( 'License BK' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License BK' ).
        GR_COLUMN->SET_SHORT_TEXT( 'BK' ).
        GR_COLUMN ?= GR_COLUMNS->GET_COLUMN( COLUMNNAME = 'LICENSE_OT' ).
        GR_COLUMN->SET_LONG_TEXT( 'License Other' ).
        GR_COLUMN->SET_MEDIUM_TEXT( 'License Other' ).
        GR_COLUMN->SET_SHORT_TEXT( 'Other' ).
        GR_LAYOUT = GR_ALV->GET_LAYOUT( ).
        KEY-REPORT = SY-REPID.
        GR_LAYOUT->SET_KEY( KEY ).
        GR_LAYOUT->SET_SAVE_RESTRICTION( CL_SALV_LAYOUT=>RESTRICT_NONE ).
        IF NOT P_VARI IS INITIAL.
          GR_LAYOUT->SET_INITIAL_LAYOUT( VALUE = P_VARI   ).
        ENDIF.
        GR_ALV->DISPLAY( ).
      CATCH CX_SALV_NOT_FOUND.
      CATCH CX_SALV_MSG.
    ENDTRY.
ENDIF.

User Change Log - "Defaults" Tab

I know that via SU01 you can run RSUSR100 to see the user changes logs. The issue we're having is that a user has changed their printer (Output Device) and we're trying to determine who changed it and when. Is there a change log for this information? We'd also like to have change log information for the User Parameters data as well.
Does any know if this information is contained in any table, change log, report, etc.?

Hello Bernard,
The following has been extracted from help.sap.com which has explained the objects for archiving change documents.
User master records and authorizations are stored in the USR* tables. You can reduce the amount of space that these take up in the database by using the archiving function. Change documents are stored in the USH* tables. The archiving function deletes change documents that are no longer required from the USR* tables.
You can archive the following change documents relating to user master records and authorizations from the USH* tables:
●      Changes to authorizations (archiving object US_AUTH)
●      Changes to authorization profiles (archiving object US_PROF)
●      Changes to the authorizations assigned to a user (archiving object US_USER)
●      Changes to a useru2019s password or to defaults stored in the user master record (archiving object US_PASS)
The last point also mentions changes to "defaults" stored in the user master record which makes me think that they may be getting stored in one of the tables.

Change Logs for TCODE -- FILE

Hi Friends,
    Please help me in finding the change logs for the TCODE FILE,
    i.e The changes made to the Logical paths
   I had tried Utilities---->change logs , but unfortunately i cannot find any changes logs
   But there are changes made to the logical paths in my system but i cannot see them in change logs
thanks
chandrasekhar j

rec/client is a profile parameter, you can view the settings in transaction RZ10. However I find program RSPARAM more useful, the report lists all system parameters with their default and altered value. Also if you double-click on a parameter you can get to the full help text for its meaning.
The parameter essentially switches on table change logging for configuration tables (based on the technical settings of the table) and has to be set before the changes are made.
Hope this helps.
Nick

Change Log Data from DSO to CUBE

Hi Experts,
Is it possible to load/transfer change log data as well from DSO to Cube
Thanks

Hi,
Yes it is possible.
Create a DTP from DSO to cube.
In the extraction tab of DTP choose the option
Datasource Change log
Hope it Helps!!
Reward if useful
Manish

Filled fields become blank in DSO change log

Hi experts,
I find an unusual behavior in DSO activation.
For some records for which I find in PSA, new data table (and in debug also!!!) correct data, when the request is activated I find in change log table all characteristic fields empty; the key fields and key figure fields are ok and correct in all tables.
It happen randomly for some orders and for a few requests.
It happen when I have one storno record, for example:
PSA (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, , 25
10000, 10, AAA, YYY, X, -25
DEBUG (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, , 25
10000, 10, AAA, YYY, X, -25
CHANGE LOG (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, , 25
10000, 10, , , X, -25
ACTIVE DATA (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, 25
In some other cases:
ACTIVE DATA (order, item, customer, material, storno, quantity)
10000, 10, , , -25
Have you some ideas? It is very strange.
We are on a 7.0 BW system, but with 3.5 data flow (update rule).
Thanks in advance.

Vito,
This happens some times...
1. Did you transport any change to this DSO where characteristics were added and are these the ones that are blank...
When this happens - see if you can clear the change log ( if this is an option ) and then reactivate the cube.
Also there is a program to regenerate the activation program, I am not able to locate this - but then usually reactivating the ODS will usually clear this issue because it regenerates the activation program.

Need suggestion to get data from change log table of ODS.

Hello,
There is a case where i am loading opportunity header data from header ODS and opportunity item data from item ODS in the opportunity cube.
Status (1= OPEN, 2= WON ETC) of the opportunity are available only in header ODS and not in item ODS.
While loading data from header ODS to cube, I am loading it directly but while loading data from item ODS to cube i am using active data table of header ODS as a lookup in the update rule from item ODS to cube. I am selecting status from the active data table of header ODS while loading data from item ODS to cube.
Since active data table will have only after image records, there is some data mismatch in the report as i am selecting data from active data table of header ODS while loading data from item ODS to cube.
I need to select data from Change log in order to get before image also instead of active data table in order to overcome this issue. Is there any way by which i can do selection from Change log instead of active data table as change logs are generated at run time.
Please let me know if you have any suggestions.
Regards,
Sanjay Chaurasia.

Hi,
You can use the changelog table of the DSO.
Right click manage the Header DSO, go to the contents tab and click Change Log table. There you can see the technical name of the Change Log table.
In the update rule Routine, give the tech name of Change log table instead of Active table name.
Hope it helps.
Krishna

Sales Orders Change Log question

Hi All,
I am currently working on a project that involves querying SAP Database to get custom reports via web browser, I've made a lot of advances and most of the site is ready but I'm missing just one item that I hope you could help me.
Thing is I am working with the Sales Order change log and the problem comes one a user deletes a row. If I go to the change log inside SAP and see the differences a new record will be shown saying that row X was deleted and
if I go to the database (ADOC and ADO1 tables) I don't have a way to see wich row was deleted.
My way of doing this is to check for the number of rows on the current state of the sales order and check the same on the previous instance of the SO and see if a line was deleted. Then I would have to check row by row between instances what rows are there and what row is missing and store that info. I think this kind of approach will definitively kill the server.
I was wondering if some one can give me a hint about how to approach this problem. Does any body know how SAP works on this area?
I'm working with SAP2005A and SQL Server 2005 Standard Edition.
Any help is greatly appreciated.
Thanks!
Alejandro.-

Hola Alejandro,
Thanks for your answer, as I see it I'm doing exactly what you proposed but the problem comes with the following scenarios:
a.- If I post a new SO with two lines I will have on the ADO1 table two records with the values 0 and 1 for each line respectively but if I delete the item on LineNum = 1 and then I add a new item, this last item will be also created with LineNum value = 1. This is not a complicated thing to do but the problem comes when the user is used to work with SOs with several items at detail level and is used to add and erase lines once in a while and as I see it it's very difficult for me to track those specific changes. There's also the fact that on the Log table a new instance is created every time the user hits the update button regardless if a modification was actually made or not. I mean I would know that a line was deleted or added but I would have to start comparing each field on each line of a sales order with it's previous instance to check what was actually added/deleted and I'm afraid that this may affect the server performance. I know that SAP does this without affecting to much the system resources and that is what I'm trying to find.
I forgot the other scenario I was considering he he I will post again as soon as I remember it but I hope I'm explaining this ok (I'm not very good at explaining...) If not let me know and I'll try to explain again.
I'm also working on trying to get another approach to see what comes up...
Thanks for checking this thread, your answers are helpful.
Regards.

HOW TO USE FUNCTION Deletion of Requests from the Change Log IN PRCSES CHAN

Respected all
i used Deletion of Requests from PSA from the prcess chain and found good results, now i have only one request at the psa and thus i am doing good space utililisation. but when i am using Deletion of Requests from the Change Log i am not getting any changes in the request of dso. kindly let me know how to use this 2nd function.
thanks
abhay

Hi Mahodaya,
As per SAp standards its good to delete the requestes that are no longer needed for the delta update and no longer used ffor inti from the change log table and the data is loaded already in to DSO.
Goto RSPC
Click on create New PC -> enter the PC name n long descp
Next we need to define the start process for the PC.Maintain the start variant process.save n come back.
for deletion of change log we have option in the Other BW Processes -> deletion of requestes from change log
Once u select the option we get a dialoge box here we need to create the variant for the process enter the process variant n long descp. cick ok.
Next in the maintenance screen for the deleting the request from change log table will appear.
Enter the selection patterns to which the requestes should be deleted from the change log.
In the maintenance screen, select one or more Data Store objects for which requests are to be deleted from the relevant change log tables under Data Store Object column and select theInfo Area of the corresponding Data Store Objects under Info Area
If you select the first check box exclude selction pattern, this means that del of requests from change log table will be ignored.
or
We can delete the requests which are Older than N-number of days (or) date in the above screen. For this one, enter the number of days (or) date in the filed Older than .
OR
If we want to select the requests with a certain status then we can also do in the above screen. We can select the following status indicators from the above screen.
Delete Successfully Updated Requests Only -This status will delete only requests which
are successfully updated into corresponding Data Store objects.
Delete Incorrect Requests that were not Updated - This status will delete only incorrect requests which are not successfully updated into the corresponding Data Store Objects.
Delete Activation Requests only, No Load requests- This status will delete only the activation requests (requests that begin with ODSR_... ). No load requests are deleted.

How to use the change log in ODS to track Delta change?

People say that historical data (like Delta change) in ODS can be tracked in the Change Log. How to use the change log to track historic data?
Thanks

Kevin
See if it helps
Every ODS object is represented on the database by three transparent tables:
Active data: A table containing the active data (A table)
Activation queue: For saving ODS data records that are to be updated but that have not yet been activated. The data is deleted after the records have been activated.
<b>Change log: Contains the change history for delta updating from the ODS Object into other data targets, such as ODS Objects or InfoCubes for example.</b>
An exception is the transactional ODS object, which is only made up of the active data table.
The tables containing active data are constructed according to the ODS object definition, meaning that key fields and data fields are specified when the ODS object is defined. Activation queue and change log are the same in the tables structure. They have the request ID, package ID and the record number as a key.
Data base structure changes
http://help.sap.com/saphelp_nw04/helpdata/en/d2/d53ec3efdc9b47a9502c3a4565320c/frameset.htm
Hope this helps
Thnaks
Sat

Change log issues-2 images for a single requests

Hi ,
in change log table for a single request i found 2 before images and two after images, is this normal behaviour if not when can we see the such type of scenarios.
because it leads to zero records when it isn updated in to the further data targets.
thanks.

the listener is NOT involved with any existing session.
stopping & restarting the listener has NO impact on existing sessions.
I suggest it is better to control network access to any system using a Firewall which is the best tool for this task.
Yes, it is possible to have more than 1 listener. It is also possible to poke yourself in the eye with a sharp pencil.
I suggest that you should avoid both of these possible activities.
Simply put having multiple listeners is wrong for multiple reasons & should be avoided.

Error while Changing log level in Agentry 6.0.44.1

Hi ,
I am trying to change the log level from the Agentry Administration client, but i am getting the below error message.
And it is showing any option to change the log levels for users. How can I change log level for users also.
How can I resolve this error.
Regards,
Shyam

Shyam,
This is fixed or planned fixed in 6.0.46 Agentry Server (supposed to be available anytime soon in the Service Marketplace - it was submitted already to the SMP team). The fix was in SMP 2.3 and SMP 3.0 but it was ported back to the Agentry 6.0.X release. If you have no access to the Agentry 6.0.X patches this means that your SAP License is preventing you from downloading it. You may need to contact the SAP CIC (customer interaction center) group.
Or you can do the manual setup for a workaround for now.
SAP KBA article: 2048202 - AgentryGUI does not allow to change log settings - Not all setttings were successfully changed.
Regards,
Mark Pe
SAP Senior Support Engineer (Mobility)

How to delete Change log data from a DSO?

Hello Experts,
I am trying to delete the change log data for a DSO which has some 80 Cr records in it.
I am trying to follow the standard procedure by using the process chain variant and giving the no.of days but somehow data is not getting deleted.
However the process chain is completing successfully with G state.
Please let me know if there are any other ways to delete the data.
Thanks in Advance.
Thanks & Regards,
Anil.

Hi,
Then there might something wrong at your Chang log deletion variant.
can you recreate changlog deletion variants and set them again.
Ty to check below settings with new variant.
Red mark - won't select
Provide dso name and info area, older than and select blue mark.
blue mark - it will delete only successfully loaded request which are older than N days.
Have you tested this process type changlog deletion before moving to prod per your data flow?
Thanks

A function module to add an entry to the change log of the ODS needed

Hi all,
I want to add an entry to the change log table of the ODS .
Is there a Function module available for this or a work around for this.
Regards
Akshay

Hi Kiran,
You can directly add days to the date.
Eg:
DATA date LIKE sy-datum.
DATA days TYPE i.
date = sy-datum.
days = 100.
date = date + days.
WRITE date.
Regards
Wenceslaus

How to find out the top ten Change log tables in BW

I want to know the top ten change log tables in terms of size. Do we have a SAP standard table where we have the following fields : "changlog table name", "number of records" field or "data in size" field.
Regards,
Prashant M J

Hi,
Click on change log table in the ODS/DSO at the top you see the name as /bic* which is the name of the database table which could also be seen at SE11.
If you wana see the requests in this change log use rstsodsrequest
and if you wana see the size in terms of kb, mb DB02 or st04
use the table name /bic* and click on tables and indexes option in history tab
DB02 tells you the sizes of the tables present on database. Incase you are not able to your basis team would help you in that
Thanks and regards
Kiran

Change log in SU01

Similar Messages

Maybe you are looking for