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.