C13Z_FILE_UPLOAD_BINARY SAP Function module

C13Z_FILE_UPLOAD_BINARY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name C13Z_FILE_UPLOAD_BINARY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: C13Z
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM C13Z_FILE_UPLOAD_BINARY - C13Z FILE UPLOAD BINARY

CALL FUNCTION 'C13Z_FILE_UPLOAD_BINARY' "
  EXPORTING
    i_file_front_end =          "
    i_file_appl =               " rcgfiletr-ftappl
*   i_file_overwrite = ESP1_FALSE  " esp1_boolean  Overwrite existing file
  IMPORTING
    e_flg_open_error =          " esp1_boolean  Error when opening file
    e_os_message =              " c
  EXCEPTIONS
    FE_FILE_NOT_EXISTS = 1      "
    FE_FILE_READ_ERROR = 2      "
    AP_NO_AUTHORITY = 3         "
    AP_FILE_OPEN_ERROR = 4      "
    AP_FILE_EXISTS = 5          "
    AP_CONVERT_ERROR = 6        "
    .  "  C13Z_FILE_UPLOAD_BINARY

ABAP code example for Function Module C13Z_FILE_UPLOAD_BINARY

The ABAP code below is a full code listing to execute function module C13Z_FILE_UPLOAD_BINARY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_flg_open_error  
 
 TYPE ESP1_BOOLEAN
,
ld_e_os_message  
 
 TYPE C
.


DATA(ld_i_file_front_end) = 'some text here'.


DATA(ld_i_file_appl) = some text here

DATA(ld_i_file_overwrite) = 'Check type of data required'.
.

CALL FUNCTION 'C13Z_FILE_UPLOAD_BINARY'
  EXPORTING
    i_file_front_end =           ld_i_file_front_end
    i_file_appl =                ld_i_file_appl
*   i_file_overwrite =           ld_i_file_overwrite
  IMPORTING
    e_flg_open_error =           ld_e_flg_open_error
    e_os_message =               ld_e_os_message
  EXCEPTIONS
    FE_FILE_NOT_EXISTS =         1
    FE_FILE_READ_ERROR =         2
    AP_NO_AUTHORITY =            3
    AP_FILE_OPEN_ERROR =         4
    AP_FILE_EXISTS =             5
    AP_CONVERT_ERROR =           6
    .  "  C13Z_FILE_UPLOAD_BINARY

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_flg_open_error
 
 TYPE ESP1_BOOLEAN ,
ld_i_file_front_end
 
 TYPE STRING ,
ld_e_os_message
 
 TYPE C ,
ld_i_file_appl
 
 TYPE RCGFILETR-FTAPPL ,
ld_i_file_overwrite
 
 TYPE ESP1_BOOLEAN .


ld_i_file_front_end = 'some text here'.

ld_i_file_appl = some text here
ld_i_file_overwrite = 'Check type of data required'.