SAP OIJU_CHECK_LOCATION_RD Function Module for OIL-TSW: Check if a location is a rundownable object with 1 plant attached

Search SAP Function Modules

OIJU_CHECK_LOCATION_RD is a standard oiju check location rd 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-TSW: Check if a location is a rundownable object with 1 plant attached 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 oiju check location rd FM, simply by entering the name OIJU_CHECK_LOCATION_RD into the relevant SAP transaction such as SE37 or SE38.

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

Function OIJU_CHECK_LOCATION_RD 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 'OIJU_CHECK_LOCATION_RD'"OIL-TSW: Check if a location is a rundownable object with 1 plant attached
  EXPORTING
   I_LOCID =  "
*  I_GET_ALL_LGORT =  "Single-character flag to get all storage locs for  a  singlelocation

 IMPORTING
   T_LOCDATA =  "
   E_WERK =  "
   E_LGORT =  "Storage location
   ES_BUSLOC =  "SSR PC: Internal table for location master

TABLES
*  T_OIJRRA_WERK_LGORT_TAB =  "Contains all plan/sloc combinations for a location

EXCEPTIONS
   INPUT_NOT_VALID = 1    LOCATION_NOT_FOUND = 2    NO_PLANT = 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_SAPLOIJU_001 OIL-TSW: Customer exit for editing rundown plant book inventory
EXIT_SAPLOIJU_002 OIL-TSW: Customer exit for editing rundown plant SOP data
EXIT_SAPLOIJU_003 OIL-TSW: Customer exit for editing rundown plant statistical movement data

IMPORTING Parameters details for OIJU_CHECK_LOCATION_RD

I_LOCID -

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

I_GET_ALL_LGORT - Single-character flag to get all storage locs for a singlelocation

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

EXPORTING Parameters details for OIJU_CHECK_LOCATION_RD

T_LOCDATA -

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

E_WERK -

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

E_LGORT - Storage location

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

ES_BUSLOC - SSR PC: Internal table for location master

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

TABLES Parameters details for OIJU_CHECK_LOCATION_RD

T_OIJRRA_WERK_LGORT_TAB - Contains all plan/sloc combinations for a location

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

EXCEPTIONS details

INPUT_NOT_VALID -

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

LOCATION_NOT_FOUND -

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

NO_PLANT -

Data type:
Optional: No
Call by Reference: Yes

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

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