SAP BAPI_INVOICEEC_XML_SEND Function Module for









BAPI_INVOICEEC_XML_SEND is a standard bapi invoiceec xml send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bapi invoiceec xml send FM, simply by entering the name BAPI_INVOICEEC_XML_SEND into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_BUS2205
Program Name: SAPLBBP_BUS2205
Main Program: SAPLBBP_BUS2205
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_INVOICEEC_XML_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 'BAPI_INVOICEEC_XML_SEND'"
EXPORTING
INV_HEADER = "Header Data for Invoice
* SHIP_FROM_ADDRESS = "Ship-From Address
* TESTRUN = "Switch to Simulation Session for Write BAPIs
* INV_HEADER_CUST = "
VENDOR = "Vendor
* VENDOR_COM_ADDRESS = "Communication Address of Vendor
* VENDOR_CONTACT = "Contact Person at Vendor
* BILL_TO_PARTY = "Sold-To Party
* BILL_TO_PARTY_CONTACT = "Contact Person at Ordering party
* SERVICE_PROVIDER = "Service Provider
* SHIP_TO_ADDRESS = "Ship-to Address

TABLES
I_INV_ITEMS = "Item Data
E_RETURN = "Return Structure
I_INV_ITEMS_CUST = "Invoice Item Customer Enhancement (vendor detail)
I_INV_TAXES = "Taxes
I_INV_SHIPCOST = "Shipment Costs
* I_BILL_TO_PARTY_CONTACT = "Requester at Item Level
* I_SERVICE_PROVIDER = "Service Provider at Item Level
* I_SHIP_TO_ADDRESS = "Ship-To Address at Item Level
* I_SHIP_FROM_ADDRESS = "Ship-From Address at Item Level
E_XML_DATA = "XML Return
.



IMPORTING Parameters details for BAPI_INVOICEEC_XML_SEND

INV_HEADER - Header Data for Invoice

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

SHIP_FROM_ADDRESS - Ship-From Address

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

TESTRUN - Switch to Simulation Session for Write BAPIs

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

INV_HEADER_CUST -

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

VENDOR - Vendor

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

VENDOR_COM_ADDRESS - Communication Address of Vendor

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

VENDOR_CONTACT - Contact Person at Vendor

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

BILL_TO_PARTY - Sold-To Party

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

BILL_TO_PARTY_CONTACT - Contact Person at Ordering party

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

SERVICE_PROVIDER - Service Provider

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

SHIP_TO_ADDRESS - Ship-to Address

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

TABLES Parameters details for BAPI_INVOICEEC_XML_SEND

I_INV_ITEMS - Item Data

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

E_RETURN - Return Structure

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

I_INV_ITEMS_CUST - Invoice Item Customer Enhancement (vendor detail)

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

I_INV_TAXES - Taxes

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

I_INV_SHIPCOST - Shipment Costs

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

I_BILL_TO_PARTY_CONTACT - Requester at Item Level

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

I_SERVICE_PROVIDER - Service Provider at Item Level

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

I_SHIP_TO_ADDRESS - Ship-To Address at Item Level

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

I_SHIP_FROM_ADDRESS - Ship-From Address at Item Level

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

E_XML_DATA - XML Return

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

Copy and paste ABAP code example for BAPI_INVOICEEC_XML_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_inv_header  TYPE BAPI_INV_HEADER_VD, "   
lt_i_inv_items  TYPE STANDARD TABLE OF BAPI_INV_ITEM_VD, "   
lt_e_return  TYPE STANDARD TABLE OF BAPI_XMLRET, "   
lv_ship_from_address  TYPE BAPIADDR3, "   
lv_testrun  TYPE BBPS_BAPI2091-TESTRUN, "   
lv_inv_header_cust  TYPE BAPI_INV_HEADER_CUST_VD, "   
lt_i_inv_items_cust  TYPE STANDARD TABLE OF BAPI_INV_ITEM_CUST_VD, "   
lv_vendor  TYPE BAPI_BUP_S, "   
lt_i_inv_taxes  TYPE STANDARD TABLE OF BAPI_IVTAX_D, "   
lt_i_inv_shipcost  TYPE STANDARD TABLE OF BAPI_IVSHP_D, "   
lv_vendor_com_address  TYPE BAPI_PARTNER_COMADR, "   
lv_vendor_contact  TYPE BAPI_BUP_S, "   
lt_i_bill_to_party_contact  TYPE STANDARD TABLE OF BAPI_BUP_S, "   
lv_bill_to_party  TYPE BAPI_BUP_S, "   
lt_i_service_provider  TYPE STANDARD TABLE OF BAPI_BUP_S, "   
lt_i_ship_to_address  TYPE STANDARD TABLE OF BAPI_BUP_S, "   
lv_bill_to_party_contact  TYPE BAPI_BUP_S, "   
lv_service_provider  TYPE BAPI_BUP_S, "   
lt_i_ship_from_address  TYPE STANDARD TABLE OF BAPI_BUP_S, "   
lt_e_xml_data  TYPE STANDARD TABLE OF BAPI_XMLDATA, "   
lv_ship_to_address  TYPE BAPIADDR3. "   

  CALL FUNCTION 'BAPI_INVOICEEC_XML_SEND'  "
    EXPORTING
         INV_HEADER = lv_inv_header
         SHIP_FROM_ADDRESS = lv_ship_from_address
         TESTRUN = lv_testrun
         INV_HEADER_CUST = lv_inv_header_cust
         VENDOR = lv_vendor
         VENDOR_COM_ADDRESS = lv_vendor_com_address
         VENDOR_CONTACT = lv_vendor_contact
         BILL_TO_PARTY = lv_bill_to_party
         BILL_TO_PARTY_CONTACT = lv_bill_to_party_contact
         SERVICE_PROVIDER = lv_service_provider
         SHIP_TO_ADDRESS = lv_ship_to_address
    TABLES
         I_INV_ITEMS = lt_i_inv_items
         E_RETURN = lt_e_return
         I_INV_ITEMS_CUST = lt_i_inv_items_cust
         I_INV_TAXES = lt_i_inv_taxes
         I_INV_SHIPCOST = lt_i_inv_shipcost
         I_BILL_TO_PARTY_CONTACT = lt_i_bill_to_party_contact
         I_SERVICE_PROVIDER = lt_i_service_provider
         I_SHIP_TO_ADDRESS = lt_i_ship_to_address
         I_SHIP_FROM_ADDRESS = lt_i_ship_from_address
         E_XML_DATA = lt_e_xml_data
. " BAPI_INVOICEEC_XML_SEND




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

 
 
 
 
"SELECT single TESTRUN FROM BBPS_BAPI2091 INTO @DATA(ld_testrun).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!