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

Function JITOUT01_MODIFY_JITOIT 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 'JITOUT01_MODIFY_JITOIT'"NOTRANSL: Verändern von Einträgen in der Tabelle JITOIT.
EXPORTING
JITOIT_IT = "JIT Outbound Components Group
EXCEPTIONS
ENTRY_DOES_NOT_EXIST = 1
IMPORTING Parameters details for JITOUT01_MODIFY_JITOIT
JITOIT_IT - JIT Outbound Components Group
Data type: JITOIT_TTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ENTRY_DOES_NOT_EXIST - Entry does not exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for JITOUT01_MODIFY_JITOIT 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_jitoit_it | TYPE JITOIT_TT, " | |||
| lv_entry_does_not_exist | TYPE JITOIT_TT. " |
|   CALL FUNCTION 'JITOUT01_MODIFY_JITOIT' "NOTRANSL: Verändern von Einträgen in der Tabelle JITOIT |
| EXPORTING | ||
| JITOIT_IT | = lv_jitoit_it | |
| EXCEPTIONS | ||
| ENTRY_DOES_NOT_EXIST = 1 | ||
| . " JITOUT01_MODIFY_JITOIT | ||
ABAP code using 7.40 inline data declarations to call FM JITOUT01_MODIFY_JITOIT
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