10-17-2006 6:48 PM
BACKGROUND
Our current SAP setup includes separate HR and FI Systems. When master data is maintained in HR, this is picked up by the change pointers, and IDocs for message type HRMD_A are ALE'd to the FI System where they're posted. This works just fine.
We're now planning to implement a third party HR Master Data Management system that will send IDocs to the HR system. When these inbound IDocs are posted in the HR system, we also need this to trigger the creation of outbound IDocs to be sent to the FI System (as if the data had been manually created directly in the HR system).
THE PROBLEM
In my testing with tcode WE19, I'm able to successfully post IDocs in the HR System for HRMD_A06, but it doesn't trigger the creation of outbound IDocs (for the FI System). Running the change pointer program RBDMIDOC for message type HRMD_A doesn't pick up anything. (However, if I manually maintain HR data via PA30/PA40, these changes are picked up by program RBDMIDOC.)
Any suggestions would be greatly appreciated!
05-17-2007 3:59 PM
We're having this exact same issue - change pointers are being created through normal maintenance, however not when we process inbound idocs.
any help out there?
05-21-2007 7:18 PM
06-25-2008 3:05 PM
HI brother,
The process what you have asked is impossible in idocs up to my knowledge.
because sap change pointers is a different concept.
just try to do it in a manual way.
06-25-2008 4:09 PM
Hi there,
the problem is in function RH_INFTY_CHANGE_PROT.
Check out this line:
* write change pointers only in dialog, not in ALE inbound process
CALL FUNCTION 'RHAP_ALE_FLG_GET'
IMPORTING
ale_flg = ale_inbound_active.
CHECK ale_inbound_active IS INITIAL.
Maybe you can extend HRMD_A using customer segments and trigger change pointers (by calling RH_INFTY_CHANGE_PROT_HRMD) modifcation by standard exits.
Or you can simply write a little abap program which reads processed inbound idocs after RBDMIDOC run and sets the Change Pointer flag.
Hope this helps,
Roby.