SAP GET_EXCISE_DETAILS Function Module for Function module to get customer/vendor/plant excise details

Search SAP Function Modules

GET_EXCISE_DETAILS is a standard get excise details SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function module to get customer/vendor/plant excise details 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 get excise details FM, simply by entering the name GET_EXCISE_DETAILS into the relevant SAP transaction such as SE37 or SE38.

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

Function GET_EXCISE_DETAILS 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 'GET_EXCISE_DETAILS'"Function module to get customer/vendor/plant excise details
  EXPORTING
*  I_KUNNR =  "Customer number
*  I_LIFNR =  "Vendor (creditor) account number
*  I_WERKS =  "Plant

 IMPORTING
   E_MOCUST =  "Customer excise details
   E_MOVEND =  "Vendor's excise details
   E_REGSET =  "Company-Plant excise details

EXCEPTIONS
   NOT_FOUND = 1    PARAMETER_ERROR = 2 

.

IMPORTING Parameters details for GET_EXCISE_DETAILS

I_KUNNR - Customer number

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

I_LIFNR - Vendor (creditor) account number

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

I_WERKS - Plant

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

EXPORTING Parameters details for GET_EXCISE_DETAILS

E_MOCUST - Customer excise details

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

E_MOVEND - Vendor's excise details

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

E_REGSET - Company-Plant excise details

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

EXCEPTIONS details

NOT_FOUND - not found

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

PARAMETER_ERROR - parameter error

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

Copy and paste ABAP code example for GET_EXCISE_DETAILS 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.

ABAP code using 7.40 inline data declarations to call FM GET_EXCISE_DETAILS

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