SAP GHO_DM_VALIDATE Function Module for Validate Hierarchy Structure After Update
GHO_DM_VALIDATE is a standard gho dm validate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Validate Hierarchy Structure After Update 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 gho dm validate FM, simply by entering the name GHO_DM_VALIDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GHO_DM_EVENT_TMG
Program Name: SAPLGHO_DM_EVENT_TMG
Main Program: SAPLGHO_DM_EVENT_TMG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GHO_DM_VALIDATE 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 'GHO_DM_VALIDATE'"Validate Hierarchy Structure After Update.
EXPORTING
IS_DEF_CODE_U = "Deferment Code
* IT_CHILD = "Deferment Code
IMPORTING
EV_ERROR = "Boolean Variable (X=Validated, Space=Failed)
IMPORTING Parameters details for GHO_DM_VALIDATE
IS_DEF_CODE_U - Deferment Code
Data type: GHO_DM_CODEOptional: No
Call by Reference: Yes
IT_CHILD - Deferment Code
Data type: GHO_TT_DM_CODEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for GHO_DM_VALIDATE
EV_ERROR - Boolean Variable (X=Validated, Space=Failed)
Data type: BOOLEANOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GHO_DM_VALIDATE 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_ev_error | TYPE BOOLEAN, " | |||
| lv_is_def_code_u | TYPE GHO_DM_CODE, " | |||
| lv_it_child | TYPE GHO_TT_DM_CODE. " |
|   CALL FUNCTION 'GHO_DM_VALIDATE' "Validate Hierarchy Structure After Update |
| EXPORTING | ||
| IS_DEF_CODE_U | = lv_is_def_code_u | |
| IT_CHILD | = lv_it_child | |
| IMPORTING | ||
| EV_ERROR | = lv_ev_error | |
| . " GHO_DM_VALIDATE | ||
ABAP code using 7.40 inline data declarations to call FM GHO_DM_VALIDATE
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