SAP G_WRITE_MESSAGE_TAB_GCIN Function Module for









G_WRITE_MESSAGE_TAB_GCIN is a standard g write message tab gcin 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 g write message tab gcin FM, simply by entering the name G_WRITE_MESSAGE_TAB_GCIN into the relevant SAP transaction such as SE37 or SE38.

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



Function G_WRITE_MESSAGE_TAB_GCIN 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_WRITE_MESSAGE_TAB_GCIN'"
EXPORTING
I_TAB_GROUP = "Name of Table Group
* I_FULL_SCREEN = ' ' "
* I_ONLY_DISPLAY = 'X' "Display Only

CHANGING
I_T_MESSAGES = "Table with Messages
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLGDX3_001 Authority Check Function Group GDX3
EXIT_SAPLGDX3_002 Authority Check Function Group GDX3, Totals Record Display

IMPORTING Parameters details for G_WRITE_MESSAGE_TAB_GCIN

I_TAB_GROUP - Name of Table Group

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

I_FULL_SCREEN -

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

I_ONLY_DISPLAY - Display Only

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

CHANGING Parameters details for G_WRITE_MESSAGE_TAB_GCIN

I_T_MESSAGES - Table with Messages

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

Copy and paste ABAP code example for G_WRITE_MESSAGE_TAB_GCIN 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_tab_group  TYPE RGINST-GCLUSTER, "   
lv_i_t_messages  TYPE GDX3_T_MESSAGE_TAB, "   
lv_i_full_screen  TYPE GUSL_BOOL, "   SPACE
lv_i_only_display  TYPE GUSL_BOOL. "   'X'

  CALL FUNCTION 'G_WRITE_MESSAGE_TAB_GCIN'  "
    EXPORTING
         I_TAB_GROUP = lv_i_tab_group
         I_FULL_SCREEN = lv_i_full_screen
         I_ONLY_DISPLAY = lv_i_only_display
    CHANGING
         I_T_MESSAGES = lv_i_t_messages
. " G_WRITE_MESSAGE_TAB_GCIN




ABAP code using 7.40 inline data declarations to call FM G_WRITE_MESSAGE_TAB_GCIN

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 GCLUSTER FROM RGINST INTO @DATA(ld_i_tab_group).
 
 
DATA(ld_i_full_screen) = ' '.
 
DATA(ld_i_only_display) = 'X'.
 


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!