SAP GRMG_ASSIGN_DEF_LONGSIDS_MECH Function Module for Aufgerufen von GRMG_ASSIGN_DEFAULT_LONG_SIDS
GRMG_ASSIGN_DEF_LONGSIDS_MECH is a standard grmg assign def longsids mech SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Aufgerufen von GRMG_ASSIGN_DEFAULT_LONG_SIDS 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 grmg assign def longsids mech FM, simply by entering the name GRMG_ASSIGN_DEF_LONGSIDS_MECH into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRMG
Program Name: SAPLGRMG
Main Program: SAPLGRMG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRMG_ASSIGN_DEF_LONGSIDS_MECH 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 'GRMG_ASSIGN_DEF_LONGSIDS_MECH'"Aufgerufen von GRMG_ASSIGN_DEFAULT_LONG_SIDS.
CHANGING
GRMG_SCENARIOS = "CCMS: Administration Table for TX GRMG
EXCEPTIONS
NO_LONGSIDS_INSERTED = 1
CHANGING Parameters details for GRMG_ASSIGN_DEF_LONGSIDS_MECH
GRMG_SCENARIOS - CCMS: Administration Table for TX GRMG
Data type: GRMG_SCENMANAGE_WA_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_LONGSIDS_INSERTED - Keine GRMG-Szenarien wurden modifiziert
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRMG_ASSIGN_DEF_LONGSIDS_MECH 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_grmg_scenarios | TYPE GRMG_SCENMANAGE_WA_T, " | |||
| lv_no_longsids_inserted | TYPE GRMG_SCENMANAGE_WA_T. " |
|   CALL FUNCTION 'GRMG_ASSIGN_DEF_LONGSIDS_MECH' "Aufgerufen von GRMG_ASSIGN_DEFAULT_LONG_SIDS |
| CHANGING | ||
| GRMG_SCENARIOS | = lv_grmg_scenarios | |
| EXCEPTIONS | ||
| NO_LONGSIDS_INSERTED = 1 | ||
| . " GRMG_ASSIGN_DEF_LONGSIDS_MECH | ||
ABAP code using 7.40 inline data declarations to call FM GRMG_ASSIGN_DEF_LONGSIDS_MECH
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