SAP ISM_BE_QUANTITIES_GET Function Module for
ISM_BE_QUANTITIES_GET is a standard ism be quantities get 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 be quantities get FM, simply by entering the name ISM_BE_QUANTITIES_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHSD
Program Name: SAPLJHSD
Main Program: SAPLJHSD
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_BE_QUANTITIES_GET 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_BE_QUANTITIES_GET'".
EXPORTING
IN_BE = "
IN_DATE = "
* XPLANNING_QUANTITIES = "
* XACTUAL_QUANTITIES = "
IMPORTING
BE_POTENTIAL_PLAN = "
BE_SI_MENGERH_PLAN = "
BE_POSTMENGE_PLAN = "
BE_JVERTPOTNT_PLAN = "
TABLES
* LFNG_TAB_PLAN = "
* BEPART_POT_TAB = "
* LFNG_TAB_BL_PLAN = "
* LFNG_TAB_RH_PLAN = "
* LFNG_TAB_POST_PLAN = "
* LFNG_TAB_BL_ACTUAL = "
* LFNG_TAB_RH_ACTUAL = "
* LFNG_TAB_POST_ACTUAL = "
* LFNG_TAB_VT_ACTUAL = "
* LFBK_TAB_VT_PLAN = "
IMPORTING Parameters details for ISM_BE_QUANTITIES_GET
IN_BE -
Data type: JHAES-BELEGEINHOptional: No
Call by Reference: No ( called with pass by value option)
IN_DATE -
Data type: JHAES-ERSCHDATOptional: No
Call by Reference: No ( called with pass by value option)
XPLANNING_QUANTITIES -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
XACTUAL_QUANTITIES -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISM_BE_QUANTITIES_GET
BE_POTENTIAL_PLAN -
Data type: JJTBEVARI-POTENTIALOptional: No
Call by Reference: No ( called with pass by value option)
BE_SI_MENGERH_PLAN -
Data type: JJTBEVARI-SI_MENGERHOptional: No
Call by Reference: No ( called with pass by value option)
BE_POSTMENGE_PLAN -
Data type: JJTBEVARI-POSTMENGEOptional: No
Call by Reference: No ( called with pass by value option)
BE_JVERTPOTNT_PLAN -
Data type: JJTBEBVTP-JVERTPOTNTLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISM_BE_QUANTITIES_GET
LFNG_TAB_PLAN -
Data type: JVTLFNGOptional: Yes
Call by Reference: No ( called with pass by value option)
BEPART_POT_TAB -
Data type: RJJBEPART_POTOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_BL_PLAN -
Data type: JVTLFNGOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_RH_PLAN -
Data type: RJV08LFNGRHOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_POST_PLAN -
Data type: JVTLFNGOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_BL_ACTUAL -
Data type: RJV08LFNG_SIOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_RH_ACTUAL -
Data type: RJV08LFNG_SIOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_POST_ACTUAL -
Data type: RJV08LFNG_SIOptional: Yes
Call by Reference: No ( called with pass by value option)
LFNG_TAB_VT_ACTUAL -
Data type: RJV08LFNG_SIOptional: Yes
Call by Reference: No ( called with pass by value option)
LFBK_TAB_VT_PLAN -
Data type: JH07_JJTBEBVT_EXPAND_POT_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_BE_QUANTITIES_GET 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_in_be | TYPE JHAES-BELEGEINH, " | |||
| lt_lfng_tab_plan | TYPE STANDARD TABLE OF JVTLFNG, " | |||
| lv_be_potential_plan | TYPE JJTBEVARI-POTENTIAL, " | |||
| lt_bepart_pot_tab | TYPE STANDARD TABLE OF RJJBEPART_POT, " | |||
| lv_in_date | TYPE JHAES-ERSCHDAT, " | |||
| lt_lfng_tab_bl_plan | TYPE STANDARD TABLE OF JVTLFNG, " | |||
| lv_be_si_mengerh_plan | TYPE JJTBEVARI-SI_MENGERH, " | |||
| lt_lfng_tab_rh_plan | TYPE STANDARD TABLE OF RJV08LFNGRH, " | |||
| lv_be_postmenge_plan | TYPE JJTBEVARI-POSTMENGE, " | |||
| lv_xplanning_quantities | TYPE JJTBEVARI, " | |||
| lv_be_jvertpotnt_plan | TYPE JJTBEBVTP-JVERTPOTNTL, " | |||
| lt_lfng_tab_post_plan | TYPE STANDARD TABLE OF JVTLFNG, " | |||
| lv_xactual_quantities | TYPE JVTLFNG, " | |||
| lt_lfng_tab_bl_actual | TYPE STANDARD TABLE OF RJV08LFNG_SI, " | |||
| lt_lfng_tab_rh_actual | TYPE STANDARD TABLE OF RJV08LFNG_SI, " | |||
| lt_lfng_tab_post_actual | TYPE STANDARD TABLE OF RJV08LFNG_SI, " | |||
| lt_lfng_tab_vt_actual | TYPE STANDARD TABLE OF RJV08LFNG_SI, " | |||
| lt_lfbk_tab_vt_plan | TYPE STANDARD TABLE OF JH07_JJTBEBVT_EXPAND_POT_TAB. " |
|   CALL FUNCTION 'ISM_BE_QUANTITIES_GET' " |
| EXPORTING | ||
| IN_BE | = lv_in_be | |
| IN_DATE | = lv_in_date | |
| XPLANNING_QUANTITIES | = lv_xplanning_quantities | |
| XACTUAL_QUANTITIES | = lv_xactual_quantities | |
| IMPORTING | ||
| BE_POTENTIAL_PLAN | = lv_be_potential_plan | |
| BE_SI_MENGERH_PLAN | = lv_be_si_mengerh_plan | |
| BE_POSTMENGE_PLAN | = lv_be_postmenge_plan | |
| BE_JVERTPOTNT_PLAN | = lv_be_jvertpotnt_plan | |
| TABLES | ||
| LFNG_TAB_PLAN | = lt_lfng_tab_plan | |
| BEPART_POT_TAB | = lt_bepart_pot_tab | |
| LFNG_TAB_BL_PLAN | = lt_lfng_tab_bl_plan | |
| LFNG_TAB_RH_PLAN | = lt_lfng_tab_rh_plan | |
| LFNG_TAB_POST_PLAN | = lt_lfng_tab_post_plan | |
| LFNG_TAB_BL_ACTUAL | = lt_lfng_tab_bl_actual | |
| LFNG_TAB_RH_ACTUAL | = lt_lfng_tab_rh_actual | |
| LFNG_TAB_POST_ACTUAL | = lt_lfng_tab_post_actual | |
| LFNG_TAB_VT_ACTUAL | = lt_lfng_tab_vt_actual | |
| LFBK_TAB_VT_PLAN | = lt_lfbk_tab_vt_plan | |
| . " ISM_BE_QUANTITIES_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISM_BE_QUANTITIES_GET
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 BELEGEINH FROM JHAES INTO @DATA(ld_in_be). | ||||
| "SELECT single POTENTIAL FROM JJTBEVARI INTO @DATA(ld_be_potential_plan). | ||||
| "SELECT single ERSCHDAT FROM JHAES INTO @DATA(ld_in_date). | ||||
| "SELECT single SI_MENGERH FROM JJTBEVARI INTO @DATA(ld_be_si_mengerh_plan). | ||||
| "SELECT single POSTMENGE FROM JJTBEVARI INTO @DATA(ld_be_postmenge_plan). | ||||
| "SELECT single JVERTPOTNTL FROM JJTBEBVTP INTO @DATA(ld_be_jvertpotnt_plan). | ||||
Search for further information about these or an SAP related objects