SAP FUTURE_PRICES_SET Function Module for









FUTURE_PRICES_SET is a standard future prices set 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 future prices set FM, simply by entering the name FUTURE_PRICES_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function FUTURE_PRICES_SET 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 'FUTURE_PRICES_SET'"
EXPORTING
P_DAT = "
LFMON = "
LFGJA = "
VMMON = "
VMGJA = "
* S_CCS_DATA_AVAILABLE = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

TABLES
T_KALNR = "
T_PR_CONVERT = "
T_PRICES = "
.



IMPORTING Parameters details for FUTURE_PRICES_SET

P_DAT -

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

LFMON -

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

LFGJA -

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

VMMON -

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

VMGJA -

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

S_CCS_DATA_AVAILABLE - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

TABLES Parameters details for FUTURE_PRICES_SET

T_KALNR -

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

T_PR_CONVERT -

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

T_PRICES -

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

Copy and paste ABAP code example for FUTURE_PRICES_SET 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_p_dat  TYPE CKMLPR-ZPRSDAT, "   
lt_t_kalnr  TYPE STANDARD TABLE OF CKMV0_MATOBJ_TBL, "   
lv_lfmon  TYPE MARV-LFMON, "   
lt_t_pr_convert  TYPE STANDARD TABLE OF CKI_PRC_ML, "   
lv_lfgja  TYPE MARV-LFGJA, "   
lt_t_prices  TYPE STANDARD TABLE OF CKI_CKMPRP_SINGLE, "   
lv_vmmon  TYPE MARV-VMMON, "   
lv_vmgja  TYPE MARV-VMGJA, "   
lv_s_ccs_data_available  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FUTURE_PRICES_SET'  "
    EXPORTING
         P_DAT = lv_p_dat
         LFMON = lv_lfmon
         LFGJA = lv_lfgja
         VMMON = lv_vmmon
         VMGJA = lv_vmgja
         S_CCS_DATA_AVAILABLE = lv_s_ccs_data_available
    TABLES
         T_KALNR = lt_t_kalnr
         T_PR_CONVERT = lt_t_pr_convert
         T_PRICES = lt_t_prices
. " FUTURE_PRICES_SET




ABAP code using 7.40 inline data declarations to call FM FUTURE_PRICES_SET

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 ZPRSDAT FROM CKMLPR INTO @DATA(ld_p_dat).
 
 
"SELECT single LFMON FROM MARV INTO @DATA(ld_lfmon).
 
 
"SELECT single LFGJA FROM MARV INTO @DATA(ld_lfgja).
 
 
"SELECT single VMMON FROM MARV INTO @DATA(ld_vmmon).
 
"SELECT single VMGJA FROM MARV INTO @DATA(ld_vmgja).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_s_ccs_data_available).
 


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!