SAP JIT01_MODIFY_JITIT_BWFLAG Function Module for NOTRANSL: JIT: Modifizieren des BW-Flags in DB-Tabelle JITIT (Teilegruppe)
JIT01_MODIFY_JITIT_BWFLAG is a standard jit01 modify jitit bwflag 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: JIT: Modifizieren des BW-Flags in DB-Tabelle JITIT (Teilegruppe) 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 jit01 modify jitit bwflag FM, simply by entering the name JIT01_MODIFY_JITIT_BWFLAG into the relevant SAP transaction such as SE37 or SE38.
Function Group: JIT01
Program Name: SAPLJIT01
Main Program: SAPLJIT01
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function JIT01_MODIFY_JITIT_BWFLAG 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 'JIT01_MODIFY_JITIT_BWFLAG'"NOTRANSL: JIT: Modifizieren des BW-Flags in DB-Tabelle JITIT (Teilegruppe).
TABLES
JITITBW_IT = "Generated Table for View
EXCEPTIONS
ENTRY_NOT_EXIST = 1
TABLES Parameters details for JIT01_MODIFY_JITIT_BWFLAG
JITITBW_IT - Generated Table for View
Data type: V_JITITBWOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ENTRY_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JIT01_MODIFY_JITIT_BWFLAG 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_jititbw_it | TYPE STANDARD TABLE OF V_JITITBW, " | |||
| lv_entry_not_exist | TYPE V_JITITBW. " |
|   CALL FUNCTION 'JIT01_MODIFY_JITIT_BWFLAG' "NOTRANSL: JIT: Modifizieren des BW-Flags in DB-Tabelle JITIT (Teilegruppe) |
| TABLES | ||
| JITITBW_IT | = lt_jititbw_it | |
| EXCEPTIONS | ||
| ENTRY_NOT_EXIST = 1 | ||
| . " JIT01_MODIFY_JITIT_BWFLAG | ||
ABAP code using 7.40 inline data declarations to call FM JIT01_MODIFY_JITIT_BWFLAG
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