SAP RKE_PRICING_INTERFACE_PLAN Function Module for









RKE_PRICING_INTERFACE_PLAN is a standard rke pricing interface plan 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 rke pricing interface plan FM, simply by entering the name RKE_PRICING_INTERFACE_PLAN into the relevant SAP transaction such as SE37 or SE38.

Function Group: KEAB
Program Name: SAPLKEAB
Main Program: SAPLKEAB
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RKE_PRICING_INTERFACE_PLAN 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 'RKE_PRICING_INTERFACE_PLAN'"
EXPORTING
* DIALOG = ' ' "Dialog function on/off
* I_TRACE_MODE_BEAN = ' ' "
* I_TRACE_MODE_COPC = ' ' "
* I_CLEAR_ALL_BUFFERS = ' ' "
* KURST = 'M' "
* BWFKT = '03' "
* I_BSTRA = "Valuation strategy (CO-PA)
RKE_EINZELPOSTEN = "Line item to be valuated
STICHTAG = "Date for valuation
TABNAME = "Table name (e.g. CE10012)
VERSI = "
* I_CONDITION_ANALYSIS = ' ' "

IMPORTING
BEWERTETER_EP = "Valuated line item
E_TRACE_HANDLE_COPC = "
E_TRACE_HANDLE_BEAN = "

TABLES
DBTAB = "Fieldtab
* WERTKOMP = "

EXCEPTIONS
VALUATION_ERROR = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLKEAB_001 User Exit for Actual Data Valuation
EXIT_SAPLKEAB_002 User Exit for Planning Data Valuation
EXIT_SAPLKEAB_003 Valuation Using Conditions: Access to the Structures KOMK / KOMP
EXIT_SAPLKEAB_004 CO-PA Valuation: Flexible Assignment Costing Key

IMPORTING Parameters details for RKE_PRICING_INTERFACE_PLAN

DIALOG - Dialog function on/off

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

I_TRACE_MODE_BEAN -

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

I_TRACE_MODE_COPC -

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

I_CLEAR_ALL_BUFFERS -

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

KURST -

Data type: TKEVS-KURST
Default: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)

BWFKT -

Data type: TKEVA01-BWFKT
Default: '03'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BSTRA - Valuation strategy (CO-PA)

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

RKE_EINZELPOSTEN - Line item to be valuated

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

STICHTAG - Date for valuation

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

TABNAME - Table name (e.g. CE10012)

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

VERSI -

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

I_CONDITION_ANALYSIS -

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

EXPORTING Parameters details for RKE_PRICING_INTERFACE_PLAN

BEWERTETER_EP - Valuated line item

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

E_TRACE_HANDLE_COPC -

Data type: KEDR_TRACE_HANDLE
Optional: No
Call by Reference: Yes

E_TRACE_HANDLE_BEAN -

Data type: KEDR_TRACE_HANDLE
Optional: No
Call by Reference: Yes

TABLES Parameters details for RKE_PRICING_INTERFACE_PLAN

DBTAB - Fieldtab

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

WERTKOMP -

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

EXCEPTIONS details

VALUATION_ERROR -

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

Copy and paste ABAP code example for RKE_PRICING_INTERFACE_PLAN 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_dbtab  TYPE STANDARD TABLE OF STRING, "   
lv_dialog  TYPE STRING, "   SPACE
lv_bewerteter_ep  TYPE STRING, "   
lv_valuation_error  TYPE STRING, "   
lv_i_trace_mode_bean  TYPE KEDR_TRACE_MODE, "   SPACE
lv_i_trace_mode_copc  TYPE KEDR_TRACE_MODE, "   SPACE
lv_i_clear_all_buffers  TYPE KEDR_FLAG, "   SPACE
lv_kurst  TYPE TKEVS-KURST, "   'M'
lt_wertkomp  TYPE STANDARD TABLE OF RKEPR, "   
lv_e_trace_handle_copc  TYPE KEDR_TRACE_HANDLE, "   
lv_bwfkt  TYPE TKEVA01-BWFKT, "   '03'
lv_e_trace_handle_bean  TYPE KEDR_TRACE_HANDLE, "   
lv_i_bstra  TYPE TKEVAS-BSTRA, "   
lv_rke_einzelposten  TYPE TKEVAS, "   
lv_stichtag  TYPE SY-DATUM, "   
lv_tabname  TYPE DD02V-TABNAME, "   
lv_versi  TYPE CEST1-VERSI, "   
lv_i_condition_analysis  TYPE CEST1. "   SPACE

  CALL FUNCTION 'RKE_PRICING_INTERFACE_PLAN'  "
    EXPORTING
         DIALOG = lv_dialog
         I_TRACE_MODE_BEAN = lv_i_trace_mode_bean
         I_TRACE_MODE_COPC = lv_i_trace_mode_copc
         I_CLEAR_ALL_BUFFERS = lv_i_clear_all_buffers
         KURST = lv_kurst
         BWFKT = lv_bwfkt
         I_BSTRA = lv_i_bstra
         RKE_EINZELPOSTEN = lv_rke_einzelposten
         STICHTAG = lv_stichtag
         TABNAME = lv_tabname
         VERSI = lv_versi
         I_CONDITION_ANALYSIS = lv_i_condition_analysis
    IMPORTING
         BEWERTETER_EP = lv_bewerteter_ep
         E_TRACE_HANDLE_COPC = lv_e_trace_handle_copc
         E_TRACE_HANDLE_BEAN = lv_e_trace_handle_bean
    TABLES
         DBTAB = lt_dbtab
         WERTKOMP = lt_wertkomp
    EXCEPTIONS
        VALUATION_ERROR = 1
. " RKE_PRICING_INTERFACE_PLAN




ABAP code using 7.40 inline data declarations to call FM RKE_PRICING_INTERFACE_PLAN

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.

 
DATA(ld_dialog) = ' '.
 
 
 
DATA(ld_i_trace_mode_bean) = ' '.
 
DATA(ld_i_trace_mode_copc) = ' '.
 
DATA(ld_i_clear_all_buffers) = ' '.
 
"SELECT single KURST FROM TKEVS INTO @DATA(ld_kurst).
DATA(ld_kurst) = 'M'.
 
 
 
"SELECT single BWFKT FROM TKEVA01 INTO @DATA(ld_bwfkt).
DATA(ld_bwfkt) = '03'.
 
 
"SELECT single BSTRA FROM TKEVAS INTO @DATA(ld_i_bstra).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_stichtag).
 
"SELECT single TABNAME FROM DD02V INTO @DATA(ld_tabname).
 
"SELECT single VERSI FROM CEST1 INTO @DATA(ld_versi).
 
DATA(ld_i_condition_analysis) = ' '.
 


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!