SAP OII_GET_AND_VALIDATE_PLANT Function Module for OIL-BDRP: Check and validate plant
OII_GET_AND_VALIDATE_PLANT is a standard oii get and validate 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 OIL-BDRP: Check and validate plant 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 oii get and validate plant FM, simply by entering the name OII_GET_AND_VALIDATE_PLANT into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIIB
Program Name: SAPLOIIB
Main Program: SAPLOIIB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OII_GET_AND_VALIDATE_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 'OII_GET_AND_VALIDATE_PLANT'"OIL-BDRP: Check and validate plant.
EXPORTING
I_WERKS = "Plant
IMPORTING
E_NAME1 = "Plant name
E_NAME2 = "Plant name 2
EXCEPTIONS
PLANT_NOT_FOUND = 1
IMPORTING Parameters details for OII_GET_AND_VALIDATE_PLANT
I_WERKS - Plant
Data type: T001W-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OII_GET_AND_VALIDATE_PLANT
E_NAME1 - Plant name
Data type: T001W-NAME1Optional: No
Call by Reference: No ( called with pass by value option)
E_NAME2 - Plant name 2
Data type: T001W-NAME2Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PLANT_NOT_FOUND - Requested plant does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OII_GET_AND_VALIDATE_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.| DATA: | ||||
| lv_e_name1 | TYPE T001W-NAME1, " | |||
| lv_i_werks | TYPE T001W-WERKS, " | |||
| lv_plant_not_found | TYPE T001W, " | |||
| lv_e_name2 | TYPE T001W-NAME2. " |
|   CALL FUNCTION 'OII_GET_AND_VALIDATE_PLANT' "OIL-BDRP: Check and validate plant |
| EXPORTING | ||
| I_WERKS | = lv_i_werks | |
| IMPORTING | ||
| E_NAME1 | = lv_e_name1 | |
| E_NAME2 | = lv_e_name2 | |
| EXCEPTIONS | ||
| PLANT_NOT_FOUND = 1 | ||
| . " OII_GET_AND_VALIDATE_PLANT | ||
ABAP code using 7.40 inline data declarations to call FM OII_GET_AND_VALIDATE_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.| "SELECT single NAME1 FROM T001W INTO @DATA(ld_e_name1). | ||||
| "SELECT single WERKS FROM T001W INTO @DATA(ld_i_werks). | ||||
| "SELECT single NAME2 FROM T001W INTO @DATA(ld_e_name2). | ||||
Search for further information about these or an SAP related objects