SAP ISM_JGBP_JGTBKUS_SELECT Function Module for
ISM_JGBP_JGTBKUS_SELECT is a standard ism jgbp jgtbkus select 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 ism jgbp jgtbkus select FM, simply by entering the name ISM_JGBP_JGTBKUS_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JGBP_SELECT
Program Name: SAPLJGBP_SELECT
Main Program: SAPLJGBP_SELECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_JGBP_JGTBKUS_SELECT 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 'ISM_JGBP_JGTBKUS_SELECT'".
EXPORTING
PV_PARTNER = "
IMPORTING
PT_JGTBKUS = "
EXCEPTIONS
NO_ENTRY_FOUND = 1
IMPORTING Parameters details for ISM_JGBP_JGTBKUS_SELECT
PV_PARTNER -
Data type: BU_PARTNEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_JGBP_JGTBKUS_SELECT
PT_JGTBKUS -
Data type: JGTBKUS_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_JGBP_JGTBKUS_SELECT 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_pt_jgtbkus | TYPE JGTBKUS_TAB, " | |||
| lv_pv_partner | TYPE BU_PARTNER, " | |||
| lv_no_entry_found | TYPE BU_PARTNER. " |
|   CALL FUNCTION 'ISM_JGBP_JGTBKUS_SELECT' " |
| EXPORTING | ||
| PV_PARTNER | = lv_pv_partner | |
| IMPORTING | ||
| PT_JGTBKUS | = lv_pt_jgtbkus | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND = 1 | ||
| . " ISM_JGBP_JGTBKUS_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM ISM_JGBP_JGTBKUS_SELECT
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