How to store image in a table upload a image file (JPEG) from local PC to SAP

you can then retrieve it and then use it in a screen, I believe you can put it in a picture contol.

Here is how to save it in the MIME.

REPORT  zrich_0001.

DATA: lr_mime_rep TYPE REF TO if_mr_api.

DATA: lv_filename TYPE string.
DATA: lv_path     TYPE string.
DATA: lv_fullpath TYPE string.
DATA: lv_content  TYPE xstring.
DATA: lv_length   TYPE i.
DATA: lv_rc TYPE sy-subrc.

DATA: lt_file TYPE filetable.
DATA: ls_file LIKE LINE OF lt_file.


DATA: lt_data TYPE STANDARD TABLE OF x255.

PARAMETERS: p_path TYPE string
            DEFAULT 'SAP/PUBLIC/Test.jpg'.   "<<-- Mime path, save to path


cl_gui_frontend_services=>file_open_dialog(
 CHANGING
   file_table              =  lt_file  " Table Holding Selected Files
   rc                      =  lv_rc  ). " Return Code, Number of Files or -1 If Error Occurred
READ TABLE lt_file INTO ls_file INDEX 1.
IF sy-subrc = 0.
 lv_filename = ls_file-filename.
ENDIF.

cl_gui_frontend_services=>gui_upload(
 EXPORTING
   filename                = lv_filename    " Name of file
   filetype                = 'BIN'
 IMPORTING
   filelength              =  lv_length   " File length
 CHANGING
   data_tab                = lt_data    " Transfer table for file contents
 EXCEPTIONS
   OTHERS                  = 19 ).

CALL FUNCTION 'SCMS_BINARY_TO_XSTRING'
 EXPORTING
   input_length = lv_length
*    first_line   = 0
*    last_line    = 0
 IMPORTING
   buffer       = lv_content
 TABLES
   binary_tab   = lt_data
 EXCEPTIONS
   failed       = 1
   OTHERS       = 2.

lr_mime_rep = cl_mime_repository_api=>if_mr_api~get_api( ).

lr_mime_rep->put(
 EXPORTING
   i_url                     = p_path
   i_content                 = lv_content
 EXCEPTIONS
   parameter_missing         = 1
   error_occured             = 2
   cancelled                 = 3
   permission_failure        = 4
   data_inconsistency        = 5
   new_loio_already_exists   = 6
   is_folder                 = 7

when you are ready to show the image in a picture control on a screen. 
You can do something like this.  This uses a docking container so that
you don't have to create a screen, but it works the same way with a
customer container.

REPORT  zrich_0001.

DATA: lr_mime_rep TYPE REF TO if_mr_api.

DATA: lv_url TYPE char255.
DATA: lv_content  TYPE xstring.
DATA: lv_repid TYPE sy-repid.

DATA: lt_data TYPE STANDARD TABLE OF x255.

DATA: lo_docking TYPE REF TO cl_gui_docking_container.
DATA: lo_picture TYPE REF TO cl_gui_picture.

DATA: p_path TYPE string VALUE 'SAP/PUBLIC/Test.jpg'.

PARAMETERS: p_check.

AT SELECTION-SCREEN OUTPUT.

* Create controls
 CREATE OBJECT lo_docking
   EXPORTING
     repid     = lv_repid
     dynnr     = sy-dynnr
     side      = lo_docking->dock_at_left
     extension = 200.

 CREATE OBJECT lo_picture
   EXPORTING
     parent = lo_docking.

 lr_mime_rep = cl_mime_repository_api=>if_mr_api~get_api( ).

 lr_mime_rep->get(
            EXPORTING
                 i_url      = p_path
            IMPORTING
                  e_content = lv_content
            EXCEPTIONS
                  not_found = 3 ).

 CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
   EXPORTING
     buffer     = lv_content
   TABLES
     binary_tab = lt_data.

 CALL FUNCTION 'DP_CREATE_URL'
   EXPORTING
     type    = 'IMAGE'
     subtype = 'JPG'
   TABLES
     data    = lt_data
   CHANGING
     url     = lv_url.

 lo_picture->load_picture_from_url_async( lv_url ).

ZTABLE Transport along with the data in development to quality

Rule 1:
Table entries can be forcefully included in a transport request and can be transported to the required system.
For including the table entries in a request,Follow the below mentioned procedure.

1.create a workbunch request in SE01.

2.Double click on the request no.

3.Select the object tab in the new screen appeared.

4.Go for change mode (Ctrl+F1)

5.Select the Program id as R3TR and Object Type as TABU.

6.Give the Object name as Table name(ZTABLE)

7.Click on the function button on that row.

Give * in that editor appeared and save this.

Now all the table entries are binded in that request and can be transported across the server.

instead if you are putting on the user recordin on in TMG it will ask for a request each time you save some entries in the table.