SAP ISM_VBEHIE_UTIL_JJTBEVARI_READ Function Module for IS-M/AM: Sales Booking Unit Hierarchy: Read Potentials for AI BUs

Search SAP Function Modules

ISM_VBEHIE_UTIL_JJTBEVARI_READ is a standard ism vbehie util jjtbevari read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/AM: Sales Booking Unit Hierarchy: Read Potentials for AI BUs 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 ism vbehie util jjtbevari read FM, simply by entering the name ISM_VBEHIE_UTIL_JJTBEVARI_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: JJBE
Program Name: SAPLJJBE
Main Program: SAPLJJBE
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_VBEHIE_UTIL_JJTBEVARI_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 'ISM_VBEHIE_UTIL_JJTBEVARI_READ'"IS-M/AM: Sales Booking Unit Hierarchy: Read Potentials for AI BUs
  EXPORTING
   PV_BEVARTYP =  "
   PV_BELEINH =  "
   PV_GUELTIGVON =  "
*  PV_GUELTIGBIS =  "

 IMPORTING
   PS_JJTBEVARI =  "
   PT_JJTBEVARI =  "
   PV_JJTBEVARI_CNT =  "
   PV_POTENT_SRC =  "
   PV_XPOT_NOT_FOUND =  "
   PV_XPOT_NOT_UNIQUE =  "

.

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_SAPLJJBE_001 IS-M/AM: BU Work Hierarchy. Initialize Sorting
EXIT_SAPLJJBE_002 IS-M-AM: BU Work Hierarchy: Definition of Sort Criteria for Sorting

IMPORTING Parameters details for ISM_VBEHIE_UTIL_JJTBEVARI_READ

PV_BEVARTYP -

Data type: JJTBEVARI-BEVARTYP
Optional: No
Call by Reference: No ( called with pass by value option)

PV_BELEINH -

Data type: JJTBEVARI-BELEINH
Optional: No
Call by Reference: No ( called with pass by value option)

PV_GUELTIGVON -

Data type: JJTBEVARI-GUELTIGVON
Optional: No
Call by Reference: No ( called with pass by value option)

PV_GUELTIGBIS -

Data type: JJTBEVARI-GUELTIGBIS
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISM_VBEHIE_UTIL_JJTBEVARI_READ

PS_JJTBEVARI -

Data type: JJBE_JJTBEVARI_STR
Optional: No
Call by Reference: No ( called with pass by value option)

PT_JJTBEVARI -

Data type: JJBE_JJTBEVARI_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

PV_JJTBEVARI_CNT -

Data type: SY-TABIX
Optional: No
Call by Reference: No ( called with pass by value option)

PV_POTENT_SRC -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PV_XPOT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PV_XPOT_NOT_UNIQUE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISM_VBEHIE_UTIL_JJTBEVARI_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.

ABAP code using 7.40 inline data declarations to call FM ISM_VBEHIE_UTIL_JJTBEVARI_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.

Search for further information about these or an SAP related objects