SAP FX_DEAL_CREATE_VIA_INTERFACE Function Module for Entry of Transaction Passed On via Interface
FX_DEAL_CREATE_VIA_INTERFACE is a standard fx deal create via 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 Entry of Transaction Passed On via Interface 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 fx deal create via interface FM, simply by entering the name FX_DEAL_CREATE_VIA_INTERFACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTX4
Program Name: SAPLFTX4
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FX_DEAL_CREATE_VIA_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 'FX_DEAL_CREATE_VIA_INTERFACE'"Entry of Transaction Passed On via Interface.
EXPORTING
I_VTBFXIFDC = "
* FLG_CHECK = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FX_DEAL_CREATE_VIA_INTERFACE
I_VTBFXIFDC -
Data type: VTBFXIFDCOptional: No
Call by Reference: No ( called with pass by value option)
FLG_CHECK -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FX_DEAL_CREATE_VIA_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_error | TYPE STRING, " | |||
| lv_i_vtbfxifdc | TYPE VTBFXIFDC, " | |||
| lv_flg_check | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'FX_DEAL_CREATE_VIA_INTERFACE' "Entry of Transaction Passed On via Interface |
| EXPORTING | ||
| I_VTBFXIFDC | = lv_i_vtbfxifdc | |
| FLG_CHECK | = lv_flg_check | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FX_DEAL_CREATE_VIA_INTERFACE | ||
ABAP code using 7.40 inline data declarations to call FM FX_DEAL_CREATE_VIA_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.| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_flg_check). | ||||
Search for further information about these or an SAP related objects