SAP DGHU_DL02_DETAIL_SCREEN_OPEN Function Module for NOTRANSL: GG: Aufruf GG-Prüfung und Dialog Vorschlag Verpackungsmaterial z









DGHU_DL02_DETAIL_SCREEN_OPEN is a standard dghu dl02 detail screen open 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: GG: Aufruf GG-Prüfung und Dialog Vorschlag Verpackungsmaterial z 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 dghu dl02 detail screen open FM, simply by entering the name DGHU_DL02_DETAIL_SCREEN_OPEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: DGHU_DL02
Program Name: SAPLDGHU_DL02
Main Program: SAPLDGHU_DL02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DGHU_DL02_DETAIL_SCREEN_OPEN 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 'DGHU_DL02_DETAIL_SCREEN_OPEN'"NOTRANSL: GG: Aufruf GG-Prüfung und Dialog Vorschlag Verpackungsmaterial z
  EXPORTING
   I_ACTYPE =  "Activity Type in the Transaction
   I_OVERAL_CONTENS =  "Packing Overview: Items and Handling Units
   I_CHK_LIKP_TAB =  "Deliveries
   I_CHK_LIPS =  "Delivery Items
*  I_V51KO =  "Shipping Unit Processing: Header Data
   I_HEADER51 =  "HU_Processing: General Header Data
*  I_HU_OBJECTS_TAB =  "Table with HU Objects
   I_VEKP_SEL_REC =  "Work Structure for Handling Unit Header
   I_VEKP_TAB =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   I_VEPO_TAB =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

 IMPORTING
   E_CALLBACK_PRG =  "ABAP Program Name
   E_CALLBACK_DYNNR =  "Number of the Following Screen

EXCEPTIONS
   PACKING_NOT_ALLOWED = 1
.



IMPORTING Parameters details for DGHU_DL02_DETAIL_SCREEN_OPEN

I_ACTYPE - Activity Type in the Transaction

Data type: AKTYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_OVERAL_CONTENS - Packing Overview: Items and Handling Units

Data type: HUMV4_T
Optional: No
Call by Reference: Yes

I_CHK_LIKP_TAB - Deliveries

Data type: SHP_LIKP_T
Optional: No
Call by Reference: Yes

I_CHK_LIPS - Delivery Items

Data type: VLGGT_LIPSVB_T
Optional: No
Call by Reference: Yes

I_V51KO - Shipping Unit Processing: Header Data

Data type: V51KO
Optional: Yes
Call by Reference: Yes

I_HEADER51 - HU_Processing: General Header Data

Data type: HEADER51
Optional: No
Call by Reference: Yes

I_HU_OBJECTS_TAB - Table with HU Objects

Data type: HUM_OBJECT_T
Optional: Yes
Call by Reference: Yes

I_VEKP_SEL_REC - Work Structure for Handling Unit Header

Data type: VEKPVB
Optional: No
Call by Reference: Yes

I_VEKP_TAB - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: VSEP_T_VEKP
Optional: No
Call by Reference: Yes

I_VEPO_TAB - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: VSEP_T_VEPO
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for DGHU_DL02_DETAIL_SCREEN_OPEN

E_CALLBACK_PRG - ABAP Program Name

Data type: REPID
Optional: No
Call by Reference: No ( called with pass by value option)

E_CALLBACK_DYNNR - Number of the Following Screen

Data type: DYNNR
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PACKING_NOT_ALLOWED - Packing Not Allowed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DGHU_DL02_DETAIL_SCREEN_OPEN 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_actype  TYPE AKTYP, "   
lv_e_callback_prg  TYPE REPID, "   
lv_packing_not_allowed  TYPE REPID, "   
lv_i_overal_contens  TYPE HUMV4_T, "   
lv_i_chk_likp_tab  TYPE SHP_LIKP_T, "   
lv_e_callback_dynnr  TYPE DYNNR, "   
lv_i_chk_lips  TYPE VLGGT_LIPSVB_T, "   
lv_i_v51ko  TYPE V51KO, "   
lv_i_header51  TYPE HEADER51, "   
lv_i_hu_objects_tab  TYPE HUM_OBJECT_T, "   
lv_i_vekp_sel_rec  TYPE VEKPVB, "   
lv_i_vekp_tab  TYPE VSEP_T_VEKP, "   
lv_i_vepo_tab  TYPE VSEP_T_VEPO. "   

  CALL FUNCTION 'DGHU_DL02_DETAIL_SCREEN_OPEN'  "NOTRANSL: GG: Aufruf GG-Prüfung und Dialog Vorschlag Verpackungsmaterial z
    EXPORTING
         I_ACTYPE = lv_i_actype
         I_OVERAL_CONTENS = lv_i_overal_contens
         I_CHK_LIKP_TAB = lv_i_chk_likp_tab
         I_CHK_LIPS = lv_i_chk_lips
         I_V51KO = lv_i_v51ko
         I_HEADER51 = lv_i_header51
         I_HU_OBJECTS_TAB = lv_i_hu_objects_tab
         I_VEKP_SEL_REC = lv_i_vekp_sel_rec
         I_VEKP_TAB = lv_i_vekp_tab
         I_VEPO_TAB = lv_i_vepo_tab
    IMPORTING
         E_CALLBACK_PRG = lv_e_callback_prg
         E_CALLBACK_DYNNR = lv_e_callback_dynnr
    EXCEPTIONS
        PACKING_NOT_ALLOWED = 1
. " DGHU_DL02_DETAIL_SCREEN_OPEN




ABAP code using 7.40 inline data declarations to call FM DGHU_DL02_DETAIL_SCREEN_OPEN

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!