SAP /AIF/CALL_LOCAL_INTERFACE Function Module for Calls popup for local interfaces
/AIF/CALL_LOCAL_INTERFACE is a standard /aif/call local interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calls popup for local interfaces processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for /aif/call local interface FM, simply by entering the name /AIF/CALL_LOCAL_INTERFACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: /AIF/LOCAL_IF
Program Name: /AIF/SAPLLOCAL_IF
Main Program: /AIF/SAPLLOCAL_IF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /AIF/CALL_LOCAL_INTERFACE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION '/AIF/CALL_LOCAL_INTERFACE'"Calls popup for local interfaces.
EXPORTING
NS = "Namespace
IFNAME = "
IFVERSION = "
* VIN = "Vehicle Identification Number (Vehicle Identification No.)
* SPARTE = "Division
* VBELN = "
* FAMGR = "
* TYPKZ = "
* CALL_SYNC = "
CHANGING
* IFDATA = "
EXCEPTIONS
CANCEL = 1 NOTHING_DONE = 2 NO_NUMBER = 3 ERR_EXECUTE = 4
IMPORTING Parameters details for /AIF/CALL_LOCAL_INTERFACE
NS - Namespace
Data type: /AIF/NSOptional: No
Call by Reference: Yes
IFNAME -
Data type: /AIF/IFNAMEOptional: No
Call by Reference: Yes
IFVERSION -
Data type: /AIF/IFVERSIONOptional: No
Call by Reference: Yes
VIN - Vehicle Identification Number (Vehicle Identification No.)
Data type: /AIF/VLC_VHVINOptional: Yes
Call by Reference: Yes
SPARTE - Division
Data type: /AIF/SPARTOptional: Yes
Call by Reference: Yes
VBELN -
Data type:Optional: Yes
Call by Reference: Yes
FAMGR -
Data type:Optional: Yes
Call by Reference: Yes
TYPKZ -
Data type:Optional: Yes
Call by Reference: Yes
CALL_SYNC -
Data type:Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for /AIF/CALL_LOCAL_INTERFACE
IFDATA -
Data type:Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
CANCEL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOTHING_DONE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_NUMBER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_EXECUTE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /AIF/CALL_LOCAL_INTERFACE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_ns | TYPE /AIF/NS, " | |||
| lv_cancel | TYPE /AIF/NS, " | |||
| lv_ifdata | TYPE /AIF/NS, " | |||
| lv_ifname | TYPE /AIF/IFNAME, " | |||
| lv_nothing_done | TYPE /AIF/IFNAME, " | |||
| lv_ifversion | TYPE /AIF/IFVERSION, " | |||
| lv_no_number | TYPE /AIF/IFVERSION, " | |||
| lv_vin | TYPE /AIF/VLC_VHVIN, " | |||
| lv_err_execute | TYPE /AIF/VLC_VHVIN, " | |||
| lv_sparte | TYPE /AIF/SPART, " | |||
| lv_vbeln | TYPE /AIF/SPART, " | |||
| lv_famgr | TYPE /AIF/SPART, " | |||
| lv_typkz | TYPE /AIF/SPART, " | |||
| lv_call_sync | TYPE /AIF/SPART. " |
|   CALL FUNCTION '/AIF/CALL_LOCAL_INTERFACE' "Calls popup for local interfaces |
| EXPORTING | ||
| NS | = lv_ns | |
| IFNAME | = lv_ifname | |
| IFVERSION | = lv_ifversion | |
| VIN | = lv_vin | |
| SPARTE | = lv_sparte | |
| VBELN | = lv_vbeln | |
| FAMGR | = lv_famgr | |
| TYPKZ | = lv_typkz | |
| CALL_SYNC | = lv_call_sync | |
| CHANGING | ||
| IFDATA | = lv_ifdata | |
| EXCEPTIONS | ||
| CANCEL = 1 | ||
| NOTHING_DONE = 2 | ||
| NO_NUMBER = 3 | ||
| ERR_EXECUTE = 4 | ||
| . " /AIF/CALL_LOCAL_INTERFACE | ||
ABAP code using 7.40 inline data declarations to call FM /AIF/CALL_LOCAL_INTERFACE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects