SAP FM_HH_FICTR_DETERMINE Function Module for









FM_HH_FICTR_DETERMINE is a standard fm hh fictr determine 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 fm hh fictr determine FM, simply by entering the name FM_HH_FICTR_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_HH_FICTR_DETERMINE 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 'FM_HH_FICTR_DETERMINE'"
EXPORTING
IP_FIKRS = "
IP_GJAHR = "

IMPORTING
OP_HH_FICTR = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for FM_HH_FICTR_DETERMINE

IP_FIKRS -

Data type: FM01BSP-FIKRS
Optional: No
Call by Reference: Yes

IP_GJAHR -

Data type: FM01BSP-GJAHR
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FM_HH_FICTR_DETERMINE

OP_HH_FICTR -

Data type: FM01BSP-HH_FICTR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for FM_HH_FICTR_DETERMINE 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_ip_fikrs  TYPE FM01BSP-FIKRS, "   
lv_not_found  TYPE FM01BSP, "   
lv_op_hh_fictr  TYPE FM01BSP-HH_FICTR, "   
lv_ip_gjahr  TYPE FM01BSP-GJAHR. "   

  CALL FUNCTION 'FM_HH_FICTR_DETERMINE'  "
    EXPORTING
         IP_FIKRS = lv_ip_fikrs
         IP_GJAHR = lv_ip_gjahr
    IMPORTING
         OP_HH_FICTR = lv_op_hh_fictr
    EXCEPTIONS
        NOT_FOUND = 1
. " FM_HH_FICTR_DETERMINE




ABAP code using 7.40 inline data declarations to call FM FM_HH_FICTR_DETERMINE

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 FM01BSP INTO @DATA(ld_ip_fikrs).
 
 
"SELECT single HH_FICTR FROM FM01BSP INTO @DATA(ld_op_hh_fictr).
 
"SELECT single GJAHR FROM FM01BSP INTO @DATA(ld_ip_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!