SAP GEN_EBPP_GET_CONTACTS Function Module for









GEN_EBPP_GET_CONTACTS is a standard gen ebpp get contacts 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 gen ebpp get contacts FM, simply by entering the name GEN_EBPP_GET_CONTACTS into the relevant SAP transaction such as SE37 or SE38.

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



Function GEN_EBPP_GET_CONTACTS 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 'GEN_EBPP_GET_CONTACTS'"
EXPORTING
I_PARTNER = "SAP Biller Direct: Partner Data
* INVID = "Bill Number of a Biller Direct Bill
* LANGUAGE_ISO = "SAP System, Current Language
* IX_BUILD_HTML_HEADERS = "
* IX_TABLES_OUTPUT = "
* IX_DELETE_CRS = 'X' "

IMPORTING
HTML_OUT = "
RETURN = "Return Parameter(s)
E_RETURNCODE = "Return Value, Return Value after ABAP Statements

TABLES
* CONTACTS = "Output Structure of Contacts
* TEXTLINES = "
* T_MESSAGES = "FSCM Biller Direct: Messages
.



IMPORTING Parameters details for GEN_EBPP_GET_CONTACTS

I_PARTNER - SAP Biller Direct: Partner Data

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

INVID - Bill Number of a Biller Direct Bill

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

LANGUAGE_ISO - SAP System, Current Language

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

IX_BUILD_HTML_HEADERS -

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

IX_TABLES_OUTPUT -

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

IX_DELETE_CRS -

Data type: BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GEN_EBPP_GET_CONTACTS

HTML_OUT -

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

RETURN - Return Parameter(s)

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

E_RETURNCODE - Return Value, Return Value after ABAP Statements

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

TABLES Parameters details for GEN_EBPP_GET_CONTACTS

CONTACTS - Output Structure of Contacts

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

TEXTLINES -

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

T_MESSAGES - FSCM Biller Direct: Messages

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

Copy and paste ABAP code example for GEN_EBPP_GET_CONTACTS 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:
lt_contacts  TYPE STANDARD TABLE OF EBPP_CONTACTOUT, "   
lv_html_out  TYPE STRING, "   
lv_i_partner  TYPE GENEBPP_PARTNER, "   
lv_invid  TYPE EBPP_INVID, "   
lv_return  TYPE BAPIRET1, "   
lt_textlines  TYPE STANDARD TABLE OF TLINE, "   
lt_t_messages  TYPE STANDARD TABLE OF GENEBPP_MSG, "   
lv_e_returncode  TYPE SY-SUBRC, "   
lv_language_iso  TYPE LAISO, "   
lv_ix_build_html_headers  TYPE BOOLEAN, "   
lv_ix_tables_output  TYPE BOOLEAN, "   
lv_ix_delete_crs  TYPE BOOLEAN. "   'X'

  CALL FUNCTION 'GEN_EBPP_GET_CONTACTS'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         INVID = lv_invid
         LANGUAGE_ISO = lv_language_iso
         IX_BUILD_HTML_HEADERS = lv_ix_build_html_headers
         IX_TABLES_OUTPUT = lv_ix_tables_output
         IX_DELETE_CRS = lv_ix_delete_crs
    IMPORTING
         HTML_OUT = lv_html_out
         RETURN = lv_return
         E_RETURNCODE = lv_e_returncode
    TABLES
         CONTACTS = lt_contacts
         TEXTLINES = lt_textlines
         T_MESSAGES = lt_t_messages
. " GEN_EBPP_GET_CONTACTS




ABAP code using 7.40 inline data declarations to call FM GEN_EBPP_GET_CONTACTS

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).
 
 
 
 
DATA(ld_ix_delete_crs) = 'X'.
 


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!