SAP J_1B_IM_TF_BWART_GI_REL Function Module for NOTRANSL: Check whether bwart is for GI - TF with STO
J_1B_IM_TF_BWART_GI_REL is a standard j 1b im tf bwart gi rel 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: Check whether bwart is for GI - TF with STO 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 j 1b im tf bwart gi rel FM, simply by entering the name J_1B_IM_TF_BWART_GI_REL into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1BN
Program Name: SAPLJ1BN
Main Program: SAPLJ1BN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1B_IM_TF_BWART_GI_REL 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 'J_1B_IM_TF_BWART_GI_REL'"NOTRANSL: Check whether bwart is for GI - TF with STO.
EXPORTING
I_BR_ACTIVE = "
I_BWART = "Movement Type (Inventory Management)
IMPORTING
E_TF_GI_ACTIVE = "
IMPORTING Parameters details for J_1B_IM_TF_BWART_GI_REL
I_BR_ACTIVE -
Data type: COptional: No
Call by Reference: Yes
I_BWART - Movement Type (Inventory Management)
Data type: T156-BWARTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for J_1B_IM_TF_BWART_GI_REL
E_TF_GI_ACTIVE -
Data type: COptional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1B_IM_TF_BWART_GI_REL 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_br_active | TYPE C, " | |||
| lv_e_tf_gi_active | TYPE C, " | |||
| lv_i_bwart | TYPE T156-BWART. " |
|   CALL FUNCTION 'J_1B_IM_TF_BWART_GI_REL' "NOTRANSL: Check whether bwart is for GI - TF with STO |
| EXPORTING | ||
| I_BR_ACTIVE | = lv_i_br_active | |
| I_BWART | = lv_i_bwart | |
| IMPORTING | ||
| E_TF_GI_ACTIVE | = lv_e_tf_gi_active | |
| . " J_1B_IM_TF_BWART_GI_REL | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_IM_TF_BWART_GI_REL
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 BWART FROM T156 INTO @DATA(ld_i_bwart). | ||||
Search for further information about these or an SAP related objects