SAP BAPI_EXCISEINVOICE_GETLIST Function Module for Excise invoice - List of all excise invoices
BAPI_EXCISEINVOICE_GETLIST is a standard bapi exciseinvoice getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Excise invoice - List of all excise invoices 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 exciseinvoice getlist FM, simply by entering the name BAPI_EXCISEINVOICE_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1IBAPI
Program Name: SAPLJ1IBAPI
Main Program: SAPLJ1IBAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_EXCISEINVOICE_GETLIST 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_EXCISEINVOICE_GETLIST'"Excise invoice - List of all excise invoices.
EXPORTING
CUSTOMER = "Customer number
* SUPPLIER = "Account number of vendor or creditor
* TRANSACTIONTYPE = "Transaction type
* EXCISE_GROUP = "Excise Group
* INVOICE_FROM_DATE = "Excise Document Date
* INVOICE_TO_DATE = "Excise Document Date
* INVOICE_STATUS = "Challan Status
IMPORTING
RETURN = "Return parameter
TABLES
EXCISE_INVOICES = "Table for ExciseInvoice GetList Bapi
IMPORTING Parameters details for BAPI_EXCISEINVOICE_GETLIST
CUSTOMER - Customer number
Data type: BAPI1007-CUSTOMEROptional: No
Call by Reference: No ( called with pass by value option)
SUPPLIER - Account number of vendor or creditor
Data type: BAPI1008-VENDOROptional: Yes
Call by Reference: No ( called with pass by value option)
TRANSACTIONTYPE - Transaction type
Data type: BAPIEXCINV-TRANSACTION_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCISE_GROUP - Excise Group
Data type: BAPIEXCINV-EXCISE_GROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
INVOICE_FROM_DATE - Excise Document Date
Data type: BAPIEXCINV-EXCISE_INVOICE_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
INVOICE_TO_DATE - Excise Document Date
Data type: BAPIEXCINV-EXCISE_INVOICE_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
INVOICE_STATUS - Challan Status
Data type: BAPIEXCINV-STATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_EXCISEINVOICE_GETLIST
RETURN - Return parameter
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_EXCISEINVOICE_GETLIST
EXCISE_INVOICES - Table for ExciseInvoice GetList Bapi
Data type: BAPIEXCINVOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_EXCISEINVOICE_GETLIST 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_return | TYPE BAPIRETURN, " | |||
lv_customer | TYPE BAPI1007-CUSTOMER, " | |||
lt_excise_invoices | TYPE STANDARD TABLE OF BAPIEXCINV, " | |||
lv_supplier | TYPE BAPI1008-VENDOR, " | |||
lv_transactiontype | TYPE BAPIEXCINV-TRANSACTION_TYPE, " | |||
lv_excise_group | TYPE BAPIEXCINV-EXCISE_GROUP, " | |||
lv_invoice_from_date | TYPE BAPIEXCINV-EXCISE_INVOICE_DATE, " | |||
lv_invoice_to_date | TYPE BAPIEXCINV-EXCISE_INVOICE_DATE, " | |||
lv_invoice_status | TYPE BAPIEXCINV-STATUS. " |
  CALL FUNCTION 'BAPI_EXCISEINVOICE_GETLIST' "Excise invoice - List of all excise invoices |
EXPORTING | ||
CUSTOMER | = lv_customer | |
SUPPLIER | = lv_supplier | |
TRANSACTIONTYPE | = lv_transactiontype | |
EXCISE_GROUP | = lv_excise_group | |
INVOICE_FROM_DATE | = lv_invoice_from_date | |
INVOICE_TO_DATE | = lv_invoice_to_date | |
INVOICE_STATUS | = lv_invoice_status | |
IMPORTING | ||
RETURN | = lv_return | |
TABLES | ||
EXCISE_INVOICES | = lt_excise_invoices | |
. " BAPI_EXCISEINVOICE_GETLIST |
ABAP code using 7.40 inline data declarations to call FM BAPI_EXCISEINVOICE_GETLIST
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 CUSTOMER FROM BAPI1007 INTO @DATA(ld_customer). | ||||
"SELECT single VENDOR FROM BAPI1008 INTO @DATA(ld_supplier). | ||||
"SELECT single TRANSACTION_TYPE FROM BAPIEXCINV INTO @DATA(ld_transactiontype). | ||||
"SELECT single EXCISE_GROUP FROM BAPIEXCINV INTO @DATA(ld_excise_group). | ||||
"SELECT single EXCISE_INVOICE_DATE FROM BAPIEXCINV INTO @DATA(ld_invoice_from_date). | ||||
"SELECT single EXCISE_INVOICE_DATE FROM BAPIEXCINV INTO @DATA(ld_invoice_to_date). | ||||
"SELECT single STATUS FROM BAPIEXCINV INTO @DATA(ld_invoice_status). | ||||
Search for further information about these or an SAP related objects