SAP ISP_GET_PPE2BBE Function Module for IS-M/AM: Read Planned PU for a Basic BU









ISP_GET_PPE2BBE is a standard isp get ppe2bbe 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: Read Planned PU for a Basic BU 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 isp get ppe2bbe FM, simply by entering the name ISP_GET_PPE2BBE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_GET_PPE2BBE 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_GET_PPE2BBE'"IS-M/AM: Read Planned PU for a Basic BU
EXPORTING
BASIS_BE = "
* IN_MAX_BUFFER_SIZE = 30 "
* IN_CLEAR_BUFFER = ' ' "

IMPORTING
JJTPPE_WA = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for ISP_GET_PPE2BBE

BASIS_BE -

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

IN_MAX_BUFFER_SIZE -

Data type: SY-TFILL
Default: 30
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_CLEAR_BUFFER -

Data type: SY-BATCH
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_GET_PPE2BBE

JJTPPE_WA -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for ISP_GET_PPE2BBE 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_basis_be  TYPE JJTBE-BELEINH, "   
lv_jjtppe_wa  TYPE JJTPPE, "   
lv_not_found  TYPE JJTPPE, "   
lv_in_max_buffer_size  TYPE SY-TFILL, "   30
lv_in_clear_buffer  TYPE SY-BATCH. "   SPACE

  CALL FUNCTION 'ISP_GET_PPE2BBE'  "IS-M/AM: Read Planned PU for a Basic BU
    EXPORTING
         BASIS_BE = lv_basis_be
         IN_MAX_BUFFER_SIZE = lv_in_max_buffer_size
         IN_CLEAR_BUFFER = lv_in_clear_buffer
    IMPORTING
         JJTPPE_WA = lv_jjtppe_wa
    EXCEPTIONS
        NOT_FOUND = 1
. " ISP_GET_PPE2BBE




ABAP code using 7.40 inline data declarations to call FM ISP_GET_PPE2BBE

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 BELEINH FROM JJTBE INTO @DATA(ld_basis_be).
 
 
 
"SELECT single TFILL FROM SY INTO @DATA(ld_in_max_buffer_size).
DATA(ld_in_max_buffer_size) = 30.
 
"SELECT single BATCH FROM SY INTO @DATA(ld_in_clear_buffer).
DATA(ld_in_clear_buffer) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!