SAP BAPI_CUSTOMEREXPINV_CREATEMUL Function Module for Agency Business: BAPI - Generate Expenses Settlement









BAPI_CUSTOMEREXPINV_CREATEMUL is a standard bapi customerexpinv createmul SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Agency Business: BAPI - Generate Expenses Settlement 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 bapi customerexpinv createmul FM, simply by entering the name BAPI_CUSTOMEREXPINV_CREATEMUL into the relevant SAP transaction such as SE37 or SE38.

Function Group: 2144
Program Name: SAPL2144
Main Program: SAPL2144
Appliation area: W
Release date: 10-Apr-2007
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_CUSTOMEREXPINV_CREATEMUL 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_CUSTOMEREXPINV_CREATEMUL'"Agency Business: BAPI - Generate Expenses Settlement
TABLES
   HEADDATA =  "Document Header Data (input)
*  ITEMTEXTIN =  "Item Texts (Input)
*  HEADTEXTOUT =  "Agency Business: Header Text For Change Case
*  ITEMTEXTOUT =  "Agency Business: Item Texts, Change Case
   ITEMDATA =  "Item Data (Input)
*  CONDITIONS =  "Conditions
*  HEADDATAOUT =  "Document Header Data (Output)
*  ITEMDATAOUT =  "Item data (output)
*  RETURN =  "Error Texts
*  EXTENSIONIN =  "Enhancements (Input)
*  EXTENSIONOUT =  "Enhancements (Output)
*  HEADTEXTIN =  "Header Texts (Input)
.



TABLES Parameters details for BAPI_CUSTOMEREXPINV_CREATEMUL

HEADDATA - Document Header Data (input)

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

ITEMTEXTIN - Item Texts (Input)

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

HEADTEXTOUT - Agency Business: Header Text For Change Case

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

ITEMTEXTOUT - Agency Business: Item Texts, Change Case

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

ITEMDATA - Item Data (Input)

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

CONDITIONS - Conditions

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

HEADDATAOUT - Document Header Data (Output)

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

ITEMDATAOUT - Item data (output)

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

RETURN - Error Texts

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

EXTENSIONIN - Enhancements (Input)

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

EXTENSIONOUT - Enhancements (Output)

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

HEADTEXTIN - Header Texts (Input)

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

Copy and paste ABAP code example for BAPI_CUSTOMEREXPINV_CREATEMUL 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_headdata  TYPE STANDARD TABLE OF BAPICSHEAD, "   
lt_itemtextin  TYPE STANDARD TABLE OF BAPIABITEMTEXT, "   
lt_headtextout  TYPE STANDARD TABLE OF BAPIABHEADCTEXT, "   
lt_itemtextout  TYPE STANDARD TABLE OF BAPIABITEMCTEXT, "   
lt_itemdata  TYPE STANDARD TABLE OF BAPICSITEM, "   
lt_conditions  TYPE STANDARD TABLE OF BAPICSCOND, "   
lt_headdataout  TYPE STANDARD TABLE OF BAPICSHEADO, "   
lt_itemdataout  TYPE STANDARD TABLE OF BAPICSITEMO, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_headtextin  TYPE STANDARD TABLE OF BAPIABHEADTEXT. "   

  CALL FUNCTION 'BAPI_CUSTOMEREXPINV_CREATEMUL'  "Agency Business: BAPI - Generate Expenses Settlement
    TABLES
         HEADDATA = lt_headdata
         ITEMTEXTIN = lt_itemtextin
         HEADTEXTOUT = lt_headtextout
         ITEMTEXTOUT = lt_itemtextout
         ITEMDATA = lt_itemdata
         CONDITIONS = lt_conditions
         HEADDATAOUT = lt_headdataout
         ITEMDATAOUT = lt_itemdataout
         RETURN = lt_return
         EXTENSIONIN = lt_extensionin
         EXTENSIONOUT = lt_extensionout
         HEADTEXTIN = lt_headtextin
. " BAPI_CUSTOMEREXPINV_CREATEMUL




ABAP code using 7.40 inline data declarations to call FM BAPI_CUSTOMEREXPINV_CREATEMUL

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!