iDoc delta loads using the program RBDMIDOC

[Former Member]

Hi ALL,

We are doing some delta loads for ALE-IDOC using the program RBDMIDOC and we are using the message type HRMD_A.Under this message type we have configured two diff distribution models with different infotype data.

So when we execute the program we have only one input parameter that takes the message type.based on our setup will the program send the delta loads for both the distribution models since they are using the same message type which we do not want.

How do we restrict the program to send the delta loads only for the intended distribution models even though they are using the same message type.

Thanks

Bala Duvvuri

[Former Member]

Hi Bala, Assuming that based on IDoc content there is some way to determine which system should be the recipient, you could do the following (requires ABAP development as indicated by Mylène):

• Define a new filter object type if required via BD95.
• 
  
• Assign new or existing filter object to E1PLOGI segment field FILTER1 or FILTER2 via BD59
• 
  
• Create BAdI implementation for HRALE00OUTBOUND_IDOC and implement method FILTER_VALUES_SET to set values for FILTER1 or FILTER2
• 
  

Even without the BAdI implementation you'd see the new filter value appearing in your distribution model for message type HRMD_A. However, you need the ABAP logic for filling the fields with actual values that you can utilize. Cheers, harald

[Former Member]

are you using filter sets on your models? if so, can you give more details?

[Former Member]

Mylene,

yes I am using filter sets,both the models contain some common filter sets too(same infotypes)

Thanks

Bala Duvvuri

[Former Member]

The same message type (HRMD_A) plus the same filter type (INFO_SET)??

-- I fear there is no ready-made solution for you. What you need is a cross-breed between RHALESMD and RHALEINI ... I may be mistaken, but I would now go and search for an abapper :O)

Edited by: Mylène Dorias on May 6, 2010 12:14 PM typo.

[Former Member]

Hi Bala, Assuming that based on IDoc content there is some way to determine which system should be the recipient, you could do the following (requires ABAP development as indicated by Mylène):

• Define a new filter object type if required via BD95.
• 
  
• Assign new or existing filter object to E1PLOGI segment field FILTER1 or FILTER2 via BD59
• 
  
• Create BAdI implementation for HRALE00OUTBOUND_IDOC and implement method FILTER_VALUES_SET to set values for FILTER1 or FILTER2
• 
  

Even without the BAdI implementation you'd see the new filter value appearing in your distribution model for message type HRMD_A. However, you need the ABAP logic for filling the fields with actual values that you can utilize. Cheers, harald

[Former Member]

🐵 and I have now learned, how to do an ordered list in this forum ... thanks, Harald.

[Former Member]

we are using PFAL for delta loads

Thanks

Bala Duvvuri