BD21 program RBDMIDOC: restrict data to send

[Former Member]

Hi everyone.

With transaction BD21 (RBDMIDOC) it is possible to send master data through change pointers via ALE but I would like to know if it is possible to restrict the information that it sends. For example in HR I would like to avoid sending some employees. Is this possible?

Thank you in advance.

[Former Member]

Hi,

You can filter the IDOC using filter objects in Distribution Model configuration in BD64.

See SAP documentation [Filtering Data in Distribution Model|http://help.sap.com/saphelp_bw/helpdata/en/64/f878da891b11d2a5bd0060087832f8/content.htm] for further details.

Regards

Vinod

[Former Member]

Hi Vinod.

Thanks for your answer. Yes in the distribution model you can choose what data is sent but not depending on the values but in the kind of information. For example you can filter by infotype 0 and send only this information but you can not choose to send employees with number between 1 and 1000. This is what I need, I need to exclude some employees so they will never be sent.

[Former Member]

Hi,

You can filter the idocs based on the data also. Hope this SDN Thread [Ale Custom filter group|; will be helpful.

Regards

Vinod

[Former Member]

Hi.

That thread is about creating a new type of filter. The thing is that I already have the type of filter that I want, I just want to exclude some values. What I need is avoid sending information about regarding some specific master data.

[Former Member]

Hi,

For excluding the idocs based on the data, may be you have to look at the userexit/BADI/BTE related to the Function module which is used to trigger the idoc.

Edit : Like BTE "VKOA0100" can be used for filtering the Outbound Pricing condition IDOCs.

Regards

Vinod

Edited by: Vinod Kumar on Sep 3, 2010 3:07 PM

[Former Member]

Yes I was thinking that maybe in the conversion rule associated to the segment of the IDoc "number of employee" I could modify the code in order to change the employee number of these empoyees to 00000000 but I dont know if that will generate an error in the destiny system. Anyway that is not a very elegant solution. Maybe there is a customizing solution for this... In the same way that in the distribution model you can choose the type of data maybe there is a place where you can exclude some values related to the master data. Or maybe inserting a bapi in the distribution model but it is not possible to insert a BAPI that I have created, is it?

[Former Member]

Juan,

you can implement this badi HRALE00OUTBOUND_IDOC to meet your requirement

Thanks

Bala Duvvuri

[Former Member]

Hi Bala and Vinod.

Yes to solve the problem I have implemented the BADI HRALE00OUTBOUND_IDOC. Before that I had to define a filter in transaction bd95 and then assign this filter to the message type in transaction bd59 so I can use it in BD64 transaction. Afterwards include the filter in the distribution model in transaction BD64 and then implement the mentioned BADI to classify the master data.

Thank you for your tips!