SAP FICTR_READ_WITH_OBJNR Function Module for









FICTR_READ_WITH_OBJNR is a standard fictr read with objnr 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 fictr read with objnr FM, simply by entering the name FICTR_READ_WITH_OBJNR into the relevant SAP transaction such as SE37 or SE38.

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



Function FICTR_READ_WITH_OBJNR 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 'FICTR_READ_WITH_OBJNR'"
EXPORTING
* IP_CTRHIVERS = 'SAP' "
IP_CTR_OBJNR = "
* IP_HIVARNT = ' ' "
* IP_HIERARCHY = ' ' "
* IP_LANGUAGE = ' ' "
* IP_TEXT = ' ' "
* IP_DATE = '00000000' "
* IP_GJAHR = '0000' "

IMPORTING
F_FMFCTR = "
F_FMFCTRT = "
F_FMHICTR = "

EXCEPTIONS
HIERARCHY_NOT_FOUND = 1 INPUT_ERROR = 2 MASTER_DATA_NOT_FOUND = 3
.



IMPORTING Parameters details for FICTR_READ_WITH_OBJNR

IP_CTRHIVERS -

Data type: FMHIPOS-POSHIVERS
Default: 'SAP'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IP_CTR_OBJNR -

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

IP_HIVARNT -

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

IP_HIERARCHY -

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

IP_LANGUAGE -

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

IP_TEXT -

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

IP_DATE -

Data type: FMFCTR-DATBIS
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IP_GJAHR -

Data type: FM01P-GJAHR
Default: '0000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FICTR_READ_WITH_OBJNR

F_FMFCTR -

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

F_FMFCTRT -

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

F_FMHICTR -

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

EXCEPTIONS details

HIERARCHY_NOT_FOUND -

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

INPUT_ERROR -

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

MASTER_DATA_NOT_FOUND -

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

Copy and paste ABAP code example for FICTR_READ_WITH_OBJNR 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_f_fmfctr  TYPE FMFCTR, "   
lv_ip_ctrhivers  TYPE FMHIPOS-POSHIVERS, "   'SAP'
lv_hierarchy_not_found  TYPE FMHIPOS, "   
lv_f_fmfctrt  TYPE FMFCTRT, "   
lv_input_error  TYPE FMFCTRT, "   
lv_ip_ctr_objnr  TYPE FMFCTR-CTR_OBJNR, "   
lv_f_fmhictr  TYPE FMHICTR, "   
lv_ip_hivarnt  TYPE FMHISV-HIVARNT, "   SPACE
lv_master_data_not_found  TYPE FMHISV, "   
lv_ip_hierarchy  TYPE FMHISV, "   SPACE
lv_ip_language  TYPE FMHISV, "   SPACE
lv_ip_text  TYPE FMHISV, "   SPACE
lv_ip_date  TYPE FMFCTR-DATBIS, "   '00000000'
lv_ip_gjahr  TYPE FM01P-GJAHR. "   '0000'

  CALL FUNCTION 'FICTR_READ_WITH_OBJNR'  "
    EXPORTING
         IP_CTRHIVERS = lv_ip_ctrhivers
         IP_CTR_OBJNR = lv_ip_ctr_objnr
         IP_HIVARNT = lv_ip_hivarnt
         IP_HIERARCHY = lv_ip_hierarchy
         IP_LANGUAGE = lv_ip_language
         IP_TEXT = lv_ip_text
         IP_DATE = lv_ip_date
         IP_GJAHR = lv_ip_gjahr
    IMPORTING
         F_FMFCTR = lv_f_fmfctr
         F_FMFCTRT = lv_f_fmfctrt
         F_FMHICTR = lv_f_fmhictr
    EXCEPTIONS
        HIERARCHY_NOT_FOUND = 1
        INPUT_ERROR = 2
        MASTER_DATA_NOT_FOUND = 3
. " FICTR_READ_WITH_OBJNR




ABAP code using 7.40 inline data declarations to call FM FICTR_READ_WITH_OBJNR

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 POSHIVERS FROM FMHIPOS INTO @DATA(ld_ip_ctrhivers).
DATA(ld_ip_ctrhivers) = 'SAP'.
 
 
 
 
"SELECT single CTR_OBJNR FROM FMFCTR INTO @DATA(ld_ip_ctr_objnr).
 
 
"SELECT single HIVARNT FROM FMHISV INTO @DATA(ld_ip_hivarnt).
DATA(ld_ip_hivarnt) = ' '.
 
 
DATA(ld_ip_hierarchy) = ' '.
 
DATA(ld_ip_language) = ' '.
 
DATA(ld_ip_text) = ' '.
 
"SELECT single DATBIS FROM FMFCTR INTO @DATA(ld_ip_date).
DATA(ld_ip_date) = '00000000'.
 
"SELECT single GJAHR FROM FM01P INTO @DATA(ld_ip_gjahr).
DATA(ld_ip_gjahr) = '0000'.
 


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!