SAP BBP_SAPXML1_DER_SEND Function Module for SAPXML1 Treiber zu META_PO_SEND









BBP_SAPXML1_DER_SEND is a standard bbp sapxml1 der 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 der send FM, simply by entering the name BBP_SAPXML1_DER_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_DER_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_DER_SEND'"SAPXML1 Treiber zu META_PO_SEND
EXPORTING
IS_HEADER = "Schnittstelle Kopf-Daten Bestellung GetDetail-Fall
IT_ATTACH = "KW-Anlagen inkl. Dokument
* IV_NO_SEND = "Nicht versenden

IMPORTING
EV_XML_STRING = "
ES_DER = "Proxy Structure (generated)

TABLES
IT_ITEM = "Schnittstelle Positions-Daten Bestellung GetDetail-Fall
IT_PARTNER = "Geschäftspartner
* IT_LONGTEXT = "Langtexte zum Procurement Document
* IT_LIMIT = "Wertlimit
IT_SDLN = "Schedule Line + Externe Sicht
.



IMPORTING Parameters details for BBP_SAPXML1_DER_SEND

IS_HEADER - Schnittstelle Kopf-Daten Bestellung GetDetail-Fall

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

IT_ATTACH - KW-Anlagen inkl. Dokument

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

IV_NO_SEND - Nicht versenden

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

EXPORTING Parameters details for BBP_SAPXML1_DER_SEND

EV_XML_STRING -

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

ES_DER - Proxy Structure (generated)

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

TABLES Parameters details for BBP_SAPXML1_DER_SEND

IT_ITEM - Schnittstelle Positions-Daten Bestellung GetDetail-Fall

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

IT_PARTNER - Geschäftspartner

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

IT_LONGTEXT - Langtexte zum Procurement Document

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

IT_LIMIT - Wertlimit

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

IT_SDLN - Schedule Line + Externe Sicht

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

Copy and paste ABAP code example for BBP_SAPXML1_DER_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:
lt_it_item  TYPE STANDARD TABLE OF BBPS_PDEXT_PO_ITEM_D, "   
lv_is_header  TYPE BBPS_PDEXT_PO_HEADER_D, "   
lv_ev_xml_string  TYPE STRING, "   
lv_es_der  TYPE I, "   
lv_it_attach  TYPE BBPT_PDEXT_ATTACH, "   
lt_it_partner  TYPE STANDARD TABLE OF BBPS_PDEXT_PARTNER, "   
lv_iv_no_send  TYPE XFELD, "   
lt_it_longtext  TYPE STANDARD TABLE OF BBPS_PDEXT_LONGTEXT, "   
lt_it_limit  TYPE STANDARD TABLE OF BBPS_PDEXT_LIMIT, "   
lt_it_sdln  TYPE STANDARD TABLE OF BBPS_PDEXT_SDLN. "   

  CALL FUNCTION 'BBP_SAPXML1_DER_SEND'  "SAPXML1 Treiber zu META_PO_SEND
    EXPORTING
         IS_HEADER = lv_is_header
         IT_ATTACH = lv_it_attach
         IV_NO_SEND = lv_iv_no_send
    IMPORTING
         EV_XML_STRING = lv_ev_xml_string
         ES_DER = lv_es_der
    TABLES
         IT_ITEM = lt_it_item
         IT_PARTNER = lt_it_partner
         IT_LONGTEXT = lt_it_longtext
         IT_LIMIT = lt_it_limit
         IT_SDLN = lt_it_sdln
. " BBP_SAPXML1_DER_SEND




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