SAP FM4D_CHECK_CARRIER_ACTIV Function Module for









FM4D_CHECK_CARRIER_ACTIV is a standard fm4d check carrier activ 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 fm4d check carrier activ FM, simply by entering the name FM4D_CHECK_CARRIER_ACTIV into the relevant SAP transaction such as SE37 or SE38.

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



Function FM4D_CHECK_CARRIER_ACTIV 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 'FM4D_CHECK_CARRIER_ACTIV'"
EXPORTING
I_FIKRS = "
* I_GEBER = ' ' "
* I_GJAHR = ' ' "

IMPORTING
E_CARRIER_ACTIVE = "
E_TOTAL = "
E_BUDGET_ACTIVE = "
E_BUDGET_PAY_ACTIVE = "
E_BUDGET_COM_ACTIVE = "
E_BAL_BUDGET_ACTIVE = "
E_POSTING_ACTIVE = "
E_CONTR_PAY_ACTIVE = "
E_CONTR_COM_ACTIVE = "
E_GJAHR = "

EXCEPTIONS
PROFILE_NOT_ASSIGNED = 1 PROFILE_NOT_FOUND = 2 FM_AREA_NOT_FOUND = 3
.



IMPORTING Parameters details for FM4D_CHECK_CARRIER_ACTIV

I_FIKRS -

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

I_GEBER -

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

I_GJAHR -

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

EXPORTING Parameters details for FM4D_CHECK_CARRIER_ACTIV

E_CARRIER_ACTIVE -

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

E_TOTAL -

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

E_BUDGET_ACTIVE -

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

E_BUDGET_PAY_ACTIVE -

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

E_BUDGET_COM_ACTIVE -

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

E_BAL_BUDGET_ACTIVE -

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

E_POSTING_ACTIVE -

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

E_CONTR_PAY_ACTIVE -

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

E_CONTR_COM_ACTIVE -

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

E_GJAHR -

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

EXCEPTIONS details

PROFILE_NOT_ASSIGNED -

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

PROFILE_NOT_FOUND -

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

FM_AREA_NOT_FOUND -

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

Copy and paste ABAP code example for FM4D_CHECK_CARRIER_ACTIV 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_fikrs  TYPE BPIN-FIKRS, "   
lv_e_carrier_active  TYPE BPIN, "   
lv_profile_not_assigned  TYPE BPIN, "   
lv_e_total  TYPE BPIN, "   
lv_i_geber  TYPE BPIN-GEBER, "   SPACE
lv_e_budget_active  TYPE BPIN, "   
lv_profile_not_found  TYPE BPIN, "   
lv_i_gjahr  TYPE BPIN-GJAHR, "   SPACE
lv_fm_area_not_found  TYPE BPIN, "   
lv_e_budget_pay_active  TYPE BPIN, "   
lv_e_budget_com_active  TYPE BPIN, "   
lv_e_bal_budget_active  TYPE BPIN, "   
lv_e_posting_active  TYPE BPIN, "   
lv_e_contr_pay_active  TYPE BPIN, "   
lv_e_contr_com_active  TYPE BPIN, "   
lv_e_gjahr  TYPE BPIN. "   

  CALL FUNCTION 'FM4D_CHECK_CARRIER_ACTIV'  "
    EXPORTING
         I_FIKRS = lv_i_fikrs
         I_GEBER = lv_i_geber
         I_GJAHR = lv_i_gjahr
    IMPORTING
         E_CARRIER_ACTIVE = lv_e_carrier_active
         E_TOTAL = lv_e_total
         E_BUDGET_ACTIVE = lv_e_budget_active
         E_BUDGET_PAY_ACTIVE = lv_e_budget_pay_active
         E_BUDGET_COM_ACTIVE = lv_e_budget_com_active
         E_BAL_BUDGET_ACTIVE = lv_e_bal_budget_active
         E_POSTING_ACTIVE = lv_e_posting_active
         E_CONTR_PAY_ACTIVE = lv_e_contr_pay_active
         E_CONTR_COM_ACTIVE = lv_e_contr_com_active
         E_GJAHR = lv_e_gjahr
    EXCEPTIONS
        PROFILE_NOT_ASSIGNED = 1
        PROFILE_NOT_FOUND = 2
        FM_AREA_NOT_FOUND = 3
. " FM4D_CHECK_CARRIER_ACTIV




ABAP code using 7.40 inline data declarations to call FM FM4D_CHECK_CARRIER_ACTIV

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 FIKRS FROM BPIN INTO @DATA(ld_i_fikrs).
 
 
 
 
"SELECT single GEBER FROM BPIN INTO @DATA(ld_i_geber).
DATA(ld_i_geber) = ' '.
 
 
 
"SELECT single GJAHR FROM BPIN INTO @DATA(ld_i_gjahr).
DATA(ld_i_gjahr) = ' '.
 
 
 
 
 
 
 
 
 


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!