Read employee changes log

Hi,
I'm using functions HREIC_GET_LOGGED_INFTY_CHANGES and HR_INFOTYPE_LOG_GET_DETAIL
To get employee changes.
Does anyone know if these functions return the operation (Insert change or delete)?
If yes where?
Thanks,

Rémi ,
Thanks for your response.
I know this report but I want to use these functions and not write the code
Thanks,
Itzik

Similar Messages

Reading change logs

Hi All,
Is there any function module to read the change log table?. I need to read the change log of withholding tax type on a vendor. Is it possible?
The changes are stored in CDHDR I guess, but not sure if they can be read in a report and displayed.
Thanks for your help!
Regards
Veena

You can try the FM <b>CHANGE_POINTERS_READ</b>, you need to pass the object class and message type.....

The "Change Log" is grey out in Employee Master Data

Hi,
Just wonder why is the "change log" is grey out in Employee Master Data ?
How can I track the log in employee master data ?
Thanks

Hi,
Confirm that the superuser assign with pro license.
No additional authorization assign to the superuser.
Already created a new test company, created employee master data, try to update, and the "change log" still grey out.
Tried on China and US localization.
Is your side really work?
Which version?
Thanks

Read Change Logs of KP26/KP27

Hello,
How to read change logs of kp26 transaction. I am unable to view the change logs in CDHDR table. COST table contains all the information, but i need changes log history by date.
Thanks
-Always Learner

Hello Rob,
Thanks for your reply. If the changes are not available in CDHDR table, then that means that changes logs are not available for these transactions.
We are able to see all changes logs in KP26 when we select any item and click on line item on application tool bar
Could you please let me know if there is any way to capture changes logs for these transactions.
Thanks & Regards
-Always Learner

How to identify the employee who logged-in using a view in peoplesoft?

I have a View in peoplesoft, that says
SUPERVISOR_ID = ' ' somewhere in the SQL. How do I keep this dynamic so that, it will identify the employee who logs into the system and assigns that id to supervisor_id field.
I know we can use %EmployeeID in peoplecode.

Peopletools has this built in out of the box. Add field OPRID to the record and set it as key and not a listitem and Peopletools will automatically add a where clause to the view based on the current user.
After this change the view sql to join to Oprid.
If you do not want to add OPRID field you can use a dynamic view to fill the supervisorid with %employeeid.
If thid is a search record you can also use SearchInit event to set supervisorid to %employeeid.
Al lot of differt possibilities, depends one what you want to use.

Extracting HR Change Log Data to BW

Hi Guru's,
does anybody know how to extract data from the HR change log (among others, cluster table PCL4)? I found two function modules HR_INFOTYPE_LOG_GET_LIST and HR_INFOTYPE_LOG_GET_DETAIL
that should be giving the data in the correct format.
Has anybody ever used these Function modules for (delta) extraction to BW?
Or are there other ways to extract this type of data?
I already got some pointers from CSM Reddy in a previous posting:
http://help.sap.com/bp_biv170/html/Bw.htm
http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
But they don't seem to work any more.
Best regards,
Arno

Those links you gave didn't work for me . . .
I have toyed with using those function modules in the past. I was trying to solve an issue I had: With heavy customization on 0EMPLOYEE, it took forever to extract the data for that infoobject as we had more than 10 extractors . . .
I no longer have access to the BI system, but I used one of the function modules you mentioned and loaded it into a DSO. From there, I used the DSO as a filter for my 0EMPLOYEE extractors. Using some ABAP, I passed to the extractors a list of employees who had data change in the previous day and extracted all of their information (should extract all in that case to properly get the begda and endda for the master data).
It had the potential to really speed things up but I never got to finish so I've never seen it in a production environment. Hopefully this helps . . .

How to delete HR Infotype Change log

Hi,
I would like to know if there are any means to delete the HR infotype change log. I've already executed the standard program RPUDELPN to delete all the employee records every time an environment is refreshed from the production image, however both the long term and short term infotype change log can still be access. I need to remove those change logs as well to prevent unauthorized access to these confidential data.
Thanks a lot.
Francis

Thanks. However, I'd like to know if I can delete the change documents that were already logged.
My scenario is that in production environment, we have turn on the logging and change documents are already created. Now we have refresh the development environment with the production images, so I've to delete all the employee records as well as the change documents in order to prevent unauthorized access to these confidential information.
The standard program RPUDELPN already delete all the employee records but not the change documents. Where and how can I delete both the long and short term document as well?
Thanks.

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.

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.

My client current process shift amount is prorating.   Now my client requirement employee change shift (SE20321D)   to normal (NSO70012) in the mid of the month employee will get shift full amount,

Hi Experts,
Please help me to solve this two issues
I will give you clearly about my client requirement
in the current system (existing) already configured for shift allowance.
shift allowance for executive
Shift Allowance Rates
2 shift
3 shift
RM 240
RM 330
shift allowance for non executive
Shift Allowance Rates
Category 1
Category 2
2 shift
3 shift
2 shift
3 shift
RM 180
RM 280
RM 95
RM 130
they are not maintained (there is no any key)   in info type 0014 or info type 0015 they earliest hr consultant copied to the Shift Allowance wage types :- 5533, 5534,5535,5536,5537,5538and 5559
Note : 5533 & 5536 are for Payment.
Other wage types are for calculation purposes only.
And they modified (standard LAP9) YAP9 (copied) schema written pcr for shift allowance
The pcrs are YSH1,YSH2,YSH3,YSH4,YSH5,YSH6,YSH7,YSH8,AND YSHF
1) So my actual my client requirement (Issue 1)
    In my client current process shift amount is prorating.   Now my client requirement employee change shift (SE20321D)   to normal (NSO70012) in the mid of the month
employee will get shift full amount
2) client requirement (Issue 2)     Shift Allowance become prorate if the Action (Info type 0000) in the same month have changes. (Depand the action type)
Actions are
WA,WB,WC,WD,WE,WF,WG,WH,WI,WJ,WK,WL,WM,WN,WO,WP
XO,X1,X2,X3,X4,X5,X6,X7,X8,X9.
XA,XB,XC,XD,XE,XF,XG,XH,XI,XJ,XK,XL,XM,XN,XP,XQ,XR,XS,XT,XW,XX,XY,XZ.
Y0,Y1,Y2,Y3,Y4,Y5,Y6,Y7
YA,YB,YC,YD,YE,YF,YG,YH,YI,YJ,YK,YL,YM,YN,YP,YQ,YU,YV,YW,YX,YY,YZ
Z9,ZY
Example
in same month employee changed action on 20.07.2014
Kindly help me to solve this issues feel very happy for your help.and if you need any information about issue please let me know i will share to you.
Thank you
Raamarao

Try this, it works very well for me.
import XMonad.Hooks.ManageHelpers (composeOne, isFullscreen, isDialog, doFullFloat, doCenterFloat)
myManageHook = composeAll. concat $
[ [ className =? c --> doCenterFloat| c <- floats]
, [ resource =? r --> doIgnore | r <- ignore]
, [ resource =? "gecko" --> doF (W.shift "net") ]
, [ isFullscreen --> doFullFloat]
, [ isDialog --> doCenterFloat]]
where floats = ["sdlpal", "MPlayer", "Gimp", "qemu-system-x86_64", "Gnome-typing-monitor", "Vlc", "Dia", "DDMS", "Audacious", "Wine"]
ignore = []
myLayout = tall ||| Mirror tall||| Full ||| tab ||| float
where
tall = named "Tall" $ limitWindows 4 $ minimize $ Tall 1 (3/100) (1/2)
tab = named "Tab" simpleTabbedBottom
float = named "Float" simpleFloat
main = do
myStatusBarPipe <- spawnPipe myBar
conkyBarProc <- spawnPipe conkyBar
trayproc <- spawnPipe myTrayer
xmonad $ ewmh $ withUrgencyHook NoUrgencyHook $ defaultConfig {
terminal = "urxvt"
, manageHook = manageDocks <+> myManageHook <+> manageHook defaultConfig
Last edited by helloworld1 (2012-08-14 05:20:56)

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.

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)

Change logs not working for manual update modify/delete statements.

Hi experts,
                 My requirement is to display the change logs for a few custom z tables.The log data changes is selected in technical settings of the table.When any changes are made to the table using sm30 the changes are logged.
My requirement also displays an alv grid which allows the users to edit/insert/delete   entries in the table.
In this case the change logs are not getting recorded(ie whenever the user manually updates or inserts a row into the table the change docs are not getting stored).
My code works like this,
Whenever the user chooses a custom table and selects the display change log button i transter the control of my abap program to the standard rsvtprot program(sap std. pgm to display change logs).
sample code:
elseif sscrfields-ucomm eq c_chgdoc.
    refresh:r_seltab.
    clear:r_seltab.
    r_seltab-sign   = 'I'.
    r_seltab-option = 'EQ'.
    r_seltab-low      = w_tab.
    append r_seltab.
Call the sap standard program rsvtprot via selection screen
by passing the table name and display grid parameters.
    submit rsvtprot via selection-screen
                      with cusobj   in r_seltab
                      with alv_grid eq c_x
                      and return.
Is there any way by which i can extend the change logs functionality for the changes made using the alv grid?
Please help me out.

Hi Anuraag,
In TM you should open the transaction /SCMTMS/ZONE. Here you select the zone you would like to modify and you execute the changes you would like to make.
Regards,
Nico.

Read employee changes log

Similar Messages

Maybe you are looking for