SAP G_LAYOUT_MAINTENANCE_FLAG Function Module for Set 'Changes allowed during execution' indicator
G_LAYOUT_MAINTENANCE_FLAG is a standard g layout maintenance flag SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set 'Changes allowed during execution' indicator 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 layout maintenance flag FM, simply by entering the name G_LAYOUT_MAINTENANCE_FLAG into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRWF
Program Name: SAPLGRWF
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_LAYOUT_MAINTENANCE_FLAG 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_LAYOUT_MAINTENANCE_FLAG'"Set 'Changes allowed during execution' indicator.
CHANGING
MAINTAIN_ALLOWED = "Indicator: Layout changes in report output allowed
EXCEPTIONS
CANCELED = 1
CHANGING Parameters details for G_LAYOUT_MAINTENANCE_FLAG
MAINTAIN_ALLOWED - Indicator: Layout changes in report output allowed
Data type: RGRWF-PARMSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELED - Entry terminated by user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_LAYOUT_MAINTENANCE_FLAG 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_canceled | TYPE STRING, " | |||
| lv_maintain_allowed | TYPE RGRWF-PARMS. " |
|   CALL FUNCTION 'G_LAYOUT_MAINTENANCE_FLAG' "Set 'Changes allowed during execution' indicator |
| CHANGING | ||
| MAINTAIN_ALLOWED | = lv_maintain_allowed | |
| EXCEPTIONS | ||
| CANCELED = 1 | ||
| . " G_LAYOUT_MAINTENANCE_FLAG | ||
ABAP code using 7.40 inline data declarations to call FM G_LAYOUT_MAINTENANCE_FLAG
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 PARMS FROM RGRWF INTO @DATA(ld_maintain_allowed). | ||||
Search for further information about these or an SAP related objects