HRMD_A IDoc Problem: Is there a way to reduce its size if we use RBDMIDOC?

[Former Member]

Hi Experts,

we copied part of the org. structure and this created about 50.000 change pointers in our system. I want to send these changes to another SAP system through the ALE interface. I thought i would use RBDMIDOC for this purpose. However, i made some (smaller) tests and it seems to me that RBDMIDOC puts all changes it finds during a run into one IDoc..  Unfortunately, the packet size parameter of the partner profile does not effect how many segments are put into an IDoc .

So is there a way to force RBDMIDOC to create several IDocs each having the recommended 3-4 MB size? If this is not possible, is it better to forget the change pointers and to use PFAL to synchronize the data between the two systems?

Thanks, D.

[BK]

Hi D.

in the past we had same problem. The solution was to write 2 ABAPS:

The first moves "most" entrys from SAP change pointer tables to custom tables. Than we could run RBDMIDOC for the left entries. Afterwards the second ABAP moves "some" change pointers back from custom table to SAP table. than we run RBDMIDOC for the next an so on.

Regards

Bernd