SAP EDOC_AIF_INTERFACE_DETERM Function Module for Determine AIF Interface for the Response









EDOC_AIF_INTERFACE_DETERM is a standard edoc aif interface determ SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine AIF Interface for the Response 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 edoc aif interface determ FM, simply by entering the name EDOC_AIF_INTERFACE_DETERM into the relevant SAP transaction such as SE37 or SE38.

Function Group: EDOC_AIF
Program Name: SAPLEDOC_AIF
Main Program: SAPLEDOC_AIF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EDOC_AIF_INTERFACE_DETERM 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 'EDOC_AIF_INTERFACE_DETERM'"Determine AIF Interface for the Response
EXPORTING
IV_TYPE = "AIF Interface Type Identifier
IV_CUST_NS = "Identifier for a customer specific AIF Interface Type
IV_CUST_TYPE = "Identifier for a Customer-Specific AIF Interface Type
IV_NAME1 = "Name of AIF Interface Type
IV_NAME2 = "Name of AIF Interface Type
IV_INPUT = "

IMPORTING
EV_NS = "eDocument: Namespace for AIF Mapping
EV_IFNAME = "eDocument: Interface Name for AIF Mapping
EV_IFVERSION = "eDocument: Interface Version for AIF Mapping

EXCEPTIONS
INTERFACE_DET_FAILED = 1
.



IMPORTING Parameters details for EDOC_AIF_INTERFACE_DETERM

IV_TYPE - AIF Interface Type Identifier

Data type: EDOC_AIF_INT_TYPE_ID
Optional: No
Call by Reference: Yes

IV_CUST_NS - Identifier for a customer specific AIF Interface Type

Data type: EDOC_AIF_NS
Optional: No
Call by Reference: Yes

IV_CUST_TYPE - Identifier for a Customer-Specific AIF Interface Type

Data type: EDOC_AIF_CUST_INT_TYPE_ID
Optional: No
Call by Reference: Yes

IV_NAME1 - Name of AIF Interface Type

Data type: EDOC_AIF_LFIELDNAME_INFDET
Optional: No
Call by Reference: Yes

IV_NAME2 - Name of AIF Interface Type

Data type: EDOC_AIF_LFIELDNAME_INFDET
Optional: No
Call by Reference: Yes

IV_INPUT -

Data type: ANY
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for EDOC_AIF_INTERFACE_DETERM

EV_NS - eDocument: Namespace for AIF Mapping

Data type: EDOC_AIF_NS
Optional: No
Call by Reference: Yes

EV_IFNAME - eDocument: Interface Name for AIF Mapping

Data type: EDOC_AIF_INTERFACE
Optional: No
Call by Reference: Yes

EV_IFVERSION - eDocument: Interface Version for AIF Mapping

Data type: EDOC_AIF_VERSION
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INTERFACE_DET_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EDOC_AIF_INTERFACE_DETERM 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_ev_ns  TYPE EDOC_AIF_NS, "   
lv_iv_type  TYPE EDOC_AIF_INT_TYPE_ID, "   
lv_interface_det_failed  TYPE EDOC_AIF_INT_TYPE_ID, "   
lv_ev_ifname  TYPE EDOC_AIF_INTERFACE, "   
lv_iv_cust_ns  TYPE EDOC_AIF_NS, "   
lv_ev_ifversion  TYPE EDOC_AIF_VERSION, "   
lv_iv_cust_type  TYPE EDOC_AIF_CUST_INT_TYPE_ID, "   
lv_iv_name1  TYPE EDOC_AIF_LFIELDNAME_INFDET, "   
lv_iv_name2  TYPE EDOC_AIF_LFIELDNAME_INFDET, "   
lv_iv_input  TYPE ANY. "   

  CALL FUNCTION 'EDOC_AIF_INTERFACE_DETERM'  "Determine AIF Interface for the Response
    EXPORTING
         IV_TYPE = lv_iv_type
         IV_CUST_NS = lv_iv_cust_ns
         IV_CUST_TYPE = lv_iv_cust_type
         IV_NAME1 = lv_iv_name1
         IV_NAME2 = lv_iv_name2
         IV_INPUT = lv_iv_input
    IMPORTING
         EV_NS = lv_ev_ns
         EV_IFNAME = lv_ev_ifname
         EV_IFVERSION = lv_ev_ifversion
    EXCEPTIONS
        INTERFACE_DET_FAILED = 1
. " EDOC_AIF_INTERFACE_DETERM




ABAP code using 7.40 inline data declarations to call FM EDOC_AIF_INTERFACE_DETERM

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!