SAP APAR_EBPP_KNB1_EXT_GETLIST Function Module for









APAR_EBPP_KNB1_EXT_GETLIST is a standard apar ebpp knb1 ext getlist 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 apar ebpp knb1 ext getlist FM, simply by entering the name APAR_EBPP_KNB1_EXT_GETLIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: APAR_EBPP_KNB1_EXT
Program Name: SAPLAPAR_EBPP_KNB1_EXT
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function APAR_EBPP_KNB1_EXT_GETLIST 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 'APAR_EBPP_KNB1_EXT_GETLIST'"
EXPORTING
I_PARTNER = "
* I_ADDSEL = "

IMPORTING
E_RETURNCODE = "
RETURN = "

TABLES
* T_MESSAGES = "
* T_EBPP_ADDSEL = "
.



IMPORTING Parameters details for APAR_EBPP_KNB1_EXT_GETLIST

I_PARTNER -

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

I_ADDSEL -

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

EXPORTING Parameters details for APAR_EBPP_KNB1_EXT_GETLIST

E_RETURNCODE -

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

RETURN -

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

TABLES Parameters details for APAR_EBPP_KNB1_EXT_GETLIST

T_MESSAGES -

Data type: EBPP_MESSAGES
Optional: Yes
Call by Reference: Yes

T_EBPP_ADDSEL -

Data type: APAREBPP_KNB1_ADDSEL
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for APAR_EBPP_KNB1_EXT_GETLIST 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_i_partner  TYPE EBPP_PARTNER, "   
lt_t_messages  TYPE STANDARD TABLE OF EBPP_MESSAGES, "   
lv_e_returncode  TYPE SY-SUBRC, "   
lv_return  TYPE BAPIRET1, "   
lv_i_addsel  TYPE EBPP_ADDSEL, "   
lt_t_ebpp_addsel  TYPE STANDARD TABLE OF APAREBPP_KNB1_ADDSEL. "   

  CALL FUNCTION 'APAR_EBPP_KNB1_EXT_GETLIST'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_ADDSEL = lv_i_addsel
    IMPORTING
         E_RETURNCODE = lv_e_returncode
         RETURN = lv_return
    TABLES
         T_MESSAGES = lt_t_messages
         T_EBPP_ADDSEL = lt_t_ebpp_addsel
. " APAR_EBPP_KNB1_EXT_GETLIST




ABAP code using 7.40 inline data declarations to call FM APAR_EBPP_KNB1_EXT_GETLIST

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 SUBRC FROM SY INTO @DATA(ld_e_returncode).
 
 
 
 


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!