SAP META_SUSINV_SEND Function Module for Send (ERS) Invoice









META_SUSINV_SEND is a standard meta susinv 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 Send (ERS) Invoice 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 meta susinv send FM, simply by entering the name META_SUSINV_SEND into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_BD_META_BAPIS_PART2
Program Name: SAPLBBP_BD_META_BAPIS_PART2
Main Program: SAPLBBP_BD_META_BAPIS_PART2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function META_SUSINV_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 'META_SUSINV_SEND'"Send (ERS) Invoice
  EXPORTING
*  IV_LOGICAL_SYSTEM =  "Logical system
*  IT_ATTACH =  "KW-Anlagen inkl. Dokument
*  IT_STATUS =  "Status
*  IV_SYSTEM_TYPE =  "Systemart
   IS_HEADER =  "Schnittstelle Kopf-Daten Rechnung GetDetail-Fall
   IT_ITEM =  "Invoice item
*  IT_ITEM_REL =  "Positionsverknüpfungen Typ Invoice Hub
*  IT_PARTNER =  "Geschäftspartner
*  IT_FREIGHT =  "Frachtkosten
*  IT_TAX =  "Steuern
*  IT_LONGTEXT =  "Langtexte

 IMPORTING
   ET_MESSAGES =  "Fehlermeldungen
.



IMPORTING Parameters details for META_SUSINV_SEND

IV_LOGICAL_SYSTEM - Logical system

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

IT_ATTACH - KW-Anlagen inkl. Dokument

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

IT_STATUS - Status

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

IV_SYSTEM_TYPE - Systemart

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

IS_HEADER - Schnittstelle Kopf-Daten Rechnung GetDetail-Fall

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

IT_ITEM - Invoice item

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

IT_ITEM_REL - Positionsverknüpfungen Typ Invoice Hub

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

IT_PARTNER - Geschäftspartner

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

IT_FREIGHT - Frachtkosten

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

IT_TAX - Steuern

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

IT_LONGTEXT - Langtexte

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

EXPORTING Parameters details for META_SUSINV_SEND

ET_MESSAGES - Fehlermeldungen

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

Copy and paste ABAP code example for META_SUSINV_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, "   
lv_iv_logical_system  TYPE BBP_BACKEND_DEST-LOG_SYS, "   
lv_it_attach  TYPE BBPT_PD_ATT_T, "   
lv_it_status  TYPE BBPT_PD_STATUS, "   
lv_iv_system_type  TYPE BBP_SYSTEM_TYPE, "   
lv_is_header  TYPE BBP_PDS_SUSINV_HEADER_D, "   
lv_it_item  TYPE BBPT_PD_SUSINV_ITEM_D, "   
lv_it_item_rel  TYPE BBPT_PD_IVHUB_IREL, "   
lv_it_partner  TYPE BBPT_PD_PARTNER, "   
lv_it_freight  TYPE BBPT_PD_FREIGHT, "   
lv_it_tax  TYPE BBPT_PD_TAX, "   
lv_it_longtext  TYPE BBPT_PD_LONGTEXT. "   

  CALL FUNCTION 'META_SUSINV_SEND'  "Send (ERS) Invoice
    EXPORTING
         IV_LOGICAL_SYSTEM = lv_iv_logical_system
         IT_ATTACH = lv_it_attach
         IT_STATUS = lv_it_status
         IV_SYSTEM_TYPE = lv_iv_system_type
         IS_HEADER = lv_is_header
         IT_ITEM = lv_it_item
         IT_ITEM_REL = lv_it_item_rel
         IT_PARTNER = lv_it_partner
         IT_FREIGHT = lv_it_freight
         IT_TAX = lv_it_tax
         IT_LONGTEXT = lv_it_longtext
    IMPORTING
         ET_MESSAGES = lv_et_messages
. " META_SUSINV_SEND




ABAP code using 7.40 inline data declarations to call FM META_SUSINV_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 LOG_SYS FROM BBP_BACKEND_DEST INTO @DATA(ld_iv_logical_system).
 
 
 
 
 
 
 
 
 
 
 


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!