SAP JITOUT02_MODIFY_DLCNOHD Function Module for NOTRANSL: Modifizieren von Einträgen in der Tabelle DLCNOHD
JITOUT02_MODIFY_DLCNOHD is a standard jitout02 modify dlcnohd 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: Modifizieren von Einträgen in der Tabelle DLCNOHD 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 jitout02 modify dlcnohd FM, simply by entering the name JITOUT02_MODIFY_DLCNOHD into the relevant SAP transaction such as SE37 or SE38.
Function Group: JITOUT02
Program Name: SAPLJITOUT02
Main Program: SAPLJITOUT02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function JITOUT02_MODIFY_DLCNOHD 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 'JITOUT02_MODIFY_DLCNOHD'"NOTRANSL: Modifizieren von Einträgen in der Tabelle DLCNOHD.
EXPORTING
DLCNOHD_IT = "Delivery Confirmations Header
EXCEPTIONS
ERROR_DURING_MODIFY = 1
IMPORTING Parameters details for JITOUT02_MODIFY_DLCNOHD
DLCNOHD_IT - Delivery Confirmations Header
Data type: DLCNOHD_TTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_DURING_MODIFY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for JITOUT02_MODIFY_DLCNOHD 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_dlcnohd_it | TYPE DLCNOHD_TT, " | |||
| lv_error_during_modify | TYPE DLCNOHD_TT. " |
|   CALL FUNCTION 'JITOUT02_MODIFY_DLCNOHD' "NOTRANSL: Modifizieren von Einträgen in der Tabelle DLCNOHD |
| EXPORTING | ||
| DLCNOHD_IT | = lv_dlcnohd_it | |
| EXCEPTIONS | ||
| ERROR_DURING_MODIFY = 1 | ||
| . " JITOUT02_MODIFY_DLCNOHD | ||
ABAP code using 7.40 inline data declarations to call FM JITOUT02_MODIFY_DLCNOHD
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