SAP BAPI_BILLDOC_CREATEMULTIPLE Function Module for BAPI for Billing document Create









BAPI_BILLDOC_CREATEMULTIPLE is a standard bapi billdoc createmultiple SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI for Billing document Create 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 billdoc createmultiple FM, simply by entering the name BAPI_BILLDOC_CREATEMULTIPLE into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_BILLDOC_CREATEMULTIPLE 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_BILLDOC_CREATEMULTIPLE'"BAPI for Billing document Create
  EXPORTING
*  TESTRUN = ' ' "Activate Simulation Mode
*  CFCVALIDATION = ' ' "Run Plausibility Checks

TABLES
   HEADERS =  "Header (External Billing Doc.)
*  ITEMS =  "Items (External Billing Doc.)
*  TAXITEMS =  "Tax Items (External Billing Doc.)
*  ADDITEMS =  "Additional Items (External Billing Doc.)
*  EXTENSIONIN =  "ExtensionIn
*  EXTENSIONOUT =  "ExtensionOut
*  BAPI_BILLDOCNUMBER =  "External or Internal Billing Doc. Number
   RETURN =  "Returns
.



IMPORTING Parameters details for BAPI_BILLDOC_CREATEMULTIPLE

TESTRUN - Activate Simulation Mode

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

CFCVALIDATION - Run Plausibility Checks

Data type: BAPI_AUX_INV-CFCVALIDATION
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_BILLDOC_CREATEMULTIPLE

HEADERS - Header (External Billing Doc.)

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

ITEMS - Items (External Billing Doc.)

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

TAXITEMS - Tax Items (External Billing Doc.)

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

ADDITEMS - Additional Items (External Billing Doc.)

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

EXTENSIONIN - ExtensionIn

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

EXTENSIONOUT - ExtensionOut

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

BAPI_BILLDOCNUMBER - External or Internal Billing Doc. Number

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

RETURN - Returns

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

Copy and paste ABAP code example for BAPI_BILLDOC_CREATEMULTIPLE 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_headers  TYPE STANDARD TABLE OF BAPI_EXTDOC_H, "   
lv_testrun  TYPE BAPI_AUX_INV-TESTRUN, "   SPACE
lt_items  TYPE STANDARD TABLE OF BAPI_EXTDOC_I, "   
lv_cfcvalidation  TYPE BAPI_AUX_INV-CFCVALIDATION, "   SPACE
lt_taxitems  TYPE STANDARD TABLE OF BAPI_EXTDOC_T, "   
lt_additems  TYPE STANDARD TABLE OF BAPI_EXTDOC_A, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_bapi_billdocnumber  TYPE STANDARD TABLE OF BAPI_FKKINV_BILLDOCNUMBER, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_BILLDOC_CREATEMULTIPLE'  "BAPI for Billing document Create
    EXPORTING
         TESTRUN = lv_testrun
         CFCVALIDATION = lv_cfcvalidation
    TABLES
         HEADERS = lt_headers
         ITEMS = lt_items
         TAXITEMS = lt_taxitems
         ADDITEMS = lt_additems
         EXTENSIONIN = lt_extensionin
         EXTENSIONOUT = lt_extensionout
         BAPI_BILLDOCNUMBER = lt_bapi_billdocnumber
         RETURN = lt_return
. " BAPI_BILLDOC_CREATEMULTIPLE




ABAP code using 7.40 inline data declarations to call FM BAPI_BILLDOC_CREATEMULTIPLE

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 BAPI_AUX_INV INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
 
"SELECT single CFCVALIDATION FROM BAPI_AUX_INV INTO @DATA(ld_cfcvalidation).
DATA(ld_cfcvalidation) = ' '.
 
 
 
 
 
 
 


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!