SAP GLE_MCA_FDOCREF_READ Function Module for Reads FI document reference from database









GLE_MCA_FDOCREF_READ is a standard gle mca fdocref read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads FI document reference from database processing and below is the pattern details for this FM, 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 gle mca fdocref read FM, simply by entering the name GLE_MCA_FDOCREF_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function GLE_MCA_FDOCREF_READ 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 'GLE_MCA_FDOCREF_READ'"Reads FI document reference from database
  EXPORTING
*  I_LOGHANDLE =  "Application Log: Log Handle
*  I_TAB_RANGE_RUNID =  "Ranges table MCA Run ID
*  I_TAB_RANGE_BUKRS =  "Ranges table Company Code
*  I_TAB_RANGE_GJAHR =  "Ranges table Fiscal Year
*  I_TAB_RANGE_BELNR =  "Ranges table Document Number
*  I_RUNID =  "MCA Run ID
*  I_BUKRS =  "Company Code
*  I_GJAHR =  "Fiscal Year
*  I_BELNR =  "Accounting Document Number
*  I_MCA_BUKRS =  "Company Code
*  I_MCA_GJAHR =  "MCA Fiscal Year
*  I_MCA_DOCNO =  "MCA Document Number
*  I_TAB_RANGE_PRCCAT =  "Ranges table Process Category

 IMPORTING
   E_TAB_FDOCREF =  "Table of FI document references
   E_TAB_RETURN =  "Return Messages
   E_ERROR =  "Error indicator
.



IMPORTING Parameters details for GLE_MCA_FDOCREF_READ

I_LOGHANDLE - Application Log: Log Handle

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

I_TAB_RANGE_RUNID - Ranges table MCA Run ID

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

I_TAB_RANGE_BUKRS - Ranges table Company Code

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

I_TAB_RANGE_GJAHR - Ranges table Fiscal Year

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

I_TAB_RANGE_BELNR - Ranges table Document Number

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

I_RUNID - MCA Run ID

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

I_BUKRS - Company Code

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

I_GJAHR - Fiscal Year

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

I_BELNR - Accounting Document Number

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

I_MCA_BUKRS - Company Code

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

I_MCA_GJAHR - MCA Fiscal Year

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

I_MCA_DOCNO - MCA Document Number

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

I_TAB_RANGE_PRCCAT - Ranges table Process Category

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

EXPORTING Parameters details for GLE_MCA_FDOCREF_READ

E_TAB_FDOCREF - Table of FI document references

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

E_TAB_RETURN - Return Messages

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

E_ERROR - Error indicator

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

Copy and paste ABAP code example for GLE_MCA_FDOCREF_READ 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_loghandle  TYPE BALLOGHNDL, "   
lv_e_tab_fdocref  TYPE GLE_MCA_TAB_FDOCREF, "   
lv_i_tab_range_runid  TYPE GLE_MCA_TAB_RANGE_RUNID, "   
lv_i_tab_range_bukrs  TYPE GLE_MCA_TAB_RANGE_BUKRS, "   
lv_i_tab_range_gjahr  TYPE GLE_MCA_TAB_RANGE_GJAHR, "   
lv_i_tab_range_belnr  TYPE GLE_MCA_TAB_RANGE_BELNR, "   
lv_i_runid  TYPE GLE_MCA_DTE_RUNID, "   
lv_e_tab_return  TYPE BAPIRET2_T, "   
lv_e_error  TYPE ABAP_BOOL, "   
lv_i_bukrs  TYPE BUKRS, "   
lv_i_gjahr  TYPE GJAHR, "   
lv_i_belnr  TYPE BELNR_D, "   
lv_i_mca_bukrs  TYPE BUKRS, "   
lv_i_mca_gjahr  TYPE GJAHR, "   
lv_i_mca_docno  TYPE BELNR_D, "   
lv_i_tab_range_prccat  TYPE GLE_MCA_TAB_RANGE_PRCCAT. "   

  CALL FUNCTION 'GLE_MCA_FDOCREF_READ'  "Reads FI document reference from database
    EXPORTING
         I_LOGHANDLE = lv_i_loghandle
         I_TAB_RANGE_RUNID = lv_i_tab_range_runid
         I_TAB_RANGE_BUKRS = lv_i_tab_range_bukrs
         I_TAB_RANGE_GJAHR = lv_i_tab_range_gjahr
         I_TAB_RANGE_BELNR = lv_i_tab_range_belnr
         I_RUNID = lv_i_runid
         I_BUKRS = lv_i_bukrs
         I_GJAHR = lv_i_gjahr
         I_BELNR = lv_i_belnr
         I_MCA_BUKRS = lv_i_mca_bukrs
         I_MCA_GJAHR = lv_i_mca_gjahr
         I_MCA_DOCNO = lv_i_mca_docno
         I_TAB_RANGE_PRCCAT = lv_i_tab_range_prccat
    IMPORTING
         E_TAB_FDOCREF = lv_e_tab_fdocref
         E_TAB_RETURN = lv_e_tab_return
         E_ERROR = lv_e_error
. " GLE_MCA_FDOCREF_READ




ABAP code using 7.40 inline data declarations to call FM GLE_MCA_FDOCREF_READ

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!