SAP LOCATION_SELECT_PLANT Function Module for NOTRANSL: Selektion des Werks (T001W)

Search SAP Function Modules

LOCATION_SELECT_PLANT is a standard location select plant 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: Selektion des Werks (T001W) 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 location select plant FM, simply by entering the name LOCATION_SELECT_PLANT into the relevant SAP transaction such as SE37 or SE38.

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

Function LOCATION_SELECT_PLANT 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 'LOCATION_SELECT_PLANT'"NOTRANSL: Selektion des Werks (T001W)
  EXPORTING
*  I_WERKS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_KUNNR = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_LIFNR = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  BYPASSING_BUFFER = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION

 IMPORTING
   O_T001W =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
   NO_VALID_PLANT = 1    PLANT_NOT_FOUND = 2    MORE_THAN_ONE_ENTRY_FOUND = 3 

.

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_SAPLWR04_001 User Exit for Determining Supplying Site

IMPORTING Parameters details for LOCATION_SELECT_PLANT

I_WERKS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_KUNNR - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_LIFNR - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

BYPASSING_BUFFER - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXPORTING Parameters details for LOCATION_SELECT_PLANT

O_T001W - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

NO_VALID_PLANT - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

PLANT_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

MORE_THAN_ONE_ENTRY_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

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

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