SAP Function Modules

META_CTINFO_SEND SAP Function module - Versenden Kontrakt Legal Document







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

Associated Function Group: BBP_BD_META_BAPIS_PART2
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM META_CTINFO_SEND - META CTINFO SEND





CALL FUNCTION 'META_CTINFO_SEND' "Versenden Kontrakt Legal Document
  EXPORTING
    iv_system_type =            " bbp_system_type  Systemart
    iv_send_changed_data_only =   " xfeld       Feld zum Ankreuzen
    is_header =                 " bbp_pds_ctr_header_d  Schnittstelle Kopf-Daten Kontrakt GetDetail-Fall
    it_attach =                 " bbpt_pds_att_t  KW-Anlagen inkl. Dokument
    it_conditions =             " bbpt_pd_cnd_d  Table Type Master Conditions
  TABLES
    it_item =                   " bbp_pds_ctr_item_d  Schnittstelle Positions-Daten Kontrakt GetDetail-Fall
*   it_partner =                " bbp_pds_partner  Geschäftspartner
*   it_longtext =               " bbp_pds_longtext  Langtexte zum Procurement Document
*   it_orgdata =                " bbp_pds_org   Org-Daten
    et_messages =               " bbp_pds_messages  Fehlermeldungen zu einer PD-Methode
    .  "  META_CTINFO_SEND

ABAP code example for Function Module META_CTINFO_SEND





The ABAP code below is a full code listing to execute function module META_CTINFO_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:
it_it_item  TYPE STANDARD TABLE OF BBP_PDS_CTR_ITEM_D,"TABLES PARAM
wa_it_item  LIKE LINE OF it_it_item ,
it_it_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER,"TABLES PARAM
wa_it_partner  LIKE LINE OF it_it_partner ,
it_it_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT,"TABLES PARAM
wa_it_longtext  LIKE LINE OF it_it_longtext ,
it_it_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG,"TABLES PARAM
wa_it_orgdata  LIKE LINE OF it_it_orgdata ,
it_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES,"TABLES PARAM
wa_et_messages  LIKE LINE OF it_et_messages .

DATA(ld_iv_system_type) = '20210129'.
DATA(ld_iv_send_changed_data_only) = 'some text here'.
DATA(ld_is_header) = 'some text here'.
DATA(ld_it_attach) = 'some text here'.
DATA(ld_it_conditions) = 'some text here'.

"populate fields of struture and append to itab
append wa_it_item to it_it_item.

"populate fields of struture and append to itab
append wa_it_partner to it_it_partner.

"populate fields of struture and append to itab
append wa_it_longtext to it_it_longtext.

"populate fields of struture and append to itab
append wa_it_orgdata to it_it_orgdata.

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages. . CALL FUNCTION 'META_CTINFO_SEND' EXPORTING iv_system_type = ld_iv_system_type iv_send_changed_data_only = ld_iv_send_changed_data_only is_header = ld_is_header it_attach = ld_it_attach it_conditions = ld_it_conditions TABLES it_item = it_it_item * it_partner = it_it_partner * it_longtext = it_it_longtext * it_orgdata = it_it_orgdata et_messages = it_et_messages . " META_CTINFO_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_iv_system_type  TYPE BBP_SYSTEM_TYPE ,
it_it_item  TYPE STANDARD TABLE OF BBP_PDS_CTR_ITEM_D ,
wa_it_item  LIKE LINE OF it_it_item,
ld_iv_send_changed_data_only  TYPE XFELD ,
it_it_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER ,
wa_it_partner  LIKE LINE OF it_it_partner,
ld_is_header  TYPE BBP_PDS_CTR_HEADER_D ,
it_it_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT ,
wa_it_longtext  LIKE LINE OF it_it_longtext,
ld_it_attach  TYPE BBPT_PDS_ATT_T ,
it_it_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG ,
wa_it_orgdata  LIKE LINE OF it_it_orgdata,
ld_it_conditions  TYPE BBPT_PD_CND_D ,
it_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_et_messages  LIKE LINE OF it_et_messages.

ld_iv_system_type = '20210129'.

"populate fields of struture and append to itab
append wa_it_item to it_it_item.
ld_iv_send_changed_data_only = 'some text here'.

"populate fields of struture and append to itab
append wa_it_partner to it_it_partner.
ld_is_header = 'some text here'.

"populate fields of struture and append to itab
append wa_it_longtext to it_it_longtext.
ld_it_attach = 'some text here'.

"populate fields of struture and append to itab
append wa_it_orgdata to it_it_orgdata.
ld_it_conditions = 'some text here'.

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

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name META_CTINFO_SEND or its description.