ALE HRMD_A Idocs in status 52

Question

HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relationship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist".
We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening. Any body experinced similar problem?
Any help on this appreciated.

Answer 1

The question here is if all necessary data has been already transferred to target system . If data is selected based on change pointer than only data that has changed in source system is send to target.
Example: imagine you have change employee position using one of already created positions in the system. Change pointer will take than only the new assignment between employee and positions. It will not actually transfer the existing position it-self. In this case you must be sure that all existing positions are already transferred to target system.
In your example only new relationship between P->S is transfered to target. Employee data should already been there. The change here is not about creating new employee but only about the new relationship P->S.
Best Regards,
Andrzej