BBP_CTR_UI_UPLOAD SAP Function module - Upload Kontrakt

BBP_CTR_UI_UPLOAD 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 BBP_CTR_UI_UPLOAD into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BBP_CTR_UI_UPLOAD - BBP CTR UI UPLOAD

CALL FUNCTION 'BBP_CTR_UI_UPLOAD' "Upload Kontrakt
* EXPORTING
*   iv_header_guid =            " bbp_guid      Globally Unique Identifier
*   iv_cache_id =               " sysuuid-c     UUID in Character-Darstellung
*   is_header =                 " bbps_ctr_ui_header  Purchase Contract Header Structure
* TABLES
*   et_messages =               " bbp_pds_messages  Tabellentyp für Fehlermeldungen
* CHANGING
*   cv_background_proc =        " xfeld         Feld zum Ankreuzen
*   cv_disp_variant =           " bbp_disp_variant  Anzeigevariante
*   ct_file_options =           " bbpt_file_options  Tabelle für Datei-Optionen
*   cs_header =                 " bbps_ctr_ui_header  Kopfstruktur Einkaufskontrakt
    .  "  BBP_CTR_UI_UPLOAD

ABAP code example for Function Module BBP_CTR_UI_UPLOAD

The ABAP code below is a full code listing to execute function module BBP_CTR_UI_UPLOAD 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:
it_et_messages  
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES,"TABLES PARAM
wa_et_messages
 
 LIKE LINE OF it_et_messages
.


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

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

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

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

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


DATA(ld_iv_cache_id) = some text here

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

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
.

CALL FUNCTION 'BBP_CTR_UI_UPLOAD'
* EXPORTING
*   iv_header_guid =             ld_iv_header_guid
*   iv_cache_id =                ld_iv_cache_id
*   is_header =                  ld_is_header
* TABLES
*   et_messages =                it_et_messages
* CHANGING
*   cv_background_proc =         ld_cv_background_proc
*   cv_disp_variant =            ld_cv_disp_variant
*   ct_file_options =            ld_ct_file_options
*   cs_header =                  ld_cs_header
    .  "  BBP_CTR_UI_UPLOAD

IF SY-SUBRC EQ 0.
  "All OK
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_cv_background_proc
 
 TYPE XFELD ,
ld_iv_header_guid
 
 TYPE BBP_GUID ,
it_et_messages
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_et_messages
 
 LIKE LINE OF it_et_messages,
ld_cv_disp_variant
 
 TYPE BBP_DISP_VARIANT ,
ld_iv_cache_id
 
 TYPE SYSUUID-C ,
ld_ct_file_options
 
 TYPE BBPT_FILE_OPTIONS ,
ld_is_header
 
 TYPE BBPS_CTR_UI_HEADER ,
ld_cs_header
 
 TYPE BBPS_CTR_UI_HEADER .


ld_cv_background_proc = 'Check type of data required'.
ld_iv_header_guid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
ld_cv_disp_variant = 'Check type of data required'.

ld_iv_cache_id = some text here
ld_ct_file_options = 'Check type of data required'.
ld_is_header = 'Check type of data required'.
ld_cs_header = 'Check type of data required'.