SAP DX_GET_FILE_PORT Function Module for

Search SAP Function Modules

DX_GET_FILE_PORT is a standard dx get file port SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 dx get file port FM, simply by entering the name DX_GET_FILE_PORT into the relevant SAP transaction such as SE37 or SE38.

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

Function DX_GET_FILE_PORT 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 'DX_GET_FILE_PORT'"
  EXPORTING
   OBJECTTYPE =  "
   PROGTYPE =  "Program Type
   LOADPRG =  "
   LOGSYS =  "
   INB_FILENAME =  "File Name
   INB_FILETYPE =  "File type (L=logical, P=physical)

 IMPORTING
   MESTYPE =  "
   PORT =  "
   FILENAME =  "

EXCEPTIONS
   NO_ALE_IDOC_INTERFACE = 1    CANCELED_BY_USER = 2    ERROR_IN_PARTNERAGREEMENT = 3    ERROR_IN_PORTDEFINITION = 4    OUTMOD_IS_DIRECT = 5    ERROR_IN_FILENAME = 6    OWN_LOGSYS = 7    NO_AUTHORITY = 8 

.

IMPORTING Parameters details for DX_GET_FILE_PORT

OBJECTTYPE -

Data type: TDXLOADP-OBJECTTYPE
Optional: No
Call by Reference: Yes

PROGTYPE - Program Type

Data type: TDXLOADP-PROGTYPE
Optional: No
Call by Reference: Yes

LOADPRG -

Data type: TDXLOADP-PROGNAME
Optional: No
Call by Reference: Yes

LOGSYS -

Data type: TBDLS-LOGSYS
Optional: No
Call by Reference: Yes

INB_FILENAME - File Name

Data type: DXFILE-FILENAME
Optional: No
Call by Reference: Yes

INB_FILETYPE - File type (L=logical, P=physical)

Data type: DXFILE-FILETYPE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for DX_GET_FILE_PORT

MESTYPE -

Data type: EDIDC-MESTYP
Optional: No
Call by Reference: No ( called with pass by value option)

PORT -

Data type: EDIPORT-PORT
Optional: No
Call by Reference: No ( called with pass by value option)

FILENAME -

Data type: DXFILEN-FILENAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_ALE_IDOC_INTERFACE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANCELED_BY_USER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_IN_PARTNERAGREEMENT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_IN_PORTDEFINITION -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OUTMOD_IS_DIRECT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_IN_FILENAME -

Data type:
Optional: No
Call by Reference: Yes

OWN_LOGSYS -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DX_GET_FILE_PORT 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.

ABAP code using 7.40 inline data declarations to call FM DX_GET_FILE_PORT

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