Asynchronous BAPI-ALE Communication

[Former Member]

Hi,

I m working in the function module where we have to

Create a bespoke Outbound Processing Function Module (o/b FM) that is responsible for creating the IDoc sent to the Target System – SE37.

The o/b FM is to be used in supporting a BAPI, can anyone tell me what could be the minimum requirements?

Sushama

[Former Member · Accepted solution]

Do not use “type” for parameters. Use “like”

• Import parameters must be passed in as “value”

• Must had “Return” parameter

• Must be “RFC enabled”

~ For full BAPI compliance, check the “BAPI Project” in the “BAPI Explorer” - BAPI

~ If Filter Objects are to be used, parameters must be passed as tables (i.e. multiline in BAPI parameters.

To create the appointment we are going to use the following data, which represent the o/b FM’s interface.

date from

time from

date to

time to

description

participant_list (this is the list of users for whom the appointments will be created for).

~ Assign the o/

FUNCTION zbapi_req_apppointment.

*"----

---

""Local interface:

*" IMPORTING

*" VALUE(DATE_FROM) LIKE SCAPPT-DATE_FROM

*" VALUE(TIME_FROM) LIKE SCAPPT-TIME_FROM

*" VALUE(DATE_TO) LIKE SCAPPT-DATE_TO

*" VALUE(TIME_TO) LIKE SCAPPT-TIME_TO

*" VALUE(DESC) LIKE SCAPPT-TXT_SHORT

*" EXPORTING

*" VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2

*" TABLES

*" PARTICIPANT_LIST STRUCTURE SCSPARINC

*"----

---

ENDFUNCTION