SLS_IOA_CHECK_IO_LOCATION SAP Function module - Check the assignment of one Info Object to a location

SLS_IOA_CHECK_IO_LOCATION is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SLS_IOA_CHECK_IO_LOCATION into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SLS3
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SLS_IOA_CHECK_IO_LOCATION - SLS IOA CHECK IO LOCATION

CALL FUNCTION 'SLS_IOA_CHECK_IO_LOCATION' "Check the assignment of one Info Object to a location
  EXPORTING
    p_plvar =                   " sls_loctty-plvar  Plan version
    p_locid =                   " sls_loctty-locid  Location ID from HR TEM
    p_class =                   " sls_loctty-class  Info object class name (KEN)
    p_guid =                    " sls_loctty-guid  LOIO - Info object unique key (KEN)
    p_var1 =                    " sls_loctty-var1  Info object context variant 1 (KEN)
    p_var2 =                    " sls_loctty-var2  Info object context variant 2 (KEN)
    p_var3 =                    " sls_loctty-var3  Info object context variant 3 (KEN)
    p_var4 =                    " sls_loctty-var4  Info object context variant 4 (KEN)
    p_date =                    " sls_loctty-begda  Start date
  IMPORTING
    p_exists =                  " ls_boolean
  TABLES
    p_loctty =                  " sls_loctty    PAW - Location - Test Type
    .  "  SLS_IOA_CHECK_IO_LOCATION

ABAP code example for Function Module SLS_IOA_CHECK_IO_LOCATION

The ABAP code below is a full code listing to execute function module SLS_IOA_CHECK_IO_LOCATION including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_p_exists  
 
 TYPE LS_BOOLEAN
,
it_p_loctty  
 
 TYPE STANDARD TABLE OF SLS_LOCTTY,"TABLES PARAM
wa_p_loctty
 
 LIKE LINE OF it_p_loctty
.

 

SELECT single PLVAR 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_plvar).

 

SELECT single LOCID 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_locid).

 

SELECT single CLASS 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_class).

 

SELECT single GUID 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_guid).

 

SELECT single VAR1 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_var1).

 

SELECT single VAR2 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_var2).

 

SELECT single VAR3 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_var3).

 

SELECT single VAR4 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_var4).

 

SELECT single BEGDA 
  FROM SLS_LOCTTY 
  INTO @DATA(ld_p_date).

 

"populate fields of struture and append to itab
append wa_p_loctty to it_p_loctty.
.

CALL FUNCTION 'SLS_IOA_CHECK_IO_LOCATION'
  EXPORTING
    p_plvar =                    ld_p_plvar
    p_locid =                    ld_p_locid
    p_class =                    ld_p_class
    p_guid =                     ld_p_guid
    p_var1 =                     ld_p_var1
    p_var2 =                     ld_p_var2
    p_var3 =                     ld_p_var3
    p_var4 =                     ld_p_var4
    p_date =                     ld_p_date
  IMPORTING
    p_exists =                   ld_p_exists
  TABLES
    p_loctty =                   it_p_loctty
    .  "  SLS_IOA_CHECK_IO_LOCATION

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_p_exists
 
 TYPE LS_BOOLEAN ,
ld_p_plvar
 
 TYPE SLS_LOCTTY-PLVAR ,
it_p_loctty
 
 TYPE STANDARD TABLE OF SLS_LOCTTY ,
wa_p_loctty
 
 LIKE LINE OF it_p_loctty,
ld_p_locid
 
 TYPE SLS_LOCTTY-LOCID ,
ld_p_class
 
 TYPE SLS_LOCTTY-CLASS ,
ld_p_guid
 
 TYPE SLS_LOCTTY-GUID ,
ld_p_var1
 
 TYPE SLS_LOCTTY-VAR1 ,
ld_p_var2
 
 TYPE SLS_LOCTTY-VAR2 ,
ld_p_var3
 
 TYPE SLS_LOCTTY-VAR3 ,
ld_p_var4
 
 TYPE SLS_LOCTTY-VAR4 ,
ld_p_date
 
 TYPE SLS_LOCTTY-BEGDA .



SELECT single PLVAR 
  FROM SLS_LOCTTY 
  INTO ld_p_plvar.
 

"populate fields of struture and append to itab
append wa_p_loctty to it_p_loctty.

SELECT single LOCID 
  FROM SLS_LOCTTY 
  INTO ld_p_locid.


SELECT single CLASS 
  FROM SLS_LOCTTY 
  INTO ld_p_class.


SELECT single GUID 
  FROM SLS_LOCTTY 
  INTO ld_p_guid.


SELECT single VAR1 
  FROM SLS_LOCTTY 
  INTO ld_p_var1.


SELECT single VAR2 
  FROM SLS_LOCTTY 
  INTO ld_p_var2.


SELECT single VAR3 
  FROM SLS_LOCTTY 
  INTO ld_p_var3.


SELECT single VAR4 
  FROM SLS_LOCTTY 
  INTO ld_p_var4.


SELECT single BEGDA 
  FROM SLS_LOCTTY 
  INTO ld_p_date.

SAP Documentation for FM SLS_IOA_CHECK_IO_LOCATION