Infotype operation (Delete,Insert,Change) Log

Hello Folks,
I want to get the log of operation happend on a infotype in my Z Report.
I know that log can be seen using prog RPUAUD00.
Iam using the FM's HR_INFOTYPE_LOG_GET_LIST & HR_INFOTYPE_LOG_GET_DETAIL but this is not fetching the Operation or action happend on a infotype.
Please suggest me the way to fecth it.

solved on my own
Below is the code
REPORT yinfotypelog.
TABLES:pcl4.
INCLUDE rpcblo00.
INCLUDE rpcbsh00.
INCLUDE rpcbdt00.
PARAMETER : p_aedtm LIKE sy-datum.
DATA: t_change_list TYPE pldoc_key_tab,
w_change_item TYPE pldoc_key.
CALL FUNCTION 'HR_INFOTYPE_LOG_GET_LIST'
EXPORTING
    tclas              = 'A'
    begda              = p_aedtm
    endda              = p_aedtm
TABLES
    infty_logg_key_tab = t_change_list.
DATA: t_before TYPE prelp_tab,
t_after TYPE prelp_tab,
w_before TYPE prelp,
w_after TYPE prelp.
LOOP AT t_change_list INTO w_change_item.
lo-key-tclas = w_change_item-tclas.
lo-key-pernr = w_change_item-pernr.
lo-key-infty = w_change_item-infty.
lo-key-bdate = w_change_item-bdate.
lo-key-btime = w_change_item-btime.
lo-key-seqnr = w_change_item-seqnr.
IMPORT header belege FROM DATABASE pcl4(la) ID
    lo-key .
CALL FUNCTION 'HR_INFOTYPE_LOG_GET_DETAIL'
    EXPORTING
      logged_infotype = w_change_item
    TABLES
      infty_tab_before = t_before
      infty_tab_after = t_after.
ENDLOOP.
LOOP AT t_after INTO w_after.
CASE w_after-infty.
    WHEN '0001'.
    WHEN '0002'.
ENDCASE.
ENDLOOP.

Similar Messages

After deletion ODS change log, Delta upload OK?

Hi all,
Now I am reducing data from BW server. For this purpose, I will delete ODS change log. Both of data "from ODS" and "to ODS" are uploaded by Delta Upload.
If I delete change log after last delta initialization, is there any problem to next delta upload?
For example, the last delta initializing was done April 1. And I delete the change log up to April 30. After this operation, can be expected any problem to Delta upload?
Bamboo Shampoo

I dont think it will cause any issue with next delta loads.
Data goes from ODS to its targets from change log table.
But I think better have strategy like..'delete change log data only for requests older than say...1 month or 2 months..'
so that if u have problems with recent data loads..u can reload easily..
u can also try cleaning up old requests from the PSA tables in the system..
cheers,
Vishvesh

How to check and delete the change logs for DSO

Hello All,
I have build a process chain that will delete the change logs for DSO prior to 7 days but when i executed it, the number of entries are still the same within DSO.
Then i tried deleting directly from "Environment" menu from DSO maintainance but does not work. Can anyone please explain how to resolve this issue or the proper process of deleting the change logs. Appreciated.
Thanks,
M

Hi
Check out the below two articles
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1058b68f-96c4-2d10-fbb1-de8757ca6a58?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02ba9e7-bb6f-2c10-09b4-e86b9fcbad41?QuickLink=index&overridelayout=true
Regards,
Venkatesh

Can we delete the change log table of ods?

hi bw gurus,
can we delete the newdata,active and change log table of ods?how?what is the advantage?
OR
can we delete the contents of new,active,change log table of ods?how?what is the advantag?
thanks in advance
srinivas

Hi Srinivas
Yes, You can delete the contents of changle log table but not the contents of new data and active data table.
Before deleting the change log data you have to make sure that the requests are not required for further delta extraction or for reconstruction purpose.
Steps
1. Goto Manage screen of your ods
2. Click on Environment tab and select the option " Delete change log data".
Adv:
To free up the disk space.
Assign points if it is useful for u.
Regards
Saddy

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 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

Delete change log

HI BI Expert,
I have got the requirement to delete change log using process chain. I have included the Objecty Type callled Change Log Table and DSO as object name and finally included this process after activating data on DSO process. Whenever, I scheduled the process chain or ran it immediately as well in order to delete change log. But this process does not seem to be working at all. The number of records on change log table is the same as before.
The process chain is as follows;
1. Variant
2. load data to PSA and then DSO
3. Delete PSA data (older than 30 day)
4. Activate DSO Data
5. Delete Change Log (older than 30 day)
Please kindly suggest me what I need to do to make this process working.
Thanks for your help.

hi,
hope u can include all the PSA and change log deletion in different chain and try to trigger the chain weekly, since if u do as in ur chain and if u miss any records and you have to disturb the source again.
try to delete the change log manually and chk if working.
Ramesh

Delete change log data

I was going through posts regarding delete change-log data but I am bit confused with the answers.My data is moving from ODS to CUBE and for the performance reasons I want to delete Change-log data from PSA and keep only 3 day requests.My question - if I delete Change-log whether it effects the delta data from ODS to CUBE.Change-log maintains images so If I keep only 3 requests there will be images of only those 3 request data.If this happens then it will effect all the delta data going into CUBE
Let me know your suggessions
Rgs,

Hi,
     Yes, you can delete the data from the Change Log unless until you do not need to re-construct the data again from the change log table.
     As a good principle for safety reasons if data is not too large, you can keep the data for 7days. This will ensure us to be safe. If something went wrong on week-end say 2 days were gone and on 3rd day the user has identified and raised a ticket on this. Forth day will be for analyzing and re-construction.
    So, unless until if the data is not too large, you can keep it for 7 days in the Change log table and the rest you can delete. As said by the other members, deletion of Change Log table does not affect the delta as it compares with the Active Table and creates a Before Image and After Images records and updates in the Change Log Table.
Raj

Problem delete chang log from process chain BW 7.01

We have upgrade BW from 3.5 version to 7.01 version two month ago.
Now I realized that the process chain running one a week to delete PSA and change log don't work well after upgrade.
The process chain end without errors (status is green), but the change log are not deleted.
In the test system I try to delete the Change Log in 2 mode:
1-with the variant "Deletion of Requests from the Change Log " and the datastoreobject = myods and all the option (correct request, incorrect request and "Delete Activation Requests Only"). In the log i see this messagge
The following excluded selections will be processed:
No excluded selections found
The following included selectiosn will be processed:
Pattern: DataStore = 0FIGL_O06, InfoArea = *
The following reqeust selections were set:
Number of days = 0000000010, Successful = X, Incorrect = X, Curr. Requests =
The following change logs were selected:
2-with the variant "Deletion of Requests from PSA " and the datasource= 8myods and all the option (correct request, incorrect request). In the log i see this messagge
The following excluded selections will be processed:
No excluded selections found
The following included selectiosn will be processed:
Pattern: DS = 80FIGL_O06, LS = BWTCLNT100, IS = , AC =
The following reqeust selections were set:
Number of days = 0000000015, Successful = X, Incorrect = X, Load requests =
The following PSAs were selected:
In both case the change log is not deleted.
I can delete the change log only using Manage screen of my ods and then using Menu -> Environment ->Delete Change Log Data.
Anna Maria

I see that this topic is still active/unanswered...
We're having the same problem, but not just changelogs, also for PSAs. We have a weekly process chain that does housekeeping on our BW system, cleaning up PSAs and changelogs, compressing cubes, realigning time-dep masterdata and renewing indexes.
The PSA chain runs fine and about 90% of all PSAs get deleted, but there are some datasources (all of them are of type 8* datamart datasources) that don't get their PSAs deleted. It says "The following PSAs were selected:" and then nothing happens...
I tried all tickbox combinations and checked that there are no PSA entries blocked by invalid partitions. Manual deletion (via "manage" in the datasource) works fine, but is tedious and time consuming.
Also, most of the 8* datasource PSAs do get deleted. Just a handful (+/- 25) get skipped somehow.
Any ideas?
Thanks,
Eduard
PS: We're still running 3.5-style backend dataflow, but will eventually get converted to transformations and DTPs. But that's not on our agenda (yet).

Change Log Table entries without Dates and How to Delete these entries !!

Hello Experts,
I was analyzing Change Log tables of some DSOs and figured out in some tables we don't have Date Column and some tables with date columns but many entries with "00/00/0000" date.
Any ideas on this ? Any idea how records can get into the table without dates and if SAP provides a safe way to remove them (without dates) ?
Many Thanks in advance, Please help.
Regards,
S. Patel

Hi Sunil
Date fileds 00/00/0000 means date are blank..that means either you did not get them from source system or the transformation is not mapped.
Do not delete change log selectively, that might affect your delta loads.
Rather delete old change log ...
From DSO administration ---use the main menu to choose Environment ® Delete Change Log Data.
For more information you can check the log below.
Cheers
Anindya

Need of Change log deletion for a DSO, when DTP delta Init with Active Tabl

Hi,
Thanks for your time, please help me with the following
Scenario: I have Cube1 being updated from DSO1 with DTP delta, for quite some time. As per new requirement, I would need to create new data mart such that Cube2 gets updated from DSO1.
In order to Configure the delta, I am Considering Following options, please let me know, which one is right one.
Note: DSO1 is in Overwrite Mode.
Create one DTP with update Mode "Delta" , and "Active Table". I knew Delta Changes are captured in change log, but my understanding is, when you execute the DTP for the First time, it fetches the records from Active Table. And from 2nd Run onwards the very "same DTP" without "any changes" get the records from change log, even if we choose "Active Table".
is my understanding is Right?
Do I have to consider deleting the change log, because DSO1 is in Production from quite some time which is in Overwrite mode?
Do I have to create a DTP with Delta and Active Table, run the dtp Once(Init), then choose "Change Log for subsequent runs explicitly
please help me with these. I have reviewed many sap help articles and sdn threads but none of them were helpful. all of them explains, difference b/w active table and change log table, also gives scenarios like use a full DTP and then 2nd DTP with Delta without Data transfer. I am not looking for that kind of details.
Appreciate any help, Thanks again
Edited by: curious maven on Mar 28, 2011 8:35 AM

Hi Uma,
Thanks for your response.
to your question, If I need to load all the data from DSO1 to Cube1, answer is NO. if you read my post once again,
Existing Flow is : DSO1 --> Cube1 (Means, Active Table and Change Logs of DSO1 already Filled Up)
Requirement is: DSO1 --> Cube2. (Need to Init the Delta, and Detlas going forward)
My Questions:
(1) Imagine, DSO1 has 10 requests, so we see resepctive data in Active Table as well as Change Log. As a matter of fact, Data is being updated to DSO1 in Overwrite Mode, so all the changes(10 requests equivalent) would be captured in Change Log, which in turn helpful / used when we do Delta from DSO1 to any Cube, in my case, it used to update to Cube1. As per new requirement, it needs to update to Cube2.
My assumption is, if I choose "Active table and Delta in Extraction Tab" in DTP, During First Run (Delta Init), Data would be fethed from Active table. And the 2nd Run Onwards, delta records would be fetehced from Change Log automatically, even if we don't change the selection from Active Table to Change Log.
Is My Assumption Right?,
in this process, Do I have to Delete Change Log
(2) Do I have to Explicitly change DTP setting from "Active Table to Change Log" Once Delta Init has been run with setting "Active table" inorder to get Deltas from DSO1 --> Cube2 ?
Appreciate your help
Edited by: curious maven on Mar 30, 2011 3:14 PM
Edited by: curious maven on Mar 30, 2011 3:29 PM

Infotype Operation: Infotype with TABNR and HRT tables

Hi all,
Can anyone share the code for updating the infotypes and corresponding HRT tables having TABNR field for example infotype 1018 and HRT1018.
Thanks,
Shilpa

Hi,
Go through below code
The HR_INFOTYPE_OPERATION function module is used for the Maintenance of HR infotypes, such as inserting, changing, deleting data etc
Parameters Explained
Here is a list of the fm's parameters and how they are used, obviously not all parameters will be used depending on what function you are performing i.e. insert, change, delet etc
infty - Infotype being updated
objectid - object id from infotype
number - Personnel number
validityend - validity end date
validitybegin - validity begin date
record - infotype record values to be updated, inserted etc (will be structure of infortyoe you are updating)
recordnumber - sequence nunber from infotype record you are updating
Operation - describes what operation is to be performed
COP = Copy
DEL = Delete
DIS = Display
EDQ = Lock/unlock
INS = Create
LIS9 = Delimit
MOD = Change
INSS = Create for Actions is not converted to Change
nocommit - commit yes('X') / no(' ')
dialog_mode - dialog mode or not, default is '0'
Example coding for MOD operation
      CONSTANTS: change TYPE pspar-actio VALUE 'MOD'.
      "This code is requred and locks the record ready for modification
      CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
        EXPORTING
         number = p_pernr.
      "loop at p0071 into p_p0071. "added to put code in context
      validitybegin = p_record-begda.
      validityend   = p_record-endda.
      p_record-endda = pn-begda - 1.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0071'
          subtype       = p_record-subty
          objectid      = P_record-objps
          number        = p_record-pernr     "employeenumber
          validityend   = validityend
          validitybegin = validitybegin
          record        = p_record
          recordnumber = p_record-SEQNR
          operation     = change
          nocommit      = nocommit
          dialog_mode   = '0'
        IMPORTING
          return        = return_struct
          key           = personaldatakey
        EXCEPTIONS
          OTHERS        = 0.
       "endloop.
     "unlock record after modification
     CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
       EXPORTING
        number = p_pernr.
Example coding for INS operation
      CONSTANTS: insert TYPE pspar-actio VALUE 'INS'.
      "This code is requred and locks the record ready for modification
      CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
        EXPORTING
         number = p_pernr.
      validitybegin = p_record-begda.
      validityend   = p_record-endda.
      p_record-pernr = p_pernr
      p_record-begda = pn-begda.
      p_record-endda = validityend.
      p_record-subty = p_SUBTY. "subtype of new entry
      p_record-SCREF = p_SUBTY. "subtype of new entry
      "plus populate any other fields you need to update
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0071'
          subtype       = p_record-subty
          number        = p_record-pernr     "employeenumber
          validityend   = validityend
          validitybegin = validitybegin
          record        = p_record
          operation     = insert
          nocommit      = nocommit
          dialog_mode   = '0'
        IMPORTING
          return        = return_struct
          key           = personaldatakey
        EXCEPTIONS
          OTHERS        = 0.
     "unlock record after modification
     CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
       EXPORTING
        number = p_pernr.
Thanks,
venkat

RPUAUD00 Change Log Issue on Table T585B

I added some new infotypes to the RPUAUD00 change log on tables:
t585a
t585b
t585c
Everything seems to be working as expected, but I received soft errors on t585b:
"! All data fields 0006 01 will be deleted"
when I used * (all fields).
This did not happen when I used actual field names.
Does anyone know what that means?
thanks!

It's just a warning for this specific view if you put '*' in field name. What it means is that if you currently configure audit changes
for specific fields of this infotype, all of these entries will automatically be deleted by SAP when you use '*' (all fields are marked for audit). Therefore, there should not be a concern on the message.

ODS Activation Returns 0 records in the Change Log

Hi All,
I have question regarding the Change Log build after the ODS req has been activated.
BW system - SAP NetWeaver BI 7.0 - Level 15
Upon loading a delta request into the ODS and Activating, it adds no records to the change log table.But the active table gets correct records
Checks I Did
ODS -> Menu-> Environment -> Delete Change Log Data.
     No job scheduled or runing to delete the change log reqs (sm37)
RSRV - Check the Status of the Generated Program of a Data Store Object
ODS - reactivation to see if it works..
ODS Manage - Auto Req Processing set Quality status, Activate DSO to Yes.
The Activation Log shows at the end that they were no changed records added:
Data pkgs 000001; Added records 0; Changed records 0; Deleted records 0
Log for activation request ODSR_4APQQHKM459YNO7CIGCE0629U data package 000001...000001
Activation of records from DataStore object C_PUR_C sucessfully finished
U table for DataStore object C_PUR_C deleted successfully
Job finished
Can anyone help on the above issue??
Thanks
Rao

Hello Siggi,
Referring to the previous post:
I have a situation where few documents are not transferred to Change log during DSO Activation, though the After image values of these records are reflected in Active table.
I have found one common pattern for those documents which are not recorded in Change Log.
They have two pairs of After and Before image records.
First Pair like this: Eg: Overall status as the only data field.
Sales Doc     Overall Statuls   Recordmode
1001             C                      X
1001             A
Second pair:
1001            A                      X
1001            C
If we consolidate all these 4 records there seems to be no change for any data fields. Should I consider this as the standard behaviour while activating DSO - causing these records not to get recorded in change log?
Or is there any SAP Note that can make sure the change log gets populated in such case.
Hope my details are clear to you..
- Varma

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.

Infotype operation (Delete,Insert,Change) Log

Similar Messages

Maybe you are looking for