what does filter represent in ale.

[Former Member]

hi

what does filter represent in ale.

[Former Member]

hi

check with this link

http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a611c507d11d18ee90000e8366fc2/content.htm

Reward if it dose

Thanks

Siva kumar

[Former Member]

<b>Filter objects</b> are attributes of a message in the distribution model. A filter objects consists of a filter object type (for example, material type) and an assigned object value (for example PROD).

<b>Related Transaction codes</b>

<b>T.code BD95</b> Define Filter object type .We can specify the field and the table it belongs to as a filter object .

<b>T.code BD59</b> Assignment of Filter object type to the Message Type .Here we create the link between Filter object and the segment and the message type and the segment Field.

<b>T.code BD64</b> Distribution Model . Also known as Customer Distribution Model Used to define all the messages that will be exchanged between remote systems and the name of thes logical systems. Any filters can also be specified.

The model once created has to be distributed on every system which will be communicating ,It can be maintained on only One system

<b>Use</b>

ALE uses filter objects in outbound processing. You can use the filter objects to specify the content of a message and its receivers.

Filter objects function differently for message types and for BAPIs.

When message types are filtered, all the IDoc segments containing a field with an object type name whose value does not match the object value are suppressed. The subsegments of these IDoc segments are also suppressed.

If the suppressed segment was a mandatory segment and provided that there are no other mandatory segments of the same name on the same IDoc hierarchy level, the higher-level IDoc segment is also suppressed. This process is repeated and the final result depends on the specific IDoc structure, mandatory segments and the segments that have been repeatedly processed.

If the uppermost mandatory segment of an IDoc still exists after this process, the rest of the IDoc is distributed.

With BAPIs the filter object type corresponds to a parameter name. BAPI filter objects check whether a parameter contains the specified object value. An IDoc is created and distributed via the BAPI, only if this is the case.

The following distinction is made:

<b>Receiver determination</b>

When the receiver is determined, the filter objects are checked against the specified conditions and the valid receivers are reported back.

<b>Parameter filtering</b>

The dataset of the BAPI tables is determined by filtering the BAPI table parameters, similar to filtering IDoc segments.

Regards,

Maha

[Former Member]

Hi,

Filtering : By using this we can supress the unwanted segments. This technique is also called as reduced message type..

we have some methods of filtering like 1.Filtering at segment level : here we filter the unwanted segments.

2. Filtering at organization level: here we filter frm bd64..

3. Filtering at filed level.: here we filter the unwanted fields tcode:bd53.

Hope it might be helpful.

Regards,

Sana.

[Former Member]

Dear Chaitanya,

Filters

Definition
Filters represent the conditions that message types and BAPIs have to
satisfy so that they can be distributed by ALE outbound processing.

Use
ALE outbound processing determines the data content and receivers of
messages from the filters. Filters are assigned to methods or message
types in the distribution model. A filter is always assigned to a

Filter Group.

SAP Web Application Server
IDoc Interface/ALE
Model and implement Business Processes
Maintain Distribution Model

Structure
Message types and BAPIs can be filtered using the following filter types:
·Filter Objects
·Classes
·Dependencies

Filter Objects

Definition

Filter objects are attributes of a message in the distribution model. A filter objects consists of a filter object type (for example, material type) and an assigned object value (for example PROD).

Use

ALE uses filter objects in outbound processing. You can use the filter objects to specify the content of a message and its receivers.

Filter objects function differently for message types and for BAPIs.

When message types are filtered, all the IDoc segments containing a field with an object type name whose value does not match the object value are suppressed. The subsegments of these IDoc segments are also suppressed.
If the suppressed segment was a mandatory segment and provided that there are no other mandatory segments of the same name on the same IDoc hierarchy level, the higher-level IDoc segment is also suppressed. This process is repeated and the final result depends on the specific IDoc structure, mandatory segments and the segments that have been repeatedly processed.

If the uppermost mandatory segment of an IDoc still exists after this process, the rest of the IDoc is distributed.

With BAPIs the filter object type corresponds to a parameter name. BAPI filter objects check whether a parameter contains the specified object value. An IDoc is created and distributed via the BAPI, only if this is the case.
The following distinction is made:

Receiver determination
When the receiver is determined, the filter objects are checked against the specified conditions and the valid receivers are reported back.

For further information see Determining the Receivers of a BAPI in the ALE Programming Guide.

Parameter filtering
The dataset of the BAPI tables is determined by filtering the BAPI table parameters, similar to filtering IDoc segments.



Structure

Filter objects comprise a filter object type and an assigned object value.

Filter object types are either field names in IDoc segments or parameter names in BAPI calls.

Classes

Definition
Classes are groups of similar objects with common characteristics.

Use
The SAP System classification can be used to control ALE distribution. Distributable object classes can be assigned to a message type and used as filters for distributing this message type.

For example, you can classify the following object types:

· Material

· Customer

· Vendor

Structure
A class contains characteristics that describe the attributes of the objects to be classified. You can define the values allowed for the characteristics.

Dependencies

Definition
Dependencies describe the distribution relationship between the interfaces below:
Between BAPIs
Between message types
Between a BAPI and a message type


Use
In some cases business processes and data only need to be distributed, if other processes are also being distributed. If so, you can make the dispatch of one message dependent on the dispatch of another one.

Such a dependency must be implemented using an application function module and it must be defined in ALE Development. For more information see the ALE Programming Guide.

When you maintain the distribution model, these defined dependencies are offered as an option for receiver filtering.

Example of dependency between a BAPI and a message type:

The distribution of company addresses has been integrated in the object maintenance for the vendor. The address data is then distributed together with the object data via ALE. The address data is dependent on the object data and is distributed via the BAPI. The object data is distributed in the message type CREMAS.

So a dependency exists between the BAPI and the message type.

In the distribution model an active receiver filter is assigned to the BAPI used for distributing organization addresses (AddressOrg.SaveReplica). The dependency has been activated in the attribute Dependent distribution in the filter display.

Based on the receiver determination, the object data with the BAPI addresses are only distributed, if the filter condition for CREMAS is met.


Regards,
Rajesh K Soman

Kindly reward points if found helpful.