BBP_SAPXML1_VND_CATALOG_SEND SAP Function module - Treiber zu META_VENDOR_CATALOG_SEND (supplier directory)

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

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

Pattern for FM BBP_SAPXML1_VND_CATALOG_SEND - BBP SAPXML1 VND CATALOG SEND

CALL FUNCTION 'BBP_SAPXML1_VND_CATALOG_SEND' "Treiber zu META_VENDOR_CATALOG_SEND (supplier directory)
  EXPORTING
*   is_bus_ei_main =            " bus_ei_main   Ext. Schnittstelle: Geschftspartnergesamtdaten
*   it_venmap =                 " bbpt_but_venmap_t  Tabellentyp fr R/3-Lieferantennummer
    iv_message =                " char40        Character 40-Stellen
*   it_surveys =                " bbpt_bupa_catalog_quest  Daten Lieferantenfragebogen fr Katalogtransfer
    iv_with_catalog_model = 'X'  " xfeld        Feld zum Ankreuzen
*   it_languages =              " bbpt_bupa_catalog_quest  Infomation über die verwendeten Sprachen
    .  "  BBP_SAPXML1_VND_CATALOG_SEND

ABAP code example for Function Module BBP_SAPXML1_VND_CATALOG_SEND

The ABAP code below is a full code listing to execute function module BBP_SAPXML1_VND_CATALOG_SEND 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_is_bus_ei_main) = 'Check type of data required'.

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

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

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

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

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

CALL FUNCTION 'BBP_SAPXML1_VND_CATALOG_SEND'
  EXPORTING
*   is_bus_ei_main =             ld_is_bus_ei_main
*   it_venmap =                  ld_it_venmap
    iv_message =                 ld_iv_message
*   it_surveys =                 ld_it_surveys
    iv_with_catalog_model =      ld_iv_with_catalog_model
*   it_languages =               ld_it_languages
    .  "  BBP_SAPXML1_VND_CATALOG_SEND

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_is_bus_ei_main
 
 TYPE BUS_EI_MAIN ,
ld_it_venmap
 
 TYPE BBPT_BUT_VENMAP_T ,
ld_iv_message
 
 TYPE CHAR40 ,
ld_it_surveys
 
 TYPE BBPT_BUPA_CATALOG_QUEST ,
ld_iv_with_catalog_model
 
 TYPE XFELD ,
ld_it_languages
 
 TYPE BBPT_BUPA_CATALOG_QUEST .


ld_is_bus_ei_main = 'Check type of data required'.
ld_it_venmap = 'Check type of data required'.
ld_iv_message = 'Check type of data required'.
ld_it_surveys = 'Check type of data required'.
ld_iv_with_catalog_model = 'Check type of data required'.
ld_it_languages = 'Check type of data required'.