2009 Feb 16 5:34 PM
We currently have the change pointer HRMD_A turned on and it's creating the IDOCs just fine.
Now, we want to turn off the change pointer, which I did in tcode BD61 and unchecked the message type HRMD_A in tcode BD50.
But, the IDOCs are still getting generated. What else has to be done to turn off the change pointer and the creation of the IDOC's ???
2009 Feb 17 12:13 AM
Hi John,
Did you save your changes into a transportable request and client-copied (SCC1) the changes back to the client where the data is i.e. the client where the IDocs are created? You can double check this by checking BD50 & BD61 in the client where the IDocs are generated. Then, as a test, go to PA30 change some employee data (keeping in mind the infotype filter if set in IMG) then cross check with table BDCP and field CRETIME.
If you have already done this and checked as per above and the system's still creates HRMD_A IDocs (which I find it unbelievable) then you should create an OSS message with a high priority and let SAP take a look at this!
Hope this helps.
Cheers,
Sougata.
We currently have the change pointer HRMD_A turned on and it's creating the IDOCs just fine.
Now, we want to turn off the change pointer, which I did in tcode BD61 and unchecked the message type HRMD_A in tcode BD50.
But, the IDOCs are still getting generated. What else has to be done to turn off the change pointer and the creation of the IDOC's ???
2009 Feb 16 6:48 PM
2009 Feb 17 12:13 AM
Hi John,
Did you save your changes into a transportable request and client-copied (SCC1) the changes back to the client where the data is i.e. the client where the IDocs are created? You can double check this by checking BD50 & BD61 in the client where the IDocs are generated. Then, as a test, go to PA30 change some employee data (keeping in mind the infotype filter if set in IMG) then cross check with table BDCP and field CRETIME.
If you have already done this and checked as per above and the system's still creates HRMD_A IDocs (which I find it unbelievable) then you should create an OSS message with a high priority and let SAP take a look at this!
Hope this helps.
Cheers,
Sougata.