SAP PROMOTION_SET_ACTIVATE_DATES Function Module for NOTRANSL: Angabe der Datümer zur Aktivierung von Aktionspreisen









PROMOTION_SET_ACTIVATE_DATES is a standard promotion set activate dates SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Angabe der Datümer zur Aktivierung von Aktionspreisen processing and below is the pattern details for this FM, 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 promotion set activate dates FM, simply by entering the name PROMOTION_SET_ACTIVATE_DATES into the relevant SAP transaction such as SE37 or SE38.

Function Group: WAK1
Program Name: SAPLWAK1
Main Program: SAPLWAK1
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PROMOTION_SET_ACTIVATE_DATES 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 'PROMOTION_SET_ACTIVATE_DATES'"NOTRANSL: Angabe der Datümer zur Aktivierung von Aktionspreisen
EXPORTING
P_I_XWAKHD = "
* P_I_FLAG_NO_KALK = "

IMPORTING
P_E_EKDAB = "
P_E_EKDBI = "
P_E_ALIVO = "
P_E_ALIBI = "
P_E_VKDAB = "
P_E_VKDBI = "
P_E_FCODE = "Function Code

CHANGING
* P_E_KZ_WALE_PRICES = "Indicator - Include plant-specific prices

TABLES
PI_T_XWAGUD = "Table of Plant Groups
PE_T_XWAGUD = "
.



IMPORTING Parameters details for PROMOTION_SET_ACTIVATE_DATES

P_I_XWAKHD -

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

P_I_FLAG_NO_KALK -

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

EXPORTING Parameters details for PROMOTION_SET_ACTIVATE_DATES

P_E_EKDAB -

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

P_E_EKDBI -

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

P_E_ALIVO -

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

P_E_ALIBI -

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

P_E_VKDAB -

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

P_E_VKDBI -

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

P_E_FCODE - Function Code

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

CHANGING Parameters details for PROMOTION_SET_ACTIVATE_DATES

P_E_KZ_WALE_PRICES - Indicator - Include plant-specific prices

Data type: RWAKA-KZ_WALE_PRICES
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for PROMOTION_SET_ACTIVATE_DATES

PI_T_XWAGUD - Table of Plant Groups

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

PE_T_XWAGUD -

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

Copy and paste ABAP code example for PROMOTION_SET_ACTIVATE_DATES 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_e_ekdab  TYPE WAKHD-EKDAB, "   
lv_p_i_xwakhd  TYPE WAKHD, "   
lt_pi_t_xwagud  TYPE STANDARD TABLE OF WAGUD, "   
lv_p_e_kz_wale_prices  TYPE RWAKA-KZ_WALE_PRICES, "   
lv_p_e_ekdbi  TYPE WAKHD-EKDBI, "   
lt_pe_t_xwagud  TYPE STANDARD TABLE OF WAGUD, "   
lv_p_i_flag_no_kalk  TYPE XFELD, "   
lv_p_e_alivo  TYPE WAKHD-ALIVO, "   
lv_p_e_alibi  TYPE WAKHD-ALIBI, "   
lv_p_e_vkdab  TYPE WAKHD-VKDAB, "   
lv_p_e_vkdbi  TYPE WAKHD-VKDBI, "   
lv_p_e_fcode  TYPE SY-UCOMM. "   

  CALL FUNCTION 'PROMOTION_SET_ACTIVATE_DATES'  "NOTRANSL: Angabe der Datümer zur Aktivierung von Aktionspreisen
    EXPORTING
         P_I_XWAKHD = lv_p_i_xwakhd
         P_I_FLAG_NO_KALK = lv_p_i_flag_no_kalk
    IMPORTING
         P_E_EKDAB = lv_p_e_ekdab
         P_E_EKDBI = lv_p_e_ekdbi
         P_E_ALIVO = lv_p_e_alivo
         P_E_ALIBI = lv_p_e_alibi
         P_E_VKDAB = lv_p_e_vkdab
         P_E_VKDBI = lv_p_e_vkdbi
         P_E_FCODE = lv_p_e_fcode
    CHANGING
         P_E_KZ_WALE_PRICES = lv_p_e_kz_wale_prices
    TABLES
         PI_T_XWAGUD = lt_pi_t_xwagud
         PE_T_XWAGUD = lt_pe_t_xwagud
. " PROMOTION_SET_ACTIVATE_DATES




ABAP code using 7.40 inline data declarations to call FM PROMOTION_SET_ACTIVATE_DATES

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 EKDAB FROM WAKHD INTO @DATA(ld_p_e_ekdab).
 
 
 
"SELECT single KZ_WALE_PRICES FROM RWAKA INTO @DATA(ld_p_e_kz_wale_prices).
 
"SELECT single EKDBI FROM WAKHD INTO @DATA(ld_p_e_ekdbi).
 
 
 
"SELECT single ALIVO FROM WAKHD INTO @DATA(ld_p_e_alivo).
 
"SELECT single ALIBI FROM WAKHD INTO @DATA(ld_p_e_alibi).
 
"SELECT single VKDAB FROM WAKHD INTO @DATA(ld_p_e_vkdab).
 
"SELECT single VKDBI FROM WAKHD INTO @DATA(ld_p_e_vkdbi).
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_p_e_fcode).
 


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!