SAP BBP_SAPXML1_RFQ_SEND Function Module for SAPXML1 Treiber zu META_PO_SEND









BBP_SAPXML1_RFQ_SEND is a standard bbp sapxml1 rfq 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 SAPXML1 Treiber zu META_PO_SEND 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 rfq send FM, simply by entering the name BBP_SAPXML1_RFQ_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_RFQ_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_RFQ_SEND'"SAPXML1 Treiber zu META_PO_SEND
  EXPORTING
   IS_HEADER =  "Kopf-Daten Ausschreibung GetDetail-Fall + Externe Sicht
   IT_STATUS =  "Enriched Status
   IT_DYN_ATTR =  "Temporrer Tabellentyp fr Dynamische Attribute
   IT_HCF =  "Tab.artige Kunden- und Solutionfelder am Ausschreibungskopf
   IT_ICF =  "Tab. Kunden- und Solutionfelder an der Ausschreibungspos.
*  IV_NO_SEND =  "Feld zum Ankreuzen
   IV_ACTION_CODE =  "Steuerung Anlegen, ndern und Lschen von Objekten
   IT_ITEM =  "Tabelle zu BBPS_PDEXT_BID_ITEM_D
   IT_ORGDATA =  "Tabellentyp Org-Daten
   IT_TEXT =  "Langtexte
   IT_SDLN =  "Schedule Line + Externe Sicht
   IT_PARTNER =  "Geschftspartner
   IT_ATTACH =  "
*  IT_EXCHRATE =  "Tabellentyp fr Umrechnungskurs-Daten
   IT_CONDITIONS =  "Tabellentyp Stammkonditionen (Detail) + Externe Sicht

 IMPORTING
   EV_XML_STRING =  "
   ES_RFQ_CREATE_REQUEST =  "
   ES_RFQ_CHANGE_REQUEST =  "Proxy Structure (generated)
   ES_RFQ_CANCEL_REQUEST =  "
   ES_RFQ_NOTIFICATION_REQUEST =  "
.



IMPORTING Parameters details for BBP_SAPXML1_RFQ_SEND

IS_HEADER - Kopf-Daten Ausschreibung GetDetail-Fall + Externe Sicht

Data type: BBPS_PDEXT_BID_HEADER_D
Optional: No
Call by Reference: Yes

IT_STATUS - Enriched Status

Data type: BBPT_PDEXT_STATUS
Optional: No
Call by Reference: Yes

IT_DYN_ATTR - Temporrer Tabellentyp fr Dynamische Attribute

Data type: BBPT_PDS_DYNATTRIBUTE
Optional: No
Call by Reference: Yes

IT_HCF - Tab.artige Kunden- und Solutionfelder am Ausschreibungskopf

Data type: BBPT_PDS_HCF_BID
Optional: No
Call by Reference: Yes

IT_ICF - Tab. Kunden- und Solutionfelder an der Ausschreibungspos.

Data type: BBPT_PDS_ICF_BID
Optional: No
Call by Reference: Yes

IV_NO_SEND - Feld zum Ankreuzen

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IV_ACTION_CODE - Steuerung Anlegen, ndern und Lschen von Objekten

Data type: BBP_ACTION_CODE
Optional: No
Call by Reference: Yes

IT_ITEM - Tabelle zu BBPS_PDEXT_BID_ITEM_D

Data type: BBPT_PDEXT_BID_ITEM_D
Optional: No
Call by Reference: Yes

IT_ORGDATA - Tabellentyp Org-Daten

Data type: BBPT_PDEXT_ORG
Optional: No
Call by Reference: Yes

IT_TEXT - Langtexte

Data type: BBPT_PDEXT_LONGTEXT
Optional: No
Call by Reference: Yes

IT_SDLN - Schedule Line + Externe Sicht

Data type: BBPT_PDEXT_SDLN
Optional: No
Call by Reference: Yes

IT_PARTNER - Geschftspartner

Data type: BBPT_PDEXT_PARTNER
Optional: No
Call by Reference: Yes

IT_ATTACH -

Data type: BBPT_PDEXT_ATTACH
Optional: No
Call by Reference: Yes

IT_EXCHRATE - Tabellentyp fr Umrechnungskurs-Daten

Data type: BBPT_PDEXT_EXR
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_CONDITIONS - Tabellentyp Stammkonditionen (Detail) + Externe Sicht

Data type: BBPT_PDEXT_CND_D
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for BBP_SAPXML1_RFQ_SEND

EV_XML_STRING -

Data type: STRING
Optional: No
Call by Reference: Yes

ES_RFQ_CREATE_REQUEST -

Data type: BBPX1_RFQREQUEST
Optional: No
Call by Reference: Yes

ES_RFQ_CHANGE_REQUEST - Proxy Structure (generated)

Data type: BBPX1_RFQCHANGE_REQUEST
Optional: No
Call by Reference: Yes

ES_RFQ_CANCEL_REQUEST -

Data type: BBPX1_RFQCANCELLATION_REQUEST
Optional: No
Call by Reference: Yes

ES_RFQ_NOTIFICATION_REQUEST -

Data type: BBPX1_RFQRESULT_NOTIFICATION
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_SAPXML1_RFQ_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_is_header  TYPE BBPS_PDEXT_BID_HEADER_D, "   
lv_ev_xml_string  TYPE STRING, "   
lv_it_status  TYPE BBPT_PDEXT_STATUS, "   
lv_it_dyn_attr  TYPE BBPT_PDS_DYNATTRIBUTE, "   
lv_it_hcf  TYPE BBPT_PDS_HCF_BID, "   
lv_it_icf  TYPE BBPT_PDS_ICF_BID, "   
lv_iv_no_send  TYPE XFELD, "   
lv_iv_action_code  TYPE BBP_ACTION_CODE, "   
lv_it_item  TYPE BBPT_PDEXT_BID_ITEM_D, "   
lv_es_rfq_create_request  TYPE BBPX1_RFQREQUEST, "   
lv_it_orgdata  TYPE BBPT_PDEXT_ORG, "   
lv_es_rfq_change_request  TYPE BBPX1_RFQCHANGE_REQUEST, "   
lv_it_text  TYPE BBPT_PDEXT_LONGTEXT, "   
lv_es_rfq_cancel_request  TYPE BBPX1_RFQCANCELLATION_REQUEST, "   
lv_it_sdln  TYPE BBPT_PDEXT_SDLN, "   
lv_es_rfq_notification_request  TYPE BBPX1_RFQRESULT_NOTIFICATION, "   
lv_it_partner  TYPE BBPT_PDEXT_PARTNER, "   
lv_it_attach  TYPE BBPT_PDEXT_ATTACH, "   
lv_it_exchrate  TYPE BBPT_PDEXT_EXR, "   
lv_it_conditions  TYPE BBPT_PDEXT_CND_D. "   

  CALL FUNCTION 'BBP_SAPXML1_RFQ_SEND'  "SAPXML1 Treiber zu META_PO_SEND
    EXPORTING
         IS_HEADER = lv_is_header
         IT_STATUS = lv_it_status
         IT_DYN_ATTR = lv_it_dyn_attr
         IT_HCF = lv_it_hcf
         IT_ICF = lv_it_icf
         IV_NO_SEND = lv_iv_no_send
         IV_ACTION_CODE = lv_iv_action_code
         IT_ITEM = lv_it_item
         IT_ORGDATA = lv_it_orgdata
         IT_TEXT = lv_it_text
         IT_SDLN = lv_it_sdln
         IT_PARTNER = lv_it_partner
         IT_ATTACH = lv_it_attach
         IT_EXCHRATE = lv_it_exchrate
         IT_CONDITIONS = lv_it_conditions
    IMPORTING
         EV_XML_STRING = lv_ev_xml_string
         ES_RFQ_CREATE_REQUEST = lv_es_rfq_create_request
         ES_RFQ_CHANGE_REQUEST = lv_es_rfq_change_request
         ES_RFQ_CANCEL_REQUEST = lv_es_rfq_cancel_request
         ES_RFQ_NOTIFICATION_REQUEST = lv_es_rfq_notification_request
. " BBP_SAPXML1_RFQ_SEND




ABAP code using 7.40 inline data declarations to call FM BBP_SAPXML1_RFQ_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!