SAP FI_BLART_AUTH_CHECK Function Module for









FI_BLART_AUTH_CHECK is a standard fi blart auth check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fi blart auth check FM, simply by entering the name FI_BLART_AUTH_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_BLART_AUTH_CHECK 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 'FI_BLART_AUTH_CHECK'"
EXPORTING
* I_BUKRS = "
I_BLART = "
I_AKTVT = "

IMPORTING
E_RTCODE = "
.



IMPORTING Parameters details for FI_BLART_AUTH_CHECK

I_BUKRS -

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

I_BLART -

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

I_AKTVT -

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

EXPORTING Parameters details for FI_BLART_AUTH_CHECK

E_RTCODE -

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

Copy and paste ABAP code example for FI_BLART_AUTH_CHECK 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_i_bukrs  TYPE T001-BUKRS, "   
lv_e_rtcode  TYPE N, "   
lv_i_blart  TYPE BKPF-BLART, "   
lv_i_aktvt  TYPE TACT-ACTVT. "   

  CALL FUNCTION 'FI_BLART_AUTH_CHECK'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_BLART = lv_i_blart
         I_AKTVT = lv_i_aktvt
    IMPORTING
         E_RTCODE = lv_e_rtcode
. " FI_BLART_AUTH_CHECK




ABAP code using 7.40 inline data declarations to call FM FI_BLART_AUTH_CHECK

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 BUKRS FROM T001 INTO @DATA(ld_i_bukrs).
 
 
"SELECT single BLART FROM BKPF INTO @DATA(ld_i_blart).
 
"SELECT single ACTVT FROM TACT INTO @DATA(ld_i_aktvt).
 


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!