My task was to perform a migration that uploads files to the Generic Object Service (BC-SRV-GBT-GOS).

I knew that the files are stored via Business Document Service (BC-SRV-BDS) using the Knowledge Provider (BC-SRV-KPR).
So I thought I will google a released and documented API for that:
But, hey this is SAP! We would not earn so much money, if everything is perfectly documented ;-)

I found a few blogs and comments, but non served me well.
So I spend a bit of time finding a solution and I would like to share this with you.

There is an API for that

My input is a binary file, so I need something that can handle RAW data, sometimes also called HEX.
I came across the function module SO_ATTACHMENT_INSERT_API1, but then I would need to call a few undocumented FMs to create a folder and link it to that. For me this was too much undocumented stuff.
At the end I found the static BOR method Message.Create, which is officially released by SAP

Sample

To demonstrate how it works, here is a sample program:

• The file is uploaded with cl_gui_frontend_services=>gui_upload from the frontend.
• Filename and extension are split with the help of DMS function modules
• Storage with BOR method Message.Create
• Linking the document to the original BOR object using BINARY_RELATION_CREATE

*----------------------------------------------------------------------* * Developer : Stephan Heinberg * Requested by / Analyst : Stephan Heinberg * Date : 22.01.2012 12:12:26 *----------------------------------------------------------------------* * Changes: * INTITALS CHANGE DOC DESCRIPTION *----------------------------------------------------------------------* * SH 22.01.2012 12:12:26 This program will upload one file as GOS attachment using BDS *----------------------------------------------------------------------* REPORT zlocal_heinberg_04b. *----------------------------------------------------------------------* * Globale Daten *----------------------------------------------------------------------* *Macros für BOR Programmierung. INCLUDE <cntn01>. TYPE-POOLS: abap. *----------------------------------------------------------------------* * Selektionsbild *----------------------------------------------------------------------* PARAMETERS: p_file TYPE filep OBLIGATORY, p_bortp LIKE obl_s_pbor-typeid OBLIGATORY DEFAULT 'BUS2078', p_qmnum LIKE qmel-qmnum OBLIGATORY VALUE CHECK DEFAULT '200126442' . START-OF-SELECTION. PERFORM do_it. *&---------------------------------------------------------------------* *& Form do_it *&---------------------------------------------------------------------* * text *----------------------------------------------------------------------* FORM do_it . DATA: lt_content_bin TYPE TABLE OF solix, lv_filename TYPE string, lv_file_length TYPE i, ls_object TYPE borident, ls_note TYPE borident, lv_objdes TYPE so_obj_des, lv_file_ext TYPE so_fileext, lv_file_name TYPE filep, lv_file_name_no_ext TYPE filep, lv_file_extension TYPE filep, lt_document_header TYPE TABLE OF soli, ls_document_header TYPE soli . DATA: lo_message TYPE swc_object . lv_filename = p_file. CALL METHOD cl_gui_frontend_services=>gui_upload EXPORTING filename = lv_filename filetype = 'BIN' IMPORTING filelength = lv_file_length CHANGING data_tab = lt_content_bin EXCEPTIONS file_open_error = 1 file_read_error = 2 no_batch = 3 gui_refuse_filetransfer = 4 invalid_type = 5 no_authority = 6 unknown_error = 7 bad_data_format = 8 header_not_allowed = 9 separator_not_allowed = 10 header_too_long = 11 unknown_dp_error = 12 access_denied = 13 dp_out_of_memory = 14 disk_full = 15 dp_timeout = 16 not_supported_by_gui = 17 error_no_gui = 18. IF sy-subrc <> 0. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. ENDIF. * Füge Extesion und Beschreibung Dateiname * Extesion hat nur drei STellen PERFORM get_filename_and_extesion USING p_file CHANGING lv_file_name lv_file_name_no_ext lv_file_extension. lv_objdes = lv_file_name_no_ext. lv_file_ext = lv_file_extension. * Siehe Hinweis 1459896 - BCS: Unterstützung für vierstellige Dateiendungen CONCATENATE '&SO_FILENAME=' lv_file_name INTO ls_document_header. INSERT ls_document_header INTO TABLE lt_document_header. * Objekt initialisieren, gibt ja keinen Garbage Collector. swc_refresh_object lo_message. swc_container l_cont. swc_create_object lo_message 'MESSAGE' abap_false. swc_set_element l_cont 'NO_DIALOG' abap_true. swc_set_element l_cont 'DOCUMENTTITLE' lv_objdes. swc_set_table l_cont 'Content_Hex' lt_content_bin. swc_set_element l_cont 'DOCUMENTTYPE' lv_file_ext. swc_set_element l_cont 'DOCUMENTSIZE' lv_file_length. swc_set_element l_cont 'DocumentHeader' lt_document_header. swc_call_method lo_message 'CREATE' l_cont. IF sy-subrc <> 0. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. ENDIF. swc_get_object_key lo_message ls_note-objkey. * Schlüssel BOR ls_object-objkey = p_qmnum. ls_object-objtype = p_bortp. * Schlüssel MESSAGE ls_note-objtype = 'MESSAGE'. CALL FUNCTION 'BINARY_RELATION_CREATE' EXPORTING obj_rolea = ls_object obj_roleb = ls_note relationtype = 'ATTA' EXCEPTIONS no_model = 1 internal_error = 2 unknown = 3. IF sy-subrc <> 0. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. ENDIF. COMMIT WORK. ENDFORM. " DO_IT *&---------------------------------------------------------------------* *& Form get_filename_and_extesion *&---------------------------------------------------------------------* * text *----------------------------------------------------------------------* * -->UV_FILE text * -->CV_FILE_NAME text * -->CV_FILE_NAME_NO_EXT text * -->CV_FILE_EXTENSION text *----------------------------------------------------------------------* FORM get_filename_and_extesion USING uv_file TYPE filep CHANGING cv_file_name TYPE filep cv_file_name_no_ext TYPE filep cv_file_extension TYPE filep. CALL FUNCTION 'CV120_SPLIT_PATH' EXPORTING pf_path = uv_file IMPORTING pfx_file = cv_file_name. CALL FUNCTION 'CV120_SPLIT_FILE' EXPORTING pf_file = cv_file_name IMPORTING pfx_file = cv_file_name_no_ext pfx_extension = cv_file_extension. ENDFORM. "get_filename_and_extesion

Background

Just a few remarks:
2010 SAP enhanced the BCS APIs to handle four digit file name extensions. Check note 1459896.
By default BCS documents are stored in the main SAP database. So keep that in mind when planning a big migration! You can also store the document on a Content Server.
Compare:
Note 904711 - SAPoffice: Where are documents physically stored?
Note 530792 - Storing documents in the generic object services

Hope I could help, if you are on a similar task.