SAP RFC_1A_UPLOAD_API_LOGFILEDIR Function Module for Upload API logfile directory
RFC_1A_UPLOAD_API_LOGFILEDIR is a standard rfc 1a upload api logfiledir SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Upload API logfile directory 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 rfc 1a upload api logfiledir FM, simply by entering the name RFC_1A_UPLOAD_API_LOGFILEDIR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_AMADEUS_RFC_INTERFACE
Program Name: SAPLFITP_AMADEUS_RFC_INTERFACE
Main Program: SAPLFITP_AMADEUS_RFC_INTERFACE
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RFC_1A_UPLOAD_API_LOGFILEDIR 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 'RFC_1A_UPLOAD_API_LOGFILEDIR'"Upload API logfile directory.
EXPORTING
LOGFILEEXTENSION = "
TABLES
LOGFILELIST = "
IMPORTING Parameters details for RFC_1A_UPLOAD_API_LOGFILEDIR
LOGFILEEXTENSION -
Data type: FTPS_API-TEXTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RFC_1A_UPLOAD_API_LOGFILEDIR
LOGFILELIST -
Data type: FTPS_API_DETL_FILE_DESCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RFC_1A_UPLOAD_API_LOGFILEDIR 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: | ||||
| lt_logfilelist | TYPE STANDARD TABLE OF FTPS_API_DETL_FILE_DESC, " | |||
| lv_logfileextension | TYPE FTPS_API-TEXT. " |
|   CALL FUNCTION 'RFC_1A_UPLOAD_API_LOGFILEDIR' "Upload API logfile directory |
| EXPORTING | ||
| LOGFILEEXTENSION | = lv_logfileextension | |
| TABLES | ||
| LOGFILELIST | = lt_logfilelist | |
| . " RFC_1A_UPLOAD_API_LOGFILEDIR | ||
ABAP code using 7.40 inline data declarations to call FM RFC_1A_UPLOAD_API_LOGFILEDIR
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 TEXT FROM FTPS_API INTO @DATA(ld_logfileextension). | ||||
Search for further information about these or an SAP related objects