|
---------------------------------2006-01-27----2006-02-07----------------------------------
这段时间花时间看了些ALE和IDOC方面的资料感觉收获不大,可能是没实践操作的原因.
1, BAPIs Must not contain call transaction or submit report.
2, BAPI structure must not use includes.
3, BAPIs should not use dialogs.
4, Asynchronous BAPIs use the ALE interface in this way:
.Creates an IDOC from the BAPI data
.Sends the IDOC to the target system
.Receives the IDOC in the target system, create the BAPIs data from the IDOC and the BAPI.
.An ALE interface for a BAPIs is created in transaction BDBG.
5, Programming a BAPI consists of follow major tasks:
.Defining BAPI data structrues in se11.
.Program a RFC enabled BAPI function module for each method.
.Create a Business object for the BAPI in the BOR.
.Documentation the BAPI.
.Generate ALE interface for asychronous BAPIS.
.Generate and release.
6, Each BAPI must have its own fuction group. we would create related BAPIs in the same fuction pool. so they will by abele to share global data.
7, Step by step to create BAPI.
.Define a structure for the BAPI.
.Write Function Moudle
.create the API Method Using the BAPI wizard.
.Final steps.
.Release the BAPI function module(in the function builder).
.Release the business object type(in the BOR objecttype->implemented).
.Release the BAPI as a mehtod in the BOR.
.For potential write BAPIS: Release the IDOC and its segments. |
|