SAP BBP_SAPXML1_CTR_CAT_SEND Function Module for Change contract
BBP_SAPXML1_CTR_CAT_SEND is a standard bbp sapxml1 ctr cat send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change contract processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for bbp sapxml1 ctr cat send FM, simply by entering the name BBP_SAPXML1_CTR_CAT_SEND into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BD_DRIVER_SAPXML1
Program Name: SAPLBBP_BD_DRIVER_SAPXML1
Main Program: SAPLBBP_BD_DRIVER_SAPXML1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_SAPXML1_CTR_CAT_SEND pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'BBP_SAPXML1_CTR_CAT_SEND'"Change contract.
EXPORTING
IV_LOGICAL_SYSTEM = "Logisches System
IT_DIST = "Kontrakt Verteilungsdaten
* IT_TOL = "Tabelle zu BBPS_PDEXT_TOL
* IV_NO_SEND = "Feld zum Ankreuzen
IV_SRC_GUID = "Globally Unique Identifier
IS_HEADER = "Kopf-Daten Kontrakt GetDetail-Fall + Externe Sicht
IT_ITEMS = "Enriched Item
IT_ORG_DATA = "Enriched Orgdata
* IT_TEXT = "Enriched Longtext
* IT_ATTACH = "Enriched Attachment
IT_PARTNER = "Enriched Partner
IT_STATUS = "Status
IMPORTING
ET_MESSAGES = "Fehlermeldungen
EV_XML_STRING = "
ES_CATALOG_REQUEST = "Proxy Structure (generated)
TABLES
ET_CONTROL_RECORD = "Steuersatz für META-BAPI-Steuerung
IMPORTING Parameters details for BBP_SAPXML1_CTR_CAT_SEND
IV_LOGICAL_SYSTEM - Logisches System
Data type: LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
IT_DIST - Kontrakt Verteilungsdaten
Data type: BBPT_PD_DISOptional: No
Call by Reference: No ( called with pass by value option)
IT_TOL - Tabelle zu BBPS_PDEXT_TOL
Data type: BBPT_PDEXT_TOLOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_SEND - Feld zum Ankreuzen
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_SRC_GUID - Globally Unique Identifier
Data type: BBP_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IS_HEADER - Kopf-Daten Kontrakt GetDetail-Fall + Externe Sicht
Data type: BBPS_PDEXT_CTR_HEADER_DOptional: No
Call by Reference: No ( called with pass by value option)
IT_ITEMS - Enriched Item
Data type: BBPT_PDEXT_CTR_ITEM_DOptional: No
Call by Reference: No ( called with pass by value option)
IT_ORG_DATA - Enriched Orgdata
Data type: BBPT_PDEXT_ORGOptional: No
Call by Reference: No ( called with pass by value option)
IT_TEXT - Enriched Longtext
Data type: BBPT_PDEXT_LONGTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ATTACH - Enriched Attachment
Data type: BBPT_PDEXT_ATTACHOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_PARTNER - Enriched Partner
Data type: BBPT_PDEXT_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IT_STATUS - Status
Data type: BBPT_PDS_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_SAPXML1_CTR_CAT_SEND
ET_MESSAGES - Fehlermeldungen
Data type: BBPT_PD_MESSAGESOptional: No
Call by Reference: Yes
EV_XML_STRING -
Data type: STRINGOptional: No
Call by Reference: Yes
ES_CATALOG_REQUEST - Proxy Structure (generated)
Data type: BBPX1_CTLG_TRANS_STROptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_SAPXML1_CTR_CAT_SEND
ET_CONTROL_RECORD - Steuersatz für META-BAPI-Steuerung
Data type: BBP_CONTROL_RECORDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_SAPXML1_CTR_CAT_SEND Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_et_messages | TYPE BBPT_PD_MESSAGES, " | |||
| lt_et_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, " | |||
| lv_iv_logical_system | TYPE LOGSYS, " | |||
| lv_it_dist | TYPE BBPT_PD_DIS, " | |||
| lv_it_tol | TYPE BBPT_PDEXT_TOL, " | |||
| lv_iv_no_send | TYPE XFELD, " | |||
| lv_iv_src_guid | TYPE BBP_GUID, " | |||
| lv_ev_xml_string | TYPE STRING, " | |||
| lv_is_header | TYPE BBPS_PDEXT_CTR_HEADER_D, " | |||
| lv_es_catalog_request | TYPE BBPX1_CTLG_TRANS_STR, " | |||
| lv_it_items | TYPE BBPT_PDEXT_CTR_ITEM_D, " | |||
| lv_it_org_data | TYPE BBPT_PDEXT_ORG, " | |||
| lv_it_text | TYPE BBPT_PDEXT_LONGTEXT, " | |||
| lv_it_attach | TYPE BBPT_PDEXT_ATTACH, " | |||
| lv_it_partner | TYPE BBPT_PDEXT_PARTNER, " | |||
| lv_it_status | TYPE BBPT_PDS_STATUS. " |
|   CALL FUNCTION 'BBP_SAPXML1_CTR_CAT_SEND' "Change contract |
| EXPORTING | ||
| IV_LOGICAL_SYSTEM | = lv_iv_logical_system | |
| IT_DIST | = lv_it_dist | |
| IT_TOL | = lv_it_tol | |
| IV_NO_SEND | = lv_iv_no_send | |
| IV_SRC_GUID | = lv_iv_src_guid | |
| IS_HEADER | = lv_is_header | |
| IT_ITEMS | = lv_it_items | |
| IT_ORG_DATA | = lv_it_org_data | |
| IT_TEXT | = lv_it_text | |
| IT_ATTACH | = lv_it_attach | |
| IT_PARTNER | = lv_it_partner | |
| IT_STATUS | = lv_it_status | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| EV_XML_STRING | = lv_ev_xml_string | |
| ES_CATALOG_REQUEST | = lv_es_catalog_request | |
| TABLES | ||
| ET_CONTROL_RECORD | = lt_et_control_record | |
| . " BBP_SAPXML1_CTR_CAT_SEND | ||
ABAP code using 7.40 inline data declarations to call FM BBP_SAPXML1_CTR_CAT_SEND
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects