OIF_LIS_USAGE_CHECK SAP Function module - Check usage of Business Location objects in LIS - IS-Oil MRN

OIF_LIS_USAGE_CHECK 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 OIF_LIS_USAGE_CHECK into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM OIF_LIS_USAGE_CHECK - OIF LIS USAGE CHECK

CALL FUNCTION 'OIF_LIS_USAGE_CHECK' "Check usage of Business Location objects in LIS - IS-Oil MRN
  EXPORTING
    i_pblnr =                   " oifspbl-pblnr  Business location ID
    i_kunnr =                   " kna1-kunnr    Customer business partner ID
*   i_ttmdat =                  " roifbbp1-ttmstm  End of partner function validity period - timestamp
  IMPORTING
    e_object_not_in_use =       " roifa-shoblo  Object is not in use in LIS
  EXCEPTIONS
    MISSING_LOCATION_ID = 1     "               Missing input Location ID
    MISSING_OBJECT_ID = 2       "               Missing partner or object ID
    .  "  OIF_LIS_USAGE_CHECK

ABAP code example for Function Module OIF_LIS_USAGE_CHECK

The ABAP code below is a full code listing to execute function module OIF_LIS_USAGE_CHECK 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_e_object_not_in_use  
 
 TYPE ROIFA-SHOBLO
.

 

SELECT single PBLNR 
  FROM OIFSPBL 
  INTO @DATA(ld_i_pblnr).

 

SELECT single KUNNR 
  FROM KNA1 
  INTO @DATA(ld_i_kunnr).



DATA(ld_i_ttmdat) = Check type of data required
.

CALL FUNCTION 'OIF_LIS_USAGE_CHECK'
  EXPORTING
    i_pblnr =                    ld_i_pblnr
    i_kunnr =                    ld_i_kunnr
*   i_ttmdat =                   ld_i_ttmdat
  IMPORTING
    e_object_not_in_use =        ld_e_object_not_in_use
  EXCEPTIONS
    MISSING_LOCATION_ID =        1
    MISSING_OBJECT_ID =          2
    .  "  OIF_LIS_USAGE_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_e_object_not_in_use
 
 TYPE ROIFA-SHOBLO ,
ld_i_pblnr
 
 TYPE OIFSPBL-PBLNR ,
ld_i_kunnr
 
 TYPE KNA1-KUNNR ,
ld_i_ttmdat
 
 TYPE ROIFBBP1-TTMSTM .



SELECT single PBLNR 
  FROM OIFSPBL 
  INTO ld_i_pblnr.


SELECT single KUNNR 
  FROM KNA1 
  INTO ld_i_kunnr.


ld_i_ttmdat = Check type of data required