SAP ISSR_IF_MIG_READ_FI_DATA Function Module for









ISSR_IF_MIG_READ_FI_DATA is a standard issr if mig read fi data 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 issr if mig read fi data FM, simply by entering the name ISSR_IF_MIG_READ_FI_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function ISSR_IF_MIG_READ_FI_DATA 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 'ISSR_IF_MIG_READ_FI_DATA'"
  EXPORTING
   I_BUKRS =  "
   I_BELNR =  "
   I_GJAHR =  "
   I_SHKZG =  "
*  I_HKONT =  "
*  I_STORNO =  "

 IMPORTING
   E_FI_BELNR =  "
   E_HKONT =  "
   E_MONAT =  "
   E_FI_STBLG =  "
   E_FI_BUZEI =  "
   E_FI_BUTIME =  "
   E_AWSYS =  "
   E_GLVOR =  "
   E_AWTYP =  "
   E_AWORG =  "
   E_AWREF =  "
   E_AWPOSNR =  "

EXCEPTIONS
   NO_ENTRY_FOUND = 1
.



IMPORTING Parameters details for ISSR_IF_MIG_READ_FI_DATA

I_BUKRS -

Data type: BUKRS
Optional: No
Call by Reference: Yes

I_BELNR -

Data type: BELNR_D
Optional: No
Call by Reference: Yes

I_GJAHR -

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

I_SHKZG -

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

I_HKONT -

Data type: HKONT
Optional: Yes
Call by Reference: Yes

I_STORNO -

Data type: ISSRACTIV
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISSR_IF_MIG_READ_FI_DATA

E_FI_BELNR -

Data type: BELNR_D
Optional: No
Call by Reference: Yes

E_HKONT -

Data type: HKONT
Optional: No
Call by Reference: Yes

E_MONAT -

Data type: MONAT
Optional: No
Call by Reference: Yes

E_FI_STBLG -

Data type: STBLG
Optional: No
Call by Reference: Yes

E_FI_BUZEI -

Data type: BUZEI
Optional: No
Call by Reference: Yes

E_FI_BUTIME -

Data type: CPUTM
Optional: No
Call by Reference: Yes

E_AWSYS -

Data type: AWSYS
Optional: No
Call by Reference: Yes

E_GLVOR -

Data type: GLVOR
Optional: No
Call by Reference: Yes

E_AWTYP -

Data type: AWTYP
Optional: No
Call by Reference: Yes

E_AWORG -

Data type: AWORG
Optional: No
Call by Reference: Yes

E_AWREF -

Data type: AWREF
Optional: No
Call by Reference: Yes

E_AWPOSNR -

Data type: POSNR_ACC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_ENTRY_FOUND -

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

Copy and paste ABAP code example for ISSR_IF_MIG_READ_FI_DATA 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 BUKRS, "   
lv_e_fi_belnr  TYPE BELNR_D, "   
lv_no_entry_found  TYPE BELNR_D, "   
lv_e_hkont  TYPE HKONT, "   
lv_e_monat  TYPE MONAT, "   
lv_e_fi_stblg  TYPE STBLG, "   
lv_i_belnr  TYPE BELNR_D, "   
lv_e_fi_buzei  TYPE BUZEI, "   
lv_i_gjahr  TYPE GJAHR, "   
lv_e_fi_butime  TYPE CPUTM, "   
lv_e_awsys  TYPE AWSYS, "   
lv_i_shkzg  TYPE SHKZG, "   
lv_e_glvor  TYPE GLVOR, "   
lv_i_hkont  TYPE HKONT, "   
lv_e_awtyp  TYPE AWTYP, "   
lv_i_storno  TYPE ISSRACTIV, "   
lv_e_aworg  TYPE AWORG, "   
lv_e_awref  TYPE AWREF, "   
lv_e_awposnr  TYPE POSNR_ACC. "   

  CALL FUNCTION 'ISSR_IF_MIG_READ_FI_DATA'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_BELNR = lv_i_belnr
         I_GJAHR = lv_i_gjahr
         I_SHKZG = lv_i_shkzg
         I_HKONT = lv_i_hkont
         I_STORNO = lv_i_storno
    IMPORTING
         E_FI_BELNR = lv_e_fi_belnr
         E_HKONT = lv_e_hkont
         E_MONAT = lv_e_monat
         E_FI_STBLG = lv_e_fi_stblg
         E_FI_BUZEI = lv_e_fi_buzei
         E_FI_BUTIME = lv_e_fi_butime
         E_AWSYS = lv_e_awsys
         E_GLVOR = lv_e_glvor
         E_AWTYP = lv_e_awtyp
         E_AWORG = lv_e_aworg
         E_AWREF = lv_e_awref
         E_AWPOSNR = lv_e_awposnr
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " ISSR_IF_MIG_READ_FI_DATA




ABAP code using 7.40 inline data declarations to call FM ISSR_IF_MIG_READ_FI_DATA

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!