OBJ_SET_IMPORTABLE SAP Function module

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

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

Pattern for FM OBJ_SET_IMPORTABLE - OBJ SET IMPORTABLE

CALL FUNCTION 'OBJ_SET_IMPORTABLE' "
  EXPORTING
*   iv_korrnum = ' '            " e070-trkorr   Task number to be used
    iv_objectname =             " objh-objectname  Object Name
    iv_objecttype =             " objh-objecttype  Object Type
    iv_importable =             " objh-importable
*   iv_no_correction = ' '      " c
  EXCEPTIONS
    OBJECT_NOT_DEFINED = 1      "               No Object Could Be Found
    INVALID = 2                 "
    TRANSPORT_ERROR = 3         "               Error occurred in correction connection
    OBJECT_ENQUEUE_FAILED = 4   "
    .  "  OBJ_SET_IMPORTABLE

ABAP code example for Function Module OBJ_SET_IMPORTABLE

The ABAP code below is a full code listing to execute function module OBJ_SET_IMPORTABLE 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).

 

SELECT single TRKORR 
  FROM E070 
  INTO @DATA(ld_iv_korrnum).

 

SELECT single OBJECTNAME 
  FROM OBJH 
  INTO @DATA(ld_iv_objectname).

 

SELECT single OBJECTTYPE 
  FROM OBJH 
  INTO @DATA(ld_iv_objecttype).

 

SELECT single IMPORTABLE 
  FROM OBJH 
  INTO @DATA(ld_iv_importable).


DATA(ld_iv_no_correction) = 'Check type of data required'.
.

CALL FUNCTION 'OBJ_SET_IMPORTABLE'
  EXPORTING
*   iv_korrnum =                 ld_iv_korrnum
    iv_objectname =              ld_iv_objectname
    iv_objecttype =              ld_iv_objecttype
    iv_importable =              ld_iv_importable
*   iv_no_correction =           ld_iv_no_correction
  EXCEPTIONS
    OBJECT_NOT_DEFINED =         1
    INVALID =                    2
    TRANSPORT_ERROR =            3
    OBJECT_ENQUEUE_FAILED =      4
    .  "  OBJ_SET_IMPORTABLE

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_iv_korrnum
 
 TYPE E070-TRKORR ,
ld_iv_objectname
 
 TYPE OBJH-OBJECTNAME ,
ld_iv_objecttype
 
 TYPE OBJH-OBJECTTYPE ,
ld_iv_importable
 
 TYPE OBJH-IMPORTABLE ,
ld_iv_no_correction
 
 TYPE C .



SELECT single TRKORR 
  FROM E070 
  INTO ld_iv_korrnum.


SELECT single OBJECTNAME 
  FROM OBJH 
  INTO ld_iv_objectname.


SELECT single OBJECTTYPE 
  FROM OBJH 
  INTO ld_iv_objecttype.


SELECT single IMPORTABLE 
  FROM OBJH 
  INTO ld_iv_importable.

ld_iv_no_correction = 'Check type of data required'.