SAP APAR_EBPP_ADD_CONTACT Function Module for









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

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



Function APAR_EBPP_ADD_CONTACT 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_ADD_CONTACT'"
EXPORTING
I_PARTNER = "
I_LONGTEXT = "
* I_DISPUTEREASON = "

IMPORTING
E_NEWCONTACT = "
E_RETURNCODE = "
RETURN = "

TABLES
* T_INVOICE_IDS = "
* T_MESSAGES = "
.



IMPORTING Parameters details for APAR_EBPP_ADD_CONTACT

I_PARTNER -

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

I_LONGTEXT -

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

I_DISPUTEREASON -

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

EXPORTING Parameters details for APAR_EBPP_ADD_CONTACT

E_NEWCONTACT -

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

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_ADD_CONTACT

T_INVOICE_IDS -

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

T_MESSAGES -

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

Copy and paste ABAP code example for APAR_EBPP_ADD_CONTACT 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, "   
lv_e_newcontact  TYPE EBPP_CONTACT, "   
lt_t_invoice_ids  TYPE STANDARD TABLE OF EBPP_INVOICE_ID, "   
lv_i_longtext  TYPE EBPP_INVOICE-DOCT1, "   
lt_t_messages  TYPE STANDARD TABLE OF EBPP_MESSAGES, "   
lv_e_returncode  TYPE SY-SUBRC, "   
lv_return  TYPE BAPIRET1, "   
lv_i_disputereason  TYPE EBPP_DISPUTEREASON. "   

  CALL FUNCTION 'APAR_EBPP_ADD_CONTACT'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_LONGTEXT = lv_i_longtext
         I_DISPUTEREASON = lv_i_disputereason
    IMPORTING
         E_NEWCONTACT = lv_e_newcontact
         E_RETURNCODE = lv_e_returncode
         RETURN = lv_return
    TABLES
         T_INVOICE_IDS = lt_t_invoice_ids
         T_MESSAGES = lt_t_messages
. " APAR_EBPP_ADD_CONTACT




ABAP code using 7.40 inline data declarations to call FM APAR_EBPP_ADD_CONTACT

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 DOCT1 FROM EBPP_INVOICE INTO @DATA(ld_i_longtext).
 
 
"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!