Implementing Distribution Using BAPIs
Now that BAPIs and ALE can be integrated you can implement your ALE business processes using BAPIs
.BAPIs are methods of SAP business objects. They are defined in the Business Object Repository (BOR) and are subject to strict design guidelines. BAPIs are implemented as RFC-enabled function modules.
For further information on BAPIs see the
BAPI User Guide and BAPI Programming. As of Release 4.5A BAPIs can also be defined that are implemented outside the R/3 System, but can be called from the R/3 System. For further information see
BAPIs Used for Outbound Processing in the BAPI Programming guide and
BAPIs of SAP Interface Types in the BAPI User Guide.ALE provides a complete programming model for implementing BAPIs. ALE supports these method calls:
Synchronous method calls can also be used in ALE distribution scenarios. These method calls are either BAPIs or
In ALE Customizing you can assign the RFC destinations to be used for a synchronous method call.
If BAPIs are called asynchronously, ALE error handling and ALE audit can be used.
If an asynchronous BAPI call is to be used for the distribution, the BAPI-ALE interface required for inbound and outbound processing can be automatically generated. Developing an ALE business process in ABAP is restricted to the programming of the BAPI.
An object-oriented approach has the following advantages:
Process Flow
If you are not enhancing an SAP BAPI and you are not creating your own BAPI when you are implementing an ALE business process, you can simply follow the steps below:
If, on the other hand, you want to enhance a BAPI or create your own, you have to follow these steps:
You can verify the quality of the ALE layer and ALE business processes using
Automatic Tests.See also:
BAPIs for Interactive Processing Enhancing IDocs of BAPI-IDoc Interfaces