SAP FI_WT_CHECK_ITEM_ACTIVATION Function Module for









FI_WT_CHECK_ITEM_ACTIVATION is a standard fi wt check item activation 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 wt check item activation FM, simply by entering the name FI_WT_CHECK_ITEM_ACTIVATION into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_WT_CHECK_ITEM_ACTIVATION 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_WT_CHECK_ITEM_ACTIVATION'"
  EXPORTING
   I_BUKRS =  "
   I_ZUMSK =  "Target special G/L indicator
   I_UMSKS =  "Special G/L Transaction Type
   I_GJAHR =  "
   I_BELNR =  "
   I_BUZEI =  "
   I_DATE =  "
   I_KOART =  "
   I_LIFNR =  "
   I_KUNNR =  "
*  I_REBZT = ' ' "

EXCEPTIONS
   ACTIVATION_IMPOSSIBLE = 1
.



IMPORTING Parameters details for FI_WT_CHECK_ITEM_ACTIVATION

I_BUKRS -

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

I_ZUMSK - Target special G/L indicator

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

I_UMSKS - Special G/L Transaction Type

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

I_GJAHR -

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

I_BELNR -

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

I_BUZEI -

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

I_DATE -

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

I_KOART -

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

I_LIFNR -

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

I_KUNNR -

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

I_REBZT -

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

EXCEPTIONS details

ACTIVATION_IMPOSSIBLE -

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

Copy and paste ABAP code example for FI_WT_CHECK_ITEM_ACTIVATION 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 BSEG-BUKRS, "   
lv_activation_impossible  TYPE BSEG, "   
lv_i_zumsk  TYPE BSEG-ZUMSK, "   
lv_i_umsks  TYPE BSEG-UMSKS, "   
lv_i_gjahr  TYPE BSEG-GJAHR, "   
lv_i_belnr  TYPE BSEG-BELNR, "   
lv_i_buzei  TYPE BSEG-BUZEI, "   
lv_i_date  TYPE BKPF-BUDAT, "   
lv_i_koart  TYPE BSEG-KOART, "   
lv_i_lifnr  TYPE BSEG-LIFNR, "   
lv_i_kunnr  TYPE BSEG-KUNNR, "   
lv_i_rebzt  TYPE BSEG-REBZT. "   SPACE

  CALL FUNCTION 'FI_WT_CHECK_ITEM_ACTIVATION'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_ZUMSK = lv_i_zumsk
         I_UMSKS = lv_i_umsks
         I_GJAHR = lv_i_gjahr
         I_BELNR = lv_i_belnr
         I_BUZEI = lv_i_buzei
         I_DATE = lv_i_date
         I_KOART = lv_i_koart
         I_LIFNR = lv_i_lifnr
         I_KUNNR = lv_i_kunnr
         I_REBZT = lv_i_rebzt
    EXCEPTIONS
        ACTIVATION_IMPOSSIBLE = 1
. " FI_WT_CHECK_ITEM_ACTIVATION




ABAP code using 7.40 inline data declarations to call FM FI_WT_CHECK_ITEM_ACTIVATION

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 BSEG INTO @DATA(ld_i_bukrs).
 
 
"SELECT single ZUMSK FROM BSEG INTO @DATA(ld_i_zumsk).
 
"SELECT single UMSKS FROM BSEG INTO @DATA(ld_i_umsks).
 
"SELECT single GJAHR FROM BSEG INTO @DATA(ld_i_gjahr).
 
"SELECT single BELNR FROM BSEG INTO @DATA(ld_i_belnr).
 
"SELECT single BUZEI FROM BSEG INTO @DATA(ld_i_buzei).
 
"SELECT single BUDAT FROM BKPF INTO @DATA(ld_i_date).
 
"SELECT single KOART FROM BSEG INTO @DATA(ld_i_koart).
 
"SELECT single LIFNR FROM BSEG INTO @DATA(ld_i_lifnr).
 
"SELECT single KUNNR FROM BSEG INTO @DATA(ld_i_kunnr).
 
"SELECT single REBZT FROM BSEG INTO @DATA(ld_i_rebzt).
DATA(ld_i_rebzt) = ' '.
 


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!