SAP GRPG_CHECK_DISGR_SETTING Function Module for NOTRANSL: Check whether requirem. grouping is activated for MRP group or n
GRPG_CHECK_DISGR_SETTING is a standard grpg check disgr setting SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check whether requirem. grouping is activated for MRP group or n 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 grpg check disgr setting FM, simply by entering the name GRPG_CHECK_DISGR_SETTING into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPG
Program Name: SAPLGRPG
Main Program: SAPLGRPG
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPG_CHECK_DISGR_SETTING 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 'GRPG_CHECK_DISGR_SETTING'"NOTRANSL: Check whether requirem. grouping is activated for MRP group or n.
EXPORTING
I_WERKS = "Plant
I_DISGR = "
EXCEPTIONS
GROUPING_NOT_ACTIVATED = 1 DISGR_NOT_FOUND = 2
IMPORTING Parameters details for GRPG_CHECK_DISGR_SETTING
I_WERKS - Plant
Data type: T438M-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
I_DISGR -
Data type: T438M-MTARTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
GROUPING_NOT_ACTIVATED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DISGR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPG_CHECK_DISGR_SETTING 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_werks | TYPE T438M-WERKS, " | |||
| lv_grouping_not_activated | TYPE T438M, " | |||
| lv_i_disgr | TYPE T438M-MTART, " | |||
| lv_disgr_not_found | TYPE T438M. " |
|   CALL FUNCTION 'GRPG_CHECK_DISGR_SETTING' "NOTRANSL: Check whether requirem. grouping is activated for MRP group or n |
| EXPORTING | ||
| I_WERKS | = lv_i_werks | |
| I_DISGR | = lv_i_disgr | |
| EXCEPTIONS | ||
| GROUPING_NOT_ACTIVATED = 1 | ||
| DISGR_NOT_FOUND = 2 | ||
| . " GRPG_CHECK_DISGR_SETTING | ||
ABAP code using 7.40 inline data declarations to call FM GRPG_CHECK_DISGR_SETTING
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 WERKS FROM T438M INTO @DATA(ld_i_werks). | ||||
| "SELECT single MTART FROM T438M INTO @DATA(ld_i_disgr). | ||||
Search for further information about these or an SAP related objects