SAP FKK_EBPP_ADD_CONTACT Function Module for
FKK_EBPP_ADD_CONTACT is a standard fkk 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 fkk ebpp add contact FM, simply by entering the name FKK_EBPP_ADD_CONTACT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_EBPP
Program Name: SAPLFKK_EBPP
Main Program: SAPLFKK_EBPP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FKK_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 'FKK_EBPP_ADD_CONTACT'".
EXPORTING
I_GPART = "Business Partner Number
I_LONGTEXT = "Text with Length 1024
* I_ACTIVITY = "Sales Activity Action
I_PARTNER = "SAP Biller Direct: Partner Data
IMPORTING
E_NEWCONTACT = "Business partner contact
E_RETURNCODE = "Return Value, Return Value after ABAP Statements
TABLES
* T_INVOICE_IDS = "FSCM Biller Direct: Bill Data (IDs)
EXCEPTIONS
INCOMPLETE_CUSTOMIZING = 1
IMPORTING Parameters details for FKK_EBPP_ADD_CONTACT
I_GPART - Business Partner Number
Data type: FKKOP-GPARTOptional: No
Call by Reference: No ( called with pass by value option)
I_LONGTEXT - Text with Length 1024
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTIVITY - Sales Activity Action
Data type: BCONTA-ACTIVITYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNER - SAP Biller Direct: Partner Data
Data type: GENEBPP_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_EBPP_ADD_CONTACT
E_NEWCONTACT - Business partner contact
Data type: BCONT-BPCONTACTOptional: No
Call by Reference: No ( called with pass by value option)
E_RETURNCODE - Return Value, Return Value after ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FKK_EBPP_ADD_CONTACT
T_INVOICE_IDS - FSCM Biller Direct: Bill Data (IDs)
Data type: GENEBPP_INVOICE_IDOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INCOMPLETE_CUSTOMIZING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_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_gpart | TYPE FKKOP-GPART, " | |||
| lv_e_newcontact | TYPE BCONT-BPCONTACT, " | |||
| lt_t_invoice_ids | TYPE STANDARD TABLE OF GENEBPP_INVOICE_ID, " | |||
| lv_incomplete_customizing | TYPE GENEBPP_INVOICE_ID, " | |||
| lv_i_longtext | TYPE STRING, " | |||
| lv_e_returncode | TYPE SY-SUBRC, " | |||
| lv_i_activity | TYPE BCONTA-ACTIVITY, " | |||
| lv_i_partner | TYPE GENEBPP_PARTNER. " |
|   CALL FUNCTION 'FKK_EBPP_ADD_CONTACT' " |
| EXPORTING | ||
| I_GPART | = lv_i_gpart | |
| I_LONGTEXT | = lv_i_longtext | |
| I_ACTIVITY | = lv_i_activity | |
| I_PARTNER | = lv_i_partner | |
| IMPORTING | ||
| E_NEWCONTACT | = lv_e_newcontact | |
| E_RETURNCODE | = lv_e_returncode | |
| TABLES | ||
| T_INVOICE_IDS | = lt_t_invoice_ids | |
| EXCEPTIONS | ||
| INCOMPLETE_CUSTOMIZING = 1 | ||
| . " FKK_EBPP_ADD_CONTACT | ||
ABAP code using 7.40 inline data declarations to call FM FKK_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 GPART FROM FKKOP INTO @DATA(ld_i_gpart). | ||||
| "SELECT single BPCONTACT FROM BCONT INTO @DATA(ld_e_newcontact). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_returncode). | ||||
| "SELECT single ACTIVITY FROM BCONTA INTO @DATA(ld_i_activity). | ||||
Search for further information about these or an SAP related objects