SAP EXIT_SAPLGUMD_006 Function Module for User exits for master data - add record with period-dependent add. info.
EXIT_SAPLGUMD_006 is a standard exit saplgumd 006 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User exits for master data - add record with period-dependent add. info. 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 exit saplgumd 006 FM, simply by entering the name EXIT_SAPLGUMD_006 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XGMD
Program Name: SAPLXGMD
Main Program:
Appliation area: G
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLGUMD_006 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 'EXIT_SAPLGUMD_006'"User exits for master data - add record with period-dependent add. info..
EXPORTING
I_EXIT_NBR = "Exit number
I_FIELD = "Field to be validated
I_PERIOD = "Period for which additional information is to be provided
I_PERIOD_DATE_FROM = "Start date of period
I_PERIOD_DATE_TO = "End date for period
I_RECORD = "Record in which the field to be validated lies
I_TABLE = "Table structure of record
IMPORTING
E_RECORD = "Transferred Record, Including Additional Information
EXCEPTIONS
NO_EXIT_FOUND = 1 NO_VALID_VALUE = 2
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.G_COMBINATIONS_BUILD
G_COMBINATIONS_FREE
G_COMBINATION_GET
G_COMBINATION_GET_EXIT
G_DEPENDENT_GET
G_GET_T800D_ENTRY_FROM_DDIC
G_READ_AREA
G_READ_AREA_TAB
G_READ_TEXT
G_READ_VALUE
G_RECORD_CHECK
G_RECORD_CHECK_AGAINST_COMB
IMPORTING Parameters details for EXIT_SAPLGUMD_006
I_EXIT_NBR - Exit number
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_FIELD - Field to be validated
Data type: T800D-FELDOptional: No
Call by Reference: No ( called with pass by value option)
I_PERIOD - Period for which additional information is to be provided
Data type: PERIODS-BUPEROptional: No
Call by Reference: No ( called with pass by value option)
I_PERIOD_DATE_FROM - Start date of period
Data type: PERIODS-DATABOptional: No
Call by Reference: No ( called with pass by value option)
I_PERIOD_DATE_TO - End date for period
Data type: PERIODS-DATBIOptional: No
Call by Reference: No ( called with pass by value option)
I_RECORD - Record in which the field to be validated lies
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_TABLE - Table structure of record
Data type: T800D-TABOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLGUMD_006
E_RECORD - Transferred Record, Including Additional Information
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_EXIT_FOUND - Exit was not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_VALUE - No valid value found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLGUMD_006 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_e_record | TYPE STRING, " | |||
| lv_i_exit_nbr | TYPE STRING, " | |||
| lv_no_exit_found | TYPE STRING, " | |||
| lv_i_field | TYPE T800D-FELD, " | |||
| lv_no_valid_value | TYPE T800D, " | |||
| lv_i_period | TYPE PERIODS-BUPER, " | |||
| lv_i_period_date_from | TYPE PERIODS-DATAB, " | |||
| lv_i_period_date_to | TYPE PERIODS-DATBI, " | |||
| lv_i_record | TYPE PERIODS, " | |||
| lv_i_table | TYPE T800D-TAB. " |
|   CALL FUNCTION 'EXIT_SAPLGUMD_006' "User exits for master data - add record with period-dependent add. info. |
| EXPORTING | ||
| I_EXIT_NBR | = lv_i_exit_nbr | |
| I_FIELD | = lv_i_field | |
| I_PERIOD | = lv_i_period | |
| I_PERIOD_DATE_FROM | = lv_i_period_date_from | |
| I_PERIOD_DATE_TO | = lv_i_period_date_to | |
| I_RECORD | = lv_i_record | |
| I_TABLE | = lv_i_table | |
| IMPORTING | ||
| E_RECORD | = lv_e_record | |
| EXCEPTIONS | ||
| NO_EXIT_FOUND = 1 | ||
| NO_VALID_VALUE = 2 | ||
| . " EXIT_SAPLGUMD_006 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLGUMD_006
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 FELD FROM T800D INTO @DATA(ld_i_field). | ||||
| "SELECT single BUPER FROM PERIODS INTO @DATA(ld_i_period). | ||||
| "SELECT single DATAB FROM PERIODS INTO @DATA(ld_i_period_date_from). | ||||
| "SELECT single DATBI FROM PERIODS INTO @DATA(ld_i_period_date_to). | ||||
| "SELECT single TAB FROM T800D INTO @DATA(ld_i_table). | ||||
Search for further information about these or an SAP related objects