How does the filter work in BD64

[Former Member]

Hi all,

I have configured ALE to distribute material master data from the sedning system to recievung system. Also in bd64 I have created filter for plant in the following manner.

Select modelview -> and expand the tree -> under the message type select -> noo filter option -> create filter group -> in that I have selected plant and in the values I have specified 1000. I saved and came back he message displaye under the message type is <b>Data Filter Active</b>. I went to bd 10 and send a material which is located at plant 1000. IN we02 when I checked the stauts is success with green light and one of the staus record with status 30 has this message <b>Receiver found , Data filtered , No conversion , Version conversion.</b> When I checked the recieving side the data records stll contains the plant value 1000.

What I expected is since I am filetring the Idoc based upon plant value, Idoc shouldn't be tranferred or the plant value must be erased on the recieving side. I still the value for werks is 1000.

I have configured bd64 only on sending side. The recieving side has this message <b>No filters , No conversion , No version change .</b> so should I configure bd64 on recieving side also for filters to be implemented and ths is only one way communication.

So I doubt how the filters work. Can anyone please expalin me how the filter works.

Regards,

Vijay.

Message was edited by: vijay kalava

[Former Member]

Hi all,

I have configured ALE to distribute material master data from the sedning system to recievung system. Also in bd64 I have created filter for plant in the following manner.

Select modelview -> and expand the tree -> under the message type select -> noo filter option -> create filter group -> in that I have selected plant and in the values I have specified 1000. I saved and came back he message displaye under the message type is <b>Data Filter Active</b>. I went to bd 10 and send a material which is located at plant 1000. IN we02 when I checked the stauts is success with green light and one of the staus record with status 30 has this message <b>Receiver found , Data filtered , No conversion , Version conversion.</b> When I checked the recieving side the data records stll contains the plant value 1000.

What I expected is since I am filetring the Idoc based upon plant value, Idoc shouldn't be tranferred or the plant value must be erased on the recieving side. I still the value for werks is 1000.

I have configured bd64 only on sending side. The recieving side has this message <b>No filters , No conversion , No version change .</b> so should I configure bd64 on recieving side also for filters to be implemented and ths is only one way communication.

So I doubt how the filters work. Can anyone please expalin me how the filter works.

Regards,

Vijay.

Message was edited by: vijay kalava

[Former Member]

Hi,

<b>No filters , No conversion , No version change</b> means you are sending the same idoc which is already existing and with out any changes. if you process the same idoc again and again then it will give the same message.

Regards

Vijay

[Former Member]

Hi Vijay,

Now I tried to send a different material but the message I get is <b>Receiver found , No filters , No conversion , Version conversion</b> The model view is not disurbed but I don't unerstand why the data is not filtered. Can you please explain me how the filter setup in bd64 works exactly.

Regards,

Vijay.

[Former Member]

Actually Vijay,

I believe that filters work quite the opposite to what you are saying.

I think that if a material has two plants : plant 1000 and plant 2000. And if you apply a filter on plant 1000 then only plant 1000 goes downstream.

Can you please test this and let us know ?

Thanks,

Urmila

[Former Member]

Hi Urmila,

You are right I tried to send a maetrial with plant value 1100 , on the ending Idoc the <b>segment E1MARCM has been tryncated</b> and the Idoc is sent sucessfully. This si shows that what you have said is correct. what ever value is secified in the filter will be sent and the rest will be filtered. Can you please clear my other doubts too in the query ?

Regards,

Vijay.

[Former Member]

Hi,

Check this Documentation..

Customer Distribution Model. In an R/3 system, the Customer Distribution Model is a tool that stores information about the flow of messages across various systems. The Customer Distribution Model uses an SAP-delivered Distribution Reference Model as its basis (the Customer Distribution Model can have distribution scenarios other than ones stored in the Distribution Reference Model.) The Customer Distribution Model stores data that dictates which messages (message types) flow to which Logical Systems. Many messages can flow to one Logical System, and one message can flow to several systems. With the use of filter objects and listings (which I’ll describe shortly), it is also possible to specify in a model the criteria for filtering information for a specific system. A Customer Distribution Model can be created in an R/3 system with that client’s base Logical System as the “sender” Logical System.

Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.

The IMG for ALE, Distribution (ALE) (*), can also be directly invoked by using transaction SALE. This transaction is used very frequently in ALE. (I’ll discuss the process of creating, maintaining, and distributing a Customer Distribution Model later in this article.)

Filter object type and filter objects. A filter object type is used in the Customer Distribution Model to impose a selection criterion on the message (type) flowing to a Logical System. A filter object type with a value associated with it is called a filter object. For example, BUKRS (Company Code) is a filter object type available for message type DEBMAS (Customer Master). To distribute Customer master data of only Company Code “1001” to a particular Logical System, you would use filter object type BUKRS to create a filter object with value BUKRS = 1001. You can have multiple filter objects with different values for the same message type associated with that LS. While determining the receiver(s) of a particular message based on the Distribution Model, ALE performs object filtering. As with the Customer Distribution Model, filter objects are relevant only to ALE.

Regards

Vijay

[Former Member]

Hi Vijay,

If you want to know whether to add any filters to the receiving side, I don't think you need to do that.

In the IDOC creation process, first the Master IDOC is created, then several operations are performed like filtering, conversions,to create the communication idoc(status 30) then idoc is sent to port(Status 03) and finally the idoc is dispatched(status 12).

This is just a mechanism which tells you what jobs have been done. I don't think you should worry abt it unless you get a error message.

Regards,

Urmila

<b>Please award points my answers were useful</b>

[Former Member]

Hi Urmila,

Please dont worry about the points I will surely award them. I have one more doubt. Say If I am using reduced Idoc where in I use tcodes bd53 and reduce some fields , how does the filter work there ? The filtered fileds data will not be send to the recieving side right ?

Regards,

Vijay.

[Former Member]

Hi Vijay,

Please check this link. It will show you the procedure for Reduced IDoc and Segment Filter.

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

Hope this will help.

Let me know if you need further assistant.

Regards,

Ferry Lianto

[Former Member]

Hi Vijay,

can u please send me the procedure for creating filter objects and assigning them to CDM.

my mail_id is [email protected]

thank you very much.

with regards,

Saya