SAP ISP_JHTVB_DIRECT_READ Function Module for
ISP_JHTVB_DIRECT_READ is a standard isp jhtvb direct read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 isp jhtvb direct read FM, simply by entering the name ISP_JHTVB_DIRECT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHAB
Program Name: SAPLJHAB
Main Program: SAPLJHAB
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_JHTVB_DIRECT_READ 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 'ISP_JHTVB_DIRECT_READ'".
EXPORTING
BEDNR_IN = "
SPART_IN = "
VKORG_IN = "
VTWEG_IN = "
* XWITH_POS = "
* XWITH_VBER = 'X' "
IMPORTING
JHTVB_OUT = "
X_LOEKZ = "
X_LOEVM = "
TABLES
* ABS_BEST = "
EXCEPTIONS
DELETED = 1 NOT_EXISTS = 2 NO_BEST = 3
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLJHAB_001 IS-M: Update Customer-Specific Contract Data
EXIT_SAPLJHAB_002 IS-M: Imported Customer-Specific Contract Data
EXIT_SAPLJHAB_003 IS-M: Initialize Customer-Specific Contract Data
IMPORTING Parameters details for ISP_JHTVB_DIRECT_READ
BEDNR_IN -
Data type: JHTVB-BEDNROptional: No
Call by Reference: No ( called with pass by value option)
SPART_IN -
Data type: JHTVB-SPARTOptional: No
Call by Reference: No ( called with pass by value option)
VKORG_IN -
Data type: JHTVB-VKORGOptional: No
Call by Reference: No ( called with pass by value option)
VTWEG_IN -
Data type: JHTVB-VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
XWITH_POS -
Data type: SY-BATCHOptional: Yes
Call by Reference: No ( called with pass by value option)
XWITH_VBER -
Data type: SY-BATCHDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_JHTVB_DIRECT_READ
JHTVB_OUT -
Data type: JHTVBOptional: No
Call by Reference: No ( called with pass by value option)
X_LOEKZ -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_LOEVM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_JHTVB_DIRECT_READ
ABS_BEST -
Data type: JHTVBPOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DELETED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_BEST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_JHTVB_DIRECT_READ 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_deleted | TYPE STRING, " | |||
| lt_abs_best | TYPE STANDARD TABLE OF JHTVBPO, " | |||
| lv_bednr_in | TYPE JHTVB-BEDNR, " | |||
| lv_jhtvb_out | TYPE JHTVB, " | |||
| lv_x_loekz | TYPE JHTVB, " | |||
| lv_spart_in | TYPE JHTVB-SPART, " | |||
| lv_not_exists | TYPE JHTVB, " | |||
| lv_no_best | TYPE JHTVB, " | |||
| lv_x_loevm | TYPE JHTVB, " | |||
| lv_vkorg_in | TYPE JHTVB-VKORG, " | |||
| lv_vtweg_in | TYPE JHTVB-VTWEG, " | |||
| lv_xwith_pos | TYPE SY-BATCH, " | |||
| lv_xwith_vber | TYPE SY-BATCH. " 'X' |
|   CALL FUNCTION 'ISP_JHTVB_DIRECT_READ' " |
| EXPORTING | ||
| BEDNR_IN | = lv_bednr_in | |
| SPART_IN | = lv_spart_in | |
| VKORG_IN | = lv_vkorg_in | |
| VTWEG_IN | = lv_vtweg_in | |
| XWITH_POS | = lv_xwith_pos | |
| XWITH_VBER | = lv_xwith_vber | |
| IMPORTING | ||
| JHTVB_OUT | = lv_jhtvb_out | |
| X_LOEKZ | = lv_x_loekz | |
| X_LOEVM | = lv_x_loevm | |
| TABLES | ||
| ABS_BEST | = lt_abs_best | |
| EXCEPTIONS | ||
| DELETED = 1 | ||
| NOT_EXISTS = 2 | ||
| NO_BEST = 3 | ||
| . " ISP_JHTVB_DIRECT_READ | ||
ABAP code using 7.40 inline data declarations to call FM ISP_JHTVB_DIRECT_READ
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 BEDNR FROM JHTVB INTO @DATA(ld_bednr_in). | ||||
| "SELECT single SPART FROM JHTVB INTO @DATA(ld_spart_in). | ||||
| "SELECT single VKORG FROM JHTVB INTO @DATA(ld_vkorg_in). | ||||
| "SELECT single VTWEG FROM JHTVB INTO @DATA(ld_vtweg_in). | ||||
| "SELECT single BATCH FROM SY INTO @DATA(ld_xwith_pos). | ||||
| "SELECT single BATCH FROM SY INTO @DATA(ld_xwith_vber). | ||||
| DATA(ld_xwith_vber) | = 'X'. | |||
Search for further information about these or an SAP related objects