SAP HAZMAT_DGTPK_SAVE_WITH_REQUEST Function Module for NOTRANSL: GG-Pack: Sichert die Inhalte (IOTABS, Puffer) mit Benutzeranfrag
HAZMAT_DGTPK_SAVE_WITH_REQUEST is a standard hazmat dgtpk save with request 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-Pack: Sichert die Inhalte (IOTABS, Puffer) mit Benutzeranfrag 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 hazmat dgtpk save with request FM, simply by entering the name HAZMAT_DGTPK_SAVE_WITH_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: DG11
Program Name: SAPLDG11
Main Program: SAPLDG11
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HAZMAT_DGTPK_SAVE_WITH_REQUEST 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 'HAZMAT_DGTPK_SAVE_WITH_REQUEST'"NOTRANSL: GG-Pack: Sichert die Inhalte (IOTABS, Puffer) mit Benutzeranfrag.
EXPORTING
* I_FLG_SYNCHRONUS_PROCESSING = ESP1_FALSE "
* I_FLG_WITH_COMMIT = ESP1_TRUE "
IMPORTING
E_FLG_CHANGENUM_COLL = "Indicator: Data record is currently valid
E_FLG_USER_ANSWER = "Generic Type
TABLES
X_IOTAB_PK = "
X_IOTAB_PK_DEL = "
EXCEPTIONS
BUFFER_NOT_INITIALIZED = 1
IMPORTING Parameters details for HAZMAT_DGTPK_SAVE_WITH_REQUEST
I_FLG_SYNCHRONUS_PROCESSING -
Data type: ESP1_BOOLEANDefault: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_WITH_COMMIT -
Data type: ESP1_BOOLEANDefault: ESP1_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HAZMAT_DGTPK_SAVE_WITH_REQUEST
E_FLG_CHANGENUM_COLL - Indicator: Data record is currently valid
Data type: RCGRHBUF-VALFLGOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_USER_ANSWER - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HAZMAT_DGTPK_SAVE_WITH_REQUEST
X_IOTAB_PK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_IOTAB_PK_DEL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BUFFER_NOT_INITIALIZED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HAZMAT_DGTPK_SAVE_WITH_REQUEST 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: | ||||
lt_x_iotab_pk | TYPE STANDARD TABLE OF STRING, " | |||
lv_e_flg_changenum_coll | TYPE RCGRHBUF-VALFLG, " | |||
lv_buffer_not_initialized | TYPE RCGRHBUF, " | |||
lv_i_flg_synchronus_processing | TYPE ESP1_BOOLEAN, " ESP1_FALSE | |||
lt_x_iotab_pk_del | TYPE STANDARD TABLE OF ESP1_BOOLEAN, " | |||
lv_e_flg_user_answer | TYPE C, " | |||
lv_i_flg_with_commit | TYPE ESP1_BOOLEAN. " ESP1_TRUE |
  CALL FUNCTION 'HAZMAT_DGTPK_SAVE_WITH_REQUEST' "NOTRANSL: GG-Pack: Sichert die Inhalte (IOTABS, Puffer) mit Benutzeranfrag |
EXPORTING | ||
I_FLG_SYNCHRONUS_PROCESSING | = lv_i_flg_synchronus_processing | |
I_FLG_WITH_COMMIT | = lv_i_flg_with_commit | |
IMPORTING | ||
E_FLG_CHANGENUM_COLL | = lv_e_flg_changenum_coll | |
E_FLG_USER_ANSWER | = lv_e_flg_user_answer | |
TABLES | ||
X_IOTAB_PK | = lt_x_iotab_pk | |
X_IOTAB_PK_DEL | = lt_x_iotab_pk_del | |
EXCEPTIONS | ||
BUFFER_NOT_INITIALIZED = 1 | ||
. " HAZMAT_DGTPK_SAVE_WITH_REQUEST |
ABAP code using 7.40 inline data declarations to call FM HAZMAT_DGTPK_SAVE_WITH_REQUEST
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 VALFLG FROM RCGRHBUF INTO @DATA(ld_e_flg_changenum_coll). | ||||
DATA(ld_i_flg_synchronus_processing) | = ESP1_FALSE. | |||
DATA(ld_i_flg_with_commit) | = ESP1_TRUE. | |||
Search for further information about these or an SAP related objects