SAP G_G_IDOC_REC_ECMCT Function Module for Receive IDOC for table group ECMCT









G_G_IDOC_REC_ECMCT is a standard g g idoc rec ecmct SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Receive IDOC for table group ECMCT 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 g g idoc rec ecmct FM, simply by entering the name G_G_IDOC_REC_ECMCT into the relevant SAP transaction such as SE37 or SE38.

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



Function G_G_IDOC_REC_ECMCT 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 'G_G_IDOC_REC_ECMCT'"Receive IDOC for table group ECMCT
EXPORTING
MESTYP = "
DOCNUM = "
TAB = "

TABLES
IDOC_SEGMENT = "
* IDOC_STATUS = "
* RETURN_VARIABLES = "
.



IMPORTING Parameters details for G_G_IDOC_REC_ECMCT

MESTYP -

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

DOCNUM -

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

TAB -

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

TABLES Parameters details for G_G_IDOC_REC_ECMCT

IDOC_SEGMENT -

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

IDOC_STATUS -

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

RETURN_VARIABLES -

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

Copy and paste ABAP code example for G_G_IDOC_REC_ECMCT 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_mestyp  TYPE EDIDC-MESTYP, "   
lt_idoc_segment  TYPE STANDARD TABLE OF EDIDD, "   
lv_docnum  TYPE EDIDC-DOCNUM, "   
lt_idoc_status  TYPE STANDARD TABLE OF BDIDOCSTAT, "   
lv_tab  TYPE T800A-TAB, "   
lt_return_variables  TYPE STANDARD TABLE OF BDWFRETVAR. "   

  CALL FUNCTION 'G_G_IDOC_REC_ECMCT'  "Receive IDOC for table group ECMCT
    EXPORTING
         MESTYP = lv_mestyp
         DOCNUM = lv_docnum
         TAB = lv_tab
    TABLES
         IDOC_SEGMENT = lt_idoc_segment
         IDOC_STATUS = lt_idoc_status
         RETURN_VARIABLES = lt_return_variables
. " G_G_IDOC_REC_ECMCT




ABAP code using 7.40 inline data declarations to call FM G_G_IDOC_REC_ECMCT

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 MESTYP FROM EDIDC INTO @DATA(ld_mestyp).
 
 
"SELECT single DOCNUM FROM EDIDC INTO @DATA(ld_docnum).
 
 
"SELECT single TAB FROM T800A INTO @DATA(ld_tab).
 
 


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!