Entering content frame

Function documentation Filtering BAPI Parameters Locate the document in its SAP Library structure

Use

Parameter filtering enables you to manage the number of datasets to be replicated in the BAPI interface using filter objects in the ALE distribution model.
The parameters filtered are BAPI table parameters. The lines in the BAPI parameter, that do not match the distribution specifications are filtered out. The filtered table lines are not replicated.

Example

Example: The logical system Q4VCLNT800 is the BAPI server for the BAPI RetailMaterial.Clone. Through the parameter filtering only the plant data of the material plant 001 is to be replicated in this system.

Prerequisites

The prerequisite for this filtering is that a Structure linkFilter Object Type is assigned to the relevant BAPI in your SAP applications. For some BAPIs SAP has already defined and assigned filter object types. You can also define your own filter object types and assign them to a BAPI (Defining Filter Object Types and Assigning Them to a BAPI.)

you have to define the valid filter object values in the distribution model. For more information see the Implementation Guide (IMG) in path SAP Application Server ® IDoc Interface / ALE  ®  Modeling and Implementing Business Processes ® Maintain Distribution Model.

Presently, BAPI parameters can only be filtered for distributing master data via BAPIs called asynchronously. For this reason the required ALE Customizing for parameter filtering is only allowed for asynchronous BAPIs with an ALE IDoc interface.

Parameter filtering is allowed for distributing transaction data via asynchronous BAPIs but for the most cases, it has no purpose.

BAPI parameter filtering for asynchronous parameters is always optional. To generate the BAPI-IDoc Interface you must select the Activate checkbox. Otherwise no coding can be generated in the BAPI-IDoc interface.

If a BAPI-IDoc interface has been generated without parameter filtering, you can specify no parameter filtering in ALE Customizing  afterwards.

Features

Parameters are filtered dynamically at runtime using the current data in the BAPI table parameters and the distribution conditions specified in the ALE distribution model.

·        Reads the specified parameter filter objects in the distribution model

·        Reads the interface definition of the BAPI

·        Reads the table field values of a table entry for the associated filter objects

·        Compares the distribution conditions with the filter objects read out and determines the value of the logical expression

·        Deletes table entry

·        Examines hierarchy-dependent BAPI parameters and, if applicable, deletes dependent table entries

·        For synchronous BAPIs: Calls associated function module and forwards the filtered parameters

·        For asynchronous BAPIs: Calls the generated BAPI-ALE interface and forwards the filtered parameters

The BAPI parameter filtering can also take into account a hierarchical dependency between BAPI table parameters (see Defining Hierarchies Between BAPI Parameters). You must specify any hierarchical dependencies before you generate the BAPI-ALE interface of the BAPI. The specified hierarchy is evaluated when the interface is generated and incorporated in the interface coding. The BAPI-ALE interface must be regenerated following all subsequent changes made to the hierarchy.

Once the generated IDoc type has been released, the specified hierarchy of the asynchronous BAPI cannot subsequently be changed because of compatibility problems.

 

 

Leaving content frame