SAP KECM_RFC_PARTNERS_GET Function Module for









KECM_RFC_PARTNERS_GET is a standard kecm rfc partners get 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 kecm rfc partners get FM, simply by entering the name KECM_RFC_PARTNERS_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function KECM_RFC_PARTNERS_GET 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 'KECM_RFC_PARTNERS_GET'"
EXPORTING
* I_LANGU = SY-LANGU "

TABLES
* E_TAB_VALUES = "
* E_TAB_VALUES_SLS = "
.



IMPORTING Parameters details for KECM_RFC_PARTNERS_GET

I_LANGU -

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

TABLES Parameters details for KECM_RFC_PARTNERS_GET

E_TAB_VALUES -

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

E_TAB_VALUES_SLS -

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

Copy and paste ABAP code example for KECM_RFC_PARTNERS_GET 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_langu  TYPE SY-LANGU, "   SY-LANGU
lt_e_tab_values  TYPE STANDARD TABLE OF RKEPARTNES, "   
lt_e_tab_values_sls  TYPE STANDARD TABLE OF RKEPARTNVS. "   

  CALL FUNCTION 'KECM_RFC_PARTNERS_GET'  "
    EXPORTING
         I_LANGU = lv_i_langu
    TABLES
         E_TAB_VALUES = lt_e_tab_values
         E_TAB_VALUES_SLS = lt_e_tab_values_sls
. " KECM_RFC_PARTNERS_GET




ABAP code using 7.40 inline data declarations to call FM KECM_RFC_PARTNERS_GET

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 LANGU FROM SY INTO @DATA(ld_i_langu).
DATA(ld_i_langu) = SY-LANGU.
 
 
 


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!