Issue in change pointers

Hi ,
i am working on change pointers on ALE & IDOCs , i have created message type zitemxxxx,using bd52 ,i have activated using BD61 tcode,
i am using one BADI using some condition in that badi if mara related fields only we have to update ,remaining fields we need to delete.
i put break point on that badi --
ZBDCP_BEF_WRITE_IS (Implementation) ,class name ZCL_IM_BDCP_BEF_WRITE_IS when i run the tcode mm42 ,if u change some fields the change want to update in cdhdr table ,my issue is if i run the tcode and i have done the changes this badi is not triggering it is going to trigger another badi BADI_ARTICLE_REF_RT and the table cdhdr is not updating.
finally it is not trigger my badi where i have put my break point it is triggering another badi BADI_ARTICLE_REF_RT
please help me....
Regards,
Ram

sorry i dont have that badi in my system even tho i got ECC 6.0.
But i cant help it to think that BADI_ARTICLE_REF_RT somehow sound like RETAIL. *pointing to the "_RT" suffix.

Similar Messages

Change Pointers Issue

Hi
Pls any body can give me step by step settings to save the changes to the DB tables(Change Log)
I am trying to read change pointers for a 1) FAGL_011PC table.But when ever i change the data using T Code FSE2 the data is saving in this table but the changes are not getting saved in CDHDR/CDPOS.
Chagne Log Check Box in tech Settings I Activated.
What shouls i Do ?
Thanks in Advance
PREETI Raj

Hi,
Change pointers is the one of the IDOC processing method in ALE.
In this once we make the config to any of messages type , if any changes are made in sending system then IDOC will be posted directly to destination with user interation.
Changes pointers are configured using BD50,BD51,BD53,BD61.
Change pointers are stored in tables BDCP and BDCPS (or BDCP2 in case of high-performance setting) - like CDHDR and CDPOS for change documents (but this is not a controlling table!).
1. Do you really need change pointers?
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61.
2. Do you really need to activate change pointers for this messages type?
If some messages types are no longer to be distributed by change pointers, you can
deactivate change pointers for this message type.
You can deactivate change pointers for the message type
and reactivate them again in transaction BD50.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
Applications which write change documents will also try to write change pointers for ALE operations. These are log entries to remember all modified data records relevant for ALE.
Most applications write change documents. These are primarily log entries in the
tables CDHDR and CDPOS.
Change documents remember the modified fields made to the database by an
application. They also remember the user name and the time when the modification
took place.
The decision whether a field modification is relevant for a change document is
triggered by a flag of the modified fields data element. You can set the flag with
SE11 by modifying the data element.
For the purpose of distributing data via ALE to other systems, you may want to
choose other fields, which shall be regarded relevant for triggering a distribution.
Therefore R/3 introduced the concept of change pointers, which are nothing else
than a second log file specially designed for writing the change pointers which are
meant to trigger IDoc distribution via ALE.
So the change pointers will remember the key of the document every time when a
relevant field has changed.
Change pointers are then evaluated by an ABAP which calls the IDoc creation, for
every modified document found in the change pointers.
The Change pointers are written from the routine CHANGEDOCUMENT_CLOSE
when saving the generated change document. So change pointers are automatically
written when a relevant document changes.
The following function is called from within CHANGEDOCUMENT_CLOSE in order to write the change pointers.
CALL FUNCTION 'CHANGE_POINTERS_CREATE'
EXPORTING
change_document_header = cdhdr
TABLES
change_document_position = ins_cdpos.
Activation of change pointer update :
Change pointers are log entries to table BDCP which are written every time a transaction modifies certain fields. The change pointers are designed for ALE distribution and written by the function CHANGE_DOCUMENT_CLOSE.
Change pointers are written for use with ALE. There are ABAPs like RBDMIDOC
which can read the change pointers and trigger an IDoc for ALE distribution.
The change pointers are mainly the same as change documents. They however can
be set up differently, so fields which trigger change documents are not necessarily
the same that cause change pointers to be written.
In order to work with change pointers there are two steps to be performed
1) Turn on change pointer update generally
2) Decide which message types shall be included for change pointer update
R3 allows to activate or deactivate the change pointer update. For this purpose it
maintains a table TBDA1. The decision whether the change pointer update is active
is done with a Function Ale_Component_Check
This check does nothing else than to check, if this table has an entry or not. If there is an entry in TBDA1, the ALE change pointers are generally active. If this table is empty, change pointers are turned off for everybody and everything, regardless of the other settings.
The two points read like you had the choice between turning it on generally or
selectively. This is not the case: you always turn them on selectively. The switch to
turn on generally is meant to activate or deactivate the whole mechanism.
The change pointers which have not been processed yet, can be read with a function
module.
Call Function 'CHANGE_POINTERS_READ'
The ABAP RBDMIDOC will process all open change pointers and distribute the
matching IDocs.
When you want to send out an IDoc unconditionally every time a transaction
updates, you better use the workflow from the change documents.
Regards,
Shiva Kumar

Change Pointers not being created for HR-PA Custom Infotype

Problem Description:
We have a custom Infotype in SAP to store the data for contingent employee - Infotype 9001. Change pointers is
turned on. We are running the program RBDMIDOC to send changes to Oracle IDM using message HRMD_A. The change
detected for all infotypes except 9001. For 9001, the change pointer is not created.
The following are the current configuration details:
IDOC Extension Created to Idoc type HRMD_A07 (ZHR_EXT)
custom segment zhr_seg
Change pointers are switched on.
Change pointers switched on for message Type HRMD_A.
IDOC configuration created for Port / Process code etc.
Maintenance of view T777D - Added ZHR_SEG.
If I add the segment ZHR_SEG as a 2nd segment to Infotype 0000, I dont get a syntax error. But the changes for Infotype 9001 are not picked up.
If I add the segment ZHR_SEG as a segment to Infotype 9001, I get a syntax error - check EDI: Syntax error in IDoc (mandatory segment missing) below.
EDI: Syntax error in IDoc (mandatory segment missing)
Message no. E0072
Diagnosis
The segment ZHR9001 has the attribute 'Mandatory' in the syntax description of the basic type HRMD_A07 (customer enhancement ZHR_EXT). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.
Procedure
Please check the IDoc or the syntax description of the basic type HRMD_A07 (customer enhancement ZHR_EXT).

Were you able to resolve the issue?
If yes, could you please share what was done to resolve it.
Your help will be greatly appreciated.

Change pointers in case of purcahse order

The scenario is to send data through idoc when i create/change delete certain fields in purchase order.
I hace used change pointer scenario for it
can u plz see what i have missed out in my configuration ..
Here are the steps i followed .
1) created a logical custom message us we81 .
2) created custom idoc using we 30
3) Linked custom mesage and idoc using we 82
4) Activated my custom message using bd50 .
5) Assigned fields to message using bd52 ie
Einkbeleg EKKO waers , EKPO-netpr ..etc
6) Assigned cutom message and custom function module
(z...smd_custommsg) via bd60
7) tried to execute the message using BD21 ..
Now the issue is that entries are being created in change document table(cdhrd/cdpos)
but no entry in BDCP/BDCPS..
please give your valuable inputs to it
Thanks In advance

hi,
You can acheive this by writing a custom program.
in the program you need to use function module 'CHANGE_POINTERS_READ' for reading the change pointers.
Give document object class as the object name in bd52 and give read_not_processed_pointers as 'X'.
Looping at the output table and using function module CHANGE_POINTERS_CREATE_DIRECT you can create an entry in bdcp table for the respective purchase order.
After this you can use SUBMIT rbdmidoc WITH mestyp = message_type AND RETURN.
Regards
Sridevi S

Issues in changing Sales Order - ECC6.0

Hi All,
We are facing an issue when we try to change a Sales Order for which Delivery has been created.
When a Sales Order is opened for change, we see that the Net Value and Tax fields in the Item Conditions is blanked out. This does not happen when the Sales Order is opened for Display.
Again, there is no issue when we try to change a Sales Order which does not have any subsequent documents created for it.
Has anyone come across such an issue?
Any pointers in resolving this issue will be highly helpful.
Thank you.
Regards,
Keerthi

Hi,
Sorry, my earlier evaluation turned out to be wrong and the reason for the issue was that we had activated a Userexit which was triggering the redetermination of Pricing, which sort of became the reason for the issue .
I managed to handle this scenario in the Userexit and resolve the problem.
But I am still facing the same issue at a different place now - whenever I try to change anything at the line item level (for instance, PLATFORM in the Additional Data 'B' tab of Sales Order Item), I see that the Function Module 'PRICING' is getting called inside the program SAPFV45P. This function module, again, somehow screws up my already determined prices and tax values for that particular item.
Any suggestions/recommendations on how we can control whether this function module gets called or not in SAP?
Thanks in advance.
Regards,
Keerthi

Change pointers not being generated in case of Z fields (extension IDOC)

Hello,
My requirement is of generating change pointers when fields from customer master change ( z fields).
Actually this is working for standard fields, but not for z fields .
I have created a Z segment and added fields 'ADRC-STR_SUPPL3' & 'ADR3-FAX_NUMBER' and have written appropriate code for populating them in 'ZXVSVU01' of exit 'EXIT_SAPLVV01_001' .
However, when I try to run change pointers transaction BD21, it says 0 idocs and 0 communication params generated.I have added those fields properly in BD52 (object class - ADDRESSE).
If you change standard fields along with Z fields, it works, but if you change only the Z fields , it doesn't trigger a change pointer.
Is there something extra that we need to do in case of object class 'ADRESSE' ?
Please help.
Thanks,
Rachna.

Were you able to resolve the issue?
If yes, could you please share what was done to resolve it.
Your help will be greatly appreciated.

0CML_DELTA : Change pointers are not active

Hi All,
I have successfully did the delta init without data transfer for datasource 0CML_DELTA and 0CML_DELTA_CAP. Now, While trying to load delta, I am getting an error "Change pointers are not active" for both the datasource 0CML_DELTA and 0CML_DELTA_CAP.
The position datasources are fecthing 0 records.
I have activated the change pointers in BD61, even though I am getting the same error.
Anyone faced the similar issue or have any clue about the problem.
Thanks in advance,
Pravender
Edited by: Pravender on Sep 30, 2010 11:09 AM

I resolved it. I was activating change pointers in BD61. But fot CML we need to activate in SPRO--> SAP Banking --> Loans Management --> Basic settings --> Installation parameters ---> Define general installation parameters.
Then it will work.
Pravender

Reg change pointers

Hi All,
For transactional data the changes are not appearing in the BDCP table.
Currently the requirement is for KAKO and KAKT tables this is not getting reflecting in bdcp after doing all config's.
I tried to find out a badi for this but didnt get worked out.
Please let me know if any body who has worked on transactional data change pointer's how to proceed for this type of issues.
Tcode:cnr2 which i tried to change few fields in the tcode for the tables
CRHD
CRCA
CRCO
CRTX
Currently i checked with KAKO and KAKT table for the change document object class but it does not exist so iam going to go for custom i have created custom also then to changes are not reflecting in BDCP.
Please let me know if any body has a solution.
Thanks & Regards,
Mahesh

HI all..
I was looking, and really "change pointers" only can be used to master data.
Check this .
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/frameset.htm
Regards.

ALE/IDOC-How to create Change Pointers for Custom Infotype

Hi,
My requirement is to transfer custom OM infotype changes using IDOCs.
But its not creating any change pointers for that infotype.
The message used is a copy of standard message OM_HRMD_A.
Can any one please help me out in this issue.
Thanks,
Sarika

Hi Sarika,
How did you solve this issue? We are also facing a similar problem, it will be helpful if you could explain how you found out the solution.
Thanks
Anu.

BATMAS IDocs not gettting generated using Change Pointers

Hi,
I have scenario where I am supposed to replicate Batch between R/3 & Ware House Systems. So, for this I am using the standard BAPI to generate IDocs correctly for the batch.
Now, when I go and change the document flow i.e. make changes to the Batch using transaction MSC2N and saving a new document is getting generated.
Change Pointers are active globally and also on the message type. Now when I use the transaction BD21 to generate IDocs, they are getting created successfully for the distribution model that is existing. Now, when I add a filter in my distribution model based on Plant IDocs are not getting generated.
Can any one let me know if I missed out any configuration step or else what needs to be done in order to solve this issue.
Raghuram.

Is this thread still valid? If not, please close the thread.
If so, as no response has been submitted, please rephrase your question and/or provide further information to describe your requirement.
Thanks
Jason
SDN SRM Moderator Team

Deletion change pointers are not going to ECC after C5

Hi,
My issue is that I am running C5 after Planning run.But deletion change pointers are not going to ECC.Because of this we have duplicate of orders in ECC.We are running CCR to bring back the "Planned orders with deletion change pointers and deleting again using RRP4.Why deletion change pointers are not going along with creation change pointer?Help will be highly appreciated.
Thanks&Regards
Venkadesh

Hi,
Check whether you have enabled the " delete events" check box. This check box will be valid if you are publishing the planning results thru background job.
If you set this indicator, the system deletes all selected change pointers without sending them first.
Thanks,
nandha

Use change pointers to send complete employee in HRMD_A

Hi
I need to distribute employee data from my SAP system. I want to send a Idoc every time a record in PA30 is changed. But know it only sends out a IDoc with the infotype that is changed, I need to distribute all infotype's.
Example: One person is changed in infotype IT0002. I need to send out not only IT0002 but also IT0006 and IT0008.
Is there a way to solve this?
Best Regards,
Morten

Hello Morten,
Yes, you can do it. I have done same thing in one of my interface. You need to write code into BADI.
BADI : BDCP_BEFORE_WRITE
Method : FILTER_BDCPV_BEFORE_WRITE
Basic idea is to populate internal table change_pointers with remaining infotype details.
Refer following code for reference....
BADI implemented in order to send customised data as
maintained in the distribution mdoel
METHOD if_ex_bdcp_before_write~filter_bdcpv_before_write.
Type Declaration
TYPES : BEGIN OF ts_range,
            sign    TYPE tvarv-sign,
            option TYPE tvarv-opti,
            low     TYPE tvarv-low,
            high    TYPE tvarv-high,
          END OF ts_range.
TYPES : BEGIN OF ts_group,
            int_grp     TYPE zthr_infty_subty-int_grp,
          END OF ts_group.
Internal table
DATA:
    lt_zthr_infty_subty TYPE TABLE OF zthr_infty_subty,
    lt_dist_infty_subty TYPE TABLE OF t788u,
    lt_groups           TYPE TABLE OF ts_group.
DATA:
    lt_changed_objects TYPE TABLE OF hrobjinfty.
DATA :
    lr_infty    TYPE RANGE OF t591s-infty, " Range for infotypes
    lr_subty    TYPE RANGE OF t591s-subty. " Range for subtypes.
Work Areas
DATA:
    lw_change_pointers   TYPE bdcpv,
    lw_change_pointers1 TYPE bdcpv,
    lw_text(254)         TYPE c,
    lw_infty             TYPE ts_range,
    lw_subty             TYPE ts_range,
    lw_groups            TYPE ts_group.
DATA:
    lw_zthr_infty_subty TYPE zthr_infty_subty,   "Infotype & Subtype
    lw_zthr_infty_subty1 TYPE zthr_infty_subty,   "Infotype & Subtype
    lw_dist_infty_subty TYPE t788u.              "Infotypes
DATA:
    lw_changed_objects   TYPE hrobjinfty,
    lw_changed_objects1 TYPE hrobjinfty,
    lw_changed_objects2 TYPE hrobjinfty.
Local Variables
DATA:
    lv_tabix      TYPE sy-tabix,      " Table index
    lv_cpident    TYPE cpident,       " Change pointer no.
    lv_pernr      TYPE pa0000-pernr, " Employee Number
    lv_tabname    TYPE dd02t-tabname, " Table Name
    lv_abkrs      TYPE pa0001-abkrs, " Payroll Area
    lv_infty(4)   TYPE n.             " Infotype Number
Local Constants
CONSTANTS:
    lc_e       TYPE t591s-sprsl   VALUE 'E',
    lc_i       TYPE tvarv-sign    VALUE 'I',
    lc_x       TYPE c             VALUE 'X',
    lc_7       TYPE c             VALUE '7',
    lc_p       TYPE otype         VALUE 'P',
    lc_zhrmd   TYPE edi_mestyp    VALUE 'ZHRMD_A',
    lc_eq      TYPE tvarv-opti    VALUE 'EQ',
    lc_pa(2)   TYPE c             VALUE 'PA',
    lc_begda   TYPE sy-datum      VALUE '19000101',
    lc_02      TYPE pa0001-abkrs VALUE '02',
    lc_1000(4) TYPE n             VALUE '1000',
    lc_2000(4) TYPE n             VALUE '2000'.
Clear all local variables / internal tables / Work Areas
REFRESH : lt_groups,
            lr_infty,
            lr_subty,
            lt_changed_objects.
CLEAR : lv_tabix,
          lv_abkrs,
          lw_change_pointers,
          lw_dist_infty_subty,
          lv_tabname,
          lw_groups.
Select only otypes and infotypes from distribution model
Read change infotype / subtype data
IF NOT change_pointers[] IS INITIAL.
    LOOP AT change_pointers INTO lw_change_pointers.
      lw_changed_objects = lw_change_pointers-tabkey.
Filter CE Employee if Pay-Area not '02'          ***
      IF flt_val EQ lc_zhrmd.    " Check for CE emploeyee
        SELECT abkrs
          INTO lv_abkrs
          FROM pa0001 UP TO 1 ROWS
        WHERE pernr EQ lw_changed_objects-objid
          AND endda GE sy-datum
          AND begda LE sy-datum
          AND abkrs EQ lc_02.
        ENDSELECT.
        IF sy-subrc EQ 0.
          APPEND lw_changed_objects TO lt_changed_objects.
        ELSE.
          DELETE change_pointers.
        ENDIF.
      ELSE.
        APPEND lw_changed_objects TO lt_changed_objects.
      ENDIF.    " IF flt_val EQ lc_zhrmd.
    ENDLOOP. " LOOP AT change_pointers INTO lw_change_pointers.
    lv_cpident = lw_change_pointers-cpident.
ENDIF. "IF NOT change_pointers[] IS INITIAL.
Select only otypes and infotypes from distribution model**
Select corresponding infotypes / subtypes from table    **
ZTHR_INFTY_SUBTY to create change pointers              **
CALL FUNCTION 'RH_DISTRIBUTED_INFOTYPES'
    EXPORTING
      message_type            = flt_val
      check_model             = lc_x
    TABLES
      distributed_infty_subty = lt_dist_infty_subty.
IF NOT lt_dist_infty_subty[] IS INITIAL.
Read table ZTHR_INFTY_SUBTY
    SELECT mandt                         " Client
           mestyp                        " Message Type
           infty                         " Infotype
           subty                         " Info Subtype
           int_grp                       " Change pointer group
      INTO TABLE lt_zthr_infty_subty
      FROM zthr_infty_subty AS a
      FOR ALL ENTRIES IN lt_dist_infty_subty
      WHERE mestyp EQ flt_val
        AND infty EQ lt_dist_infty_subty-infty.
    IF sy-subrc EQ 0.
      CLEAR : lw_changed_objects.
      LOOP AT lt_changed_objects INTO lw_changed_objects.
        MOVE : lw_changed_objects TO lw_changed_objects2.
        AT NEW objid.
Read all groups belongs to infotype.
          CLEAR : lw_groups.
          REFRESH: lt_groups.
          LOOP AT lt_zthr_infty_subty INTO lw_zthr_infty_subty
                  WHERE infty = lw_changed_objects2-infty
                    AND subty = lw_changed_objects2-subty.
            lw_groups = lw_zthr_infty_subty-int_grp.
            APPEND lw_groups TO lt_groups.
          ENDLOOP. " LOOP AT lt_zthr_infty_subty INTO ....
Do not create change pointer if infotype not maintained in
table 'ZTHR_INFTY_SUBTY'.
          IF sy-subrc NE 0.
            DELETE change_pointers WHERE
                        tabkey+12(4) = lw_changed_objects2-infty
                    AND tabkey+16(4) = lw_changed_objects2-subty.
          ENDIF. " IF sy-subrc NE 0.
Read all infotypes belongs to all above groups.
          LOOP AT lt_groups INTO lw_groups.
            LOOP AT lt_zthr_infty_subty INTO lw_zthr_infty_subty
                          WHERE int_grp EQ lw_groups-int_grp.
Check if change pointer already present
              READ TABLE lt_changed_objects INTO lw_changed_objects1
                  WITH KEY infty = lw_zthr_infty_subty-infty
                           subty = lw_zthr_infty_subty-subty.
              IF sy-subrc NE 0.
Check if data exist for infotype / subtype
                IF lw_changed_objects-otype EQ lc_p.
                  CONCATENATE : lc_pa lw_zthr_infty_subty-infty
                         INTO   lv_tabname.
                  SELECT SINGLE pernr
                    INTO lv_pernr
                    FROM (lv_tabname)
                   WHERE subty EQ lw_zthr_infty_subty-subty
                     AND pernr EQ lw_changed_objects2-objid.
                  IF sy-subrc EQ 0.    " Change pointer for employee
Create change pointer for infotype / subtype combination
                    ADD 1 TO lv_cpident.
                    lw_change_pointers-cpident      = lv_cpident.
            lw_change_pointers-tabkey+12(4) = lw_zthr_infty_subty-infty.
            lw_change_pointers-tabkey+16(4) = lw_zthr_infty_subty-subty.
                    lw_change_pointers-tabkey+20(8) = lc_begda.
                    APPEND lw_change_pointers TO change_pointers.
                  ENDIF. " IF sy-subrc EQ 0.
                ELSE.
Create change pointer for Org Data
                  ADD 1 TO lv_cpident.
                  lw_change_pointers-cpident      = lv_cpident.
            lw_change_pointers-tabkey+12(4) = lw_zthr_infty_subty-infty.
            lw_change_pointers-tabkey+16(4) = lw_zthr_infty_subty-subty.
                  lw_change_pointers-tabkey+20(8) = lc_begda.
                  APPEND lw_change_pointers TO change_pointers.
                ENDIF. " IF lw_changed_objects-objtyp EQ lc_p.
              ENDIF. " IF sy-sybrc NE 0.
            ENDLOOP. " LOOP AT lt_zthr_infty_subty INTO..
          ENDLOOP. " LOOP AT lt_groups INTO lw_groups.
        ENDAT. " AT NEW objid.
      ENDLOOP. " LOOP AT lt_changed_objects INTO lw_changed_objects.
    ENDIF. " IF sy-subrc EQ 0.
ENDIF. " IF NOT lt_dist_infty_subty[] IS INITIAL.
ENDMETHOD.
But make sure you maintained remaining infotypes in distribution model. I have created table zthr_infty_subty twhere I am keeping track of all infotype and subtype for which I have to send a data.. You can hardcode values in u r program if you want / if you know the all infotype for which you have to send data.
if you still have any doubt / issues let me know your email id will mail you badi-code.
Cheers,
Nilesh

Reprocessing change pointers for MATMAS idoc

Hi
I have a situation where i executed BD21 for changes to materials but no idocs were created due to some issue with the distribution model. Now i have fixed the issue and would like to re process all the materials which were changed. Since i have already executed BD21, now no new idocs are being generated. Is there a way to reprocess the changed materials and generate the idocs again.
Thanks
Nag

Hi Roger
Thanks for your inputs. I am trying to generate idocs through the change pointers and not using output determination.
When i executed BD21 the first time, idocs were not generated due to some config issues. But the job ended successfully saying that idocs were generated and marked all the changed material documents under change pointers (But in WE02, the idocs never showed up actually).
Now i have fixed the issue in config and want to generate the idocs using the change pointers. Is there any way to regenerate the same idocs using BD21 or some alternative.
Thanks
Nag

Regarding change pointers in CDHDR table.

Hi All
Can we write change pointers in CDHDR table when we change the status of the project (CJ20n).
When I change the status of the project then status of the network is also changed.
Now my requirement is , as soon as the status of the network is changed ,entry should be recorded in to CDHDR.
I am able to record the changes when description or other things of the nework are changed but facing problem for status change.
Can we achieve this if yes then how ?

Hi Pranay,
Could you please let me know how you could able to resolve this issue? i am facing same kind of problem
Regards,
M, Manohar

HR Infotype change pointers

Hi Friends,
I have been trying to find how to activate the infotype change pointers and I could not find any helpful thread in this forum, in my case the program RPUAUD00 does not return any change logs.
Could someone please tell me how to activate the change logs for all the HR infotypes?
Thanks,
Muktar

OMG it's weird!
I guess maybe you miss some steps in configurations.
Please refer link blow: Re: Report for logged changes in infotype data
and http://sap.ittoolbox.com/groups/technical-functional/sap-hr/infotype-audit-log-2322026
Hope you can solve your issue soon, because it's really important report
Good Luck!
Woody.

Issue in change pointers

Similar Messages

Maybe you are looking for