SAP SALES_AREA_FIND Function Module for NOTRANSL: Vertriebsbereichsfindung für Umlagerungsbestellung









SALES_AREA_FIND is a standard sales area find 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: Vertriebsbereichsfindung für Umlagerungsbestellung 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 area find FM, simply by entering the name SALES_AREA_FIND into the relevant SAP transaction such as SE37 or SE38.

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



Function SALES_AREA_FIND 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_AREA_FIND'"NOTRANSL: Vertriebsbereichsfindung für Umlagerungsbestellung
EXPORTING
IVKORG = "
IVTWEG = "
ISPART = "
LFWERK = "Supplying Plant
KUNNR = "
* ONLY_ONE = ' ' "

IMPORTING
EVKORG = "
EVTWEG = "
ESPART = "
TAB_COUNT = "

TABLES
* ETVTA = "

EXCEPTIONS
VERTRBEREICH_NICHT_BESTIMMBAR = 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_SAPLV02V_001 User Exit for Sales Area Determination
EXIT_SAPLV02V_002 User Exit Storage Location Determination
EXIT_SAPLV02V_003 User Exit for Door and Staging Area Determination
EXIT_SAPLV02V_004 User Exit for Staging Area Determination - Delivery Item

IMPORTING Parameters details for SALES_AREA_FIND

IVKORG -

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

IVTWEG -

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

ISPART -

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

LFWERK - Supplying Plant

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

KUNNR -

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

ONLY_ONE -

Data type: TVAK-TRTRM
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SALES_AREA_FIND

EVKORG -

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

EVTWEG -

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

ESPART -

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

TAB_COUNT -

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

TABLES Parameters details for SALES_AREA_FIND

ETVTA -

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

EXCEPTIONS details

VERTRBEREICH_NICHT_BESTIMMBAR -

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

Copy and paste ABAP code example for SALES_AREA_FIND 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_etvta  TYPE STANDARD TABLE OF TVTA, "   
lv_evkorg  TYPE TVTA-VKORG, "   
lv_ivkorg  TYPE TVTA-VKORG, "   
lv_vertrbereich_nicht_bestimmbar  TYPE TVTA, "   
lv_evtweg  TYPE TVTA-VTWEG, "   
lv_ivtweg  TYPE TVTA-VTWEG, "   
lv_espart  TYPE TVTA-SPART, "   
lv_ispart  TYPE TVTA-SPART, "   
lv_lfwerk  TYPE T001W-WERKS, "   
lv_tab_count  TYPE SY-TABIX, "   
lv_kunnr  TYPE KNVV-KUNNR, "   
lv_only_one  TYPE TVAK-TRTRM. "   ' '

  CALL FUNCTION 'SALES_AREA_FIND'  "NOTRANSL: Vertriebsbereichsfindung für Umlagerungsbestellung
    EXPORTING
         IVKORG = lv_ivkorg
         IVTWEG = lv_ivtweg
         ISPART = lv_ispart
         LFWERK = lv_lfwerk
         KUNNR = lv_kunnr
         ONLY_ONE = lv_only_one
    IMPORTING
         EVKORG = lv_evkorg
         EVTWEG = lv_evtweg
         ESPART = lv_espart
         TAB_COUNT = lv_tab_count
    TABLES
         ETVTA = lt_etvta
    EXCEPTIONS
        VERTRBEREICH_NICHT_BESTIMMBAR = 1
. " SALES_AREA_FIND




ABAP code using 7.40 inline data declarations to call FM SALES_AREA_FIND

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 VKORG FROM TVTA INTO @DATA(ld_evkorg).
 
"SELECT single VKORG FROM TVTA INTO @DATA(ld_ivkorg).
 
 
"SELECT single VTWEG FROM TVTA INTO @DATA(ld_evtweg).
 
"SELECT single VTWEG FROM TVTA INTO @DATA(ld_ivtweg).
 
"SELECT single SPART FROM TVTA INTO @DATA(ld_espart).
 
"SELECT single SPART FROM TVTA INTO @DATA(ld_ispart).
 
"SELECT single WERKS FROM T001W INTO @DATA(ld_lfwerk).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_tab_count).
 
"SELECT single KUNNR FROM KNVV INTO @DATA(ld_kunnr).
 
"SELECT single TRTRM FROM TVAK INTO @DATA(ld_only_one).
DATA(ld_only_one) = ' '.
 


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!