SAP POPUP_TO_CHANGE_LIST_FIELD Function Module for NOTRANSL: Massenänderung Listfeld









POPUP_TO_CHANGE_LIST_FIELD is a standard popup to change list field 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: Massenänderung Listfeld 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 popup to change list field FM, simply by entering the name POPUP_TO_CHANGE_LIST_FIELD into the relevant SAP transaction such as SE37 or SE38.

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



Function POPUP_TO_CHANGE_LIST_FIELD 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 'POPUP_TO_CHANGE_LIST_FIELD'"NOTRANSL: Massenänderung Listfeld
  EXPORTING
   PI_ECKKZ_ALLOWED =  "Checkbox
*  PI_PRICE_POINT_DET =  "Price Point Group Determination
*  PI_VKORG =  "Sales Organization
*  PI_VTWEG =  "Distribution Channel
*  PI_MATKL =  "Material Group
*  PI_PLTYP =  "Price List Type
*  PI_WAERK =  "Price point currency
*  PI_EPTYP =  "Sales Pricing: List Field for Determining Sales Price

 IMPORTING
   PE_EPRGR =  "Price Point Group

CHANGING
   PX_KBETR =  "Rate (Condition Rate or Percentage)
   PX_KWAER =  "Controlling Area Currency
   PX_KIND =  "Type of Sales Price Change
   PX_BASIS =  "Price Change Basis
*  PX_ECKKZ =  "SP calc.: price point rounding for suggested final price

EXCEPTIONS
   CANCELED_BY_USER = 1    INVALID_DATA = 2
.



IMPORTING Parameters details for POPUP_TO_CHANGE_LIST_FIELD

PI_ECKKZ_ALLOWED - Checkbox

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

PI_PRICE_POINT_DET - Price Point Group Determination

Data type: WCOL_POINT_PRICE
Optional: Yes
Call by Reference: Yes

PI_VKORG - Sales Organization

Data type: VKORG
Optional: Yes
Call by Reference: Yes

PI_VTWEG - Distribution Channel

Data type: VTWEG
Optional: Yes
Call by Reference: Yes

PI_MATKL - Material Group

Data type: MATKL
Optional: Yes
Call by Reference: Yes

PI_PLTYP - Price List Type

Data type: PLTYP
Optional: Yes
Call by Reference: Yes

PI_WAERK - Price point currency

Data type: WAERS_EPG
Optional: Yes
Call by Reference: Yes

PI_EPTYP - Sales Pricing: List Field for Determining Sales Price

Data type: EPTYP
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for POPUP_TO_CHANGE_LIST_FIELD

PE_EPRGR - Price Point Group

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

CHANGING Parameters details for POPUP_TO_CHANGE_LIST_FIELD

PX_KBETR - Rate (Condition Rate or Percentage)

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

PX_KWAER - Controlling Area Currency

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

PX_KIND - Type of Sales Price Change

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

PX_BASIS - Price Change Basis

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

PX_ECKKZ - SP calc.: price point rounding for suggested final price

Data type: ECKKZ
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

CANCELED_BY_USER - User Termination

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATA - Invalid Interface Data

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for POPUP_TO_CHANGE_LIST_FIELD 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_pe_eprgr  TYPE EPRGR, "   
lv_px_kbetr  TYPE KBETR, "   
lv_canceled_by_user  TYPE KBETR, "   
lv_pi_eckkz_allowed  TYPE XFELD, "   
lv_px_kwaer  TYPE KWAER, "   
lv_invalid_data  TYPE KWAER, "   
lv_pi_price_point_det  TYPE WCOL_POINT_PRICE, "   
lv_px_kind  TYPE WCOL_KIND, "   
lv_pi_vkorg  TYPE VKORG, "   
lv_pi_vtweg  TYPE VTWEG, "   
lv_px_basis  TYPE WCOL_BASIS, "   
lv_pi_matkl  TYPE MATKL, "   
lv_px_eckkz  TYPE ECKKZ, "   
lv_pi_pltyp  TYPE PLTYP, "   
lv_pi_waerk  TYPE WAERS_EPG, "   
lv_pi_eptyp  TYPE EPTYP. "   

  CALL FUNCTION 'POPUP_TO_CHANGE_LIST_FIELD'  "NOTRANSL: Massenänderung Listfeld
    EXPORTING
         PI_ECKKZ_ALLOWED = lv_pi_eckkz_allowed
         PI_PRICE_POINT_DET = lv_pi_price_point_det
         PI_VKORG = lv_pi_vkorg
         PI_VTWEG = lv_pi_vtweg
         PI_MATKL = lv_pi_matkl
         PI_PLTYP = lv_pi_pltyp
         PI_WAERK = lv_pi_waerk
         PI_EPTYP = lv_pi_eptyp
    IMPORTING
         PE_EPRGR = lv_pe_eprgr
    CHANGING
         PX_KBETR = lv_px_kbetr
         PX_KWAER = lv_px_kwaer
         PX_KIND = lv_px_kind
         PX_BASIS = lv_px_basis
         PX_ECKKZ = lv_px_eckkz
    EXCEPTIONS
        CANCELED_BY_USER = 1
        INVALID_DATA = 2
. " POPUP_TO_CHANGE_LIST_FIELD




ABAP code using 7.40 inline data declarations to call FM POPUP_TO_CHANGE_LIST_FIELD

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!