SAP BAPI_INVOICEEC_XML_RESP_SEND Function Module for









BAPI_INVOICEEC_XML_RESP_SEND is a standard bapi invoiceec xml resp 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 resp send FM, simply by entering the name BAPI_INVOICEEC_XML_RESP_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_RESP_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_RESP_SEND'"
  EXPORTING
   I_INVRESP_HEADER =  "Invoice Response Header
   I_BILL_TO_PARTY =  "Business Partner (Bapi Send)
*  I_BILL_TO_PARTY_CONTACT =  "Business Partner (Bapi Send)
   I_INVOICING_PARTY =  "Business Partner (Bapi Send)
*  I_INVOICING_PARTY_CONTACT =  "Business Partner (Bapi Send)
   VENDOR_COM_ADDRESS =  "Communication Address of Business Partner

TABLES
*  I_INVRESP_ITEMS =  "Item Data - Invoice Response
*  I_INVRESP_TEXT =  "BAPI Structure for Long Text
*  I_INVRESP_ATTACH =  "Attachments (GetDetail)
   E_RETURN =  "Return Structure for XML Dispatch
.



IMPORTING Parameters details for BAPI_INVOICEEC_XML_RESP_SEND

I_INVRESP_HEADER - Invoice Response Header

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

I_BILL_TO_PARTY - Business Partner (Bapi Send)

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

I_BILL_TO_PARTY_CONTACT - Business Partner (Bapi Send)

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

I_INVOICING_PARTY - Business Partner (Bapi Send)

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

I_INVOICING_PARTY_CONTACT - Business Partner (Bapi Send)

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

VENDOR_COM_ADDRESS - Communication Address of Business Partner

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

TABLES Parameters details for BAPI_INVOICEEC_XML_RESP_SEND

I_INVRESP_ITEMS - Item Data - Invoice Response

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

I_INVRESP_TEXT - BAPI Structure for Long Text

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

I_INVRESP_ATTACH - Attachments (GetDetail)

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

E_RETURN - Return Structure for XML Dispatch

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

Copy and paste ABAP code example for BAPI_INVOICEEC_XML_RESP_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_i_invresp_items  TYPE STANDARD TABLE OF BAPI_INVRESPONSE_ITEM, "   
lv_i_invresp_header  TYPE BAPI_INVRESPONSE_HEADER, "   
lt_i_invresp_text  TYPE STANDARD TABLE OF BAPI_TEXT_I, "   
lv_i_bill_to_party  TYPE BAPI_BUP_S, "   
lt_i_invresp_attach  TYPE STANDARD TABLE OF BAPI_ATT_BC, "   
lv_i_bill_to_party_contact  TYPE BAPI_BUP_S, "   
lt_e_return  TYPE STANDARD TABLE OF BAPI_XMLRET, "   
lv_i_invoicing_party  TYPE BAPI_BUP_S, "   
lv_i_invoicing_party_contact  TYPE BAPI_BUP_S, "   
lv_vendor_com_address  TYPE BAPI_PARTNER_COMADR. "   

  CALL FUNCTION 'BAPI_INVOICEEC_XML_RESP_SEND'  "
    EXPORTING
         I_INVRESP_HEADER = lv_i_invresp_header
         I_BILL_TO_PARTY = lv_i_bill_to_party
         I_BILL_TO_PARTY_CONTACT = lv_i_bill_to_party_contact
         I_INVOICING_PARTY = lv_i_invoicing_party
         I_INVOICING_PARTY_CONTACT = lv_i_invoicing_party_contact
         VENDOR_COM_ADDRESS = lv_vendor_com_address
    TABLES
         I_INVRESP_ITEMS = lt_i_invresp_items
         I_INVRESP_TEXT = lt_i_invresp_text
         I_INVRESP_ATTACH = lt_i_invresp_attach
         E_RETURN = lt_e_return
. " BAPI_INVOICEEC_XML_RESP_SEND




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