SAP VERSANDSTELLE_ERMITTELN Function Module for NOTRANSL: Ermitteln Versandstelle









VERSANDSTELLE_ERMITTELN is a standard versandstelle ermitteln 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: Ermitteln Versandstelle 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 versandstelle ermitteln FM, simply by entering the name VERSANDSTELLE_ERMITTELN into the relevant SAP transaction such as SE37 or SE38.

Function Group: V45E
Program Name: SAPLV45E
Main Program: SAPLV45E
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function VERSANDSTELLE_ERMITTELN 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 'VERSANDSTELLE_ERMITTELN'"NOTRANSL: Ermitteln Versandstelle
EXPORTING
LADGR = "Loading group
* LGORT = "
VSBED = "
VSTEL_I = "
WERKS = "Plant
* IF_LFART = ' ' "Delivery Type
* IF_SPOFI = ' ' "Rules for Shipping Point Determination

IMPORTING
E_TVST = "
VSTEL = "Shipping point

EXCEPTIONS
FEHLER_BEI_LESEN_TVST = 1 FEHLER_BEI_LESEN_TVSTZ = 2 VSTEL_NICHT_ERLAUBT = 3
.



IMPORTING Parameters details for VERSANDSTELLE_ERMITTELN

LADGR - Loading group

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

LGORT -

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

VSBED -

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

VSTEL_I -

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

WERKS - Plant

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

IF_LFART - Delivery Type

Data type: TVLK-LFART
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IF_SPOFI - Rules for Shipping Point Determination

Data type: TVLK-SPOFI
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for VERSANDSTELLE_ERMITTELN

E_TVST -

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

VSTEL - Shipping point

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

EXCEPTIONS details

FEHLER_BEI_LESEN_TVST - Error when reading TVST.

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

FEHLER_BEI_LESEN_TVSTZ - Error when reading TVSTZ.

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

VSTEL_NICHT_ERLAUBT - Shipping point not allowed in this

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

Copy and paste ABAP code example for VERSANDSTELLE_ERMITTELN 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_ladgr  TYPE TVSTZ-LADGR, "   
lv_e_tvst  TYPE TVST, "   
lv_fehler_bei_lesen_tvst  TYPE TVST, "   
lv_lgort  TYPE TVSTZ-LGORT, "   
lv_vstel  TYPE TVSTZ-VSTEL, "   
lv_fehler_bei_lesen_tvstz  TYPE TVSTZ, "   
lv_vsbed  TYPE TVSTZ-VSBED, "   
lv_vstel_nicht_erlaubt  TYPE TVSTZ, "   
lv_vstel_i  TYPE TVSTZ-VSTEL, "   
lv_werks  TYPE TVSTZ-WERKS, "   
lv_if_lfart  TYPE TVLK-LFART, "   SPACE
lv_if_spofi  TYPE TVLK-SPOFI. "   SPACE

  CALL FUNCTION 'VERSANDSTELLE_ERMITTELN'  "NOTRANSL: Ermitteln Versandstelle
    EXPORTING
         LADGR = lv_ladgr
         LGORT = lv_lgort
         VSBED = lv_vsbed
         VSTEL_I = lv_vstel_i
         WERKS = lv_werks
         IF_LFART = lv_if_lfart
         IF_SPOFI = lv_if_spofi
    IMPORTING
         E_TVST = lv_e_tvst
         VSTEL = lv_vstel
    EXCEPTIONS
        FEHLER_BEI_LESEN_TVST = 1
        FEHLER_BEI_LESEN_TVSTZ = 2
        VSTEL_NICHT_ERLAUBT = 3
. " VERSANDSTELLE_ERMITTELN




ABAP code using 7.40 inline data declarations to call FM VERSANDSTELLE_ERMITTELN

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 LADGR FROM TVSTZ INTO @DATA(ld_ladgr).
 
 
 
"SELECT single LGORT FROM TVSTZ INTO @DATA(ld_lgort).
 
"SELECT single VSTEL FROM TVSTZ INTO @DATA(ld_vstel).
 
 
"SELECT single VSBED FROM TVSTZ INTO @DATA(ld_vsbed).
 
 
"SELECT single VSTEL FROM TVSTZ INTO @DATA(ld_vstel_i).
 
"SELECT single WERKS FROM TVSTZ INTO @DATA(ld_werks).
 
"SELECT single LFART FROM TVLK INTO @DATA(ld_if_lfart).
DATA(ld_if_lfart) = ' '.
 
"SELECT single SPOFI FROM TVLK INTO @DATA(ld_if_spofi).
DATA(ld_if_spofi) = ' '.
 


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!