SAP SALES_CONDITIONS_TABLE_DISPLAY Function Module for NOTRANSL: Listanzeige von Verkaufs-Konditionen

Search SAP Function Modules

SALES_CONDITIONS_TABLE_DISPLAY is a standard sales conditions table display 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: Listanzeige von Verkaufs-Konditionen 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 sales conditions table display FM, simply by entering the name SALES_CONDITIONS_TABLE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

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

Function SALES_CONDITIONS_TABLE_DISPLAY 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 'SALES_CONDITIONS_TABLE_DISPLAY'"NOTRANSL: Listanzeige von Verkaufs-Konditionen
  EXPORTING
   PI_I_SCD =  "
*  IV_SWITCH_TO_ALV =  "

TABLES
*  SO_WERKS =  "Range table for the plant
*  SO_PLTYP =  "Range table for the price list
*  SO_MATNR =  "Range table for the material number
*  PI_T_ARFI =  "

EXCEPTIONS
   NO_MATERIALS_SELECTED = 1    NO_PLANTS_SELECTED = 2    NO_CONDITION_TYPES_FOUND = 3    NO_CONDITIONS_FOUND = 4    TOO_MANY_MATERIALS = 5 

.

IMPORTING Parameters details for SALES_CONDITIONS_TABLE_DISPLAY

PI_I_SCD -

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

IV_SWITCH_TO_ALV -

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

TABLES Parameters details for SALES_CONDITIONS_TABLE_DISPLAY

SO_WERKS - Range table for the plant

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

SO_PLTYP - Range table for the price list

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

SO_MATNR - Range table for the material number

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

PI_T_ARFI -

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

EXCEPTIONS details

NO_MATERIALS_SELECTED - No materials could be selected

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

NO_PLANTS_SELECTED - No plants able to be selected

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

NO_CONDITION_TYPES_FOUND -

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

NO_CONDITIONS_FOUND -

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

TOO_MANY_MATERIALS -

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

Copy and paste ABAP code example for SALES_CONDITIONS_TABLE_DISPLAY 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.

ABAP code using 7.40 inline data declarations to call FM SALES_CONDITIONS_TABLE_DISPLAY

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