CTS_ORLA_SET_TABDIRDEVC SAP Function module

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

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

Pattern for FM CTS_ORLA_SET_TABDIRDEVC - CTS ORLA SET TABDIRDEVC

CALL FUNCTION 'CTS_ORLA_SET_TABDIRDEVC' "
  EXPORTING
    iv_tabname =                " tabname       Table Name
    iv_granfield1 =             " fieldname     Field Name
    iv_granfield2 =             " fieldname     Field Name
    iv_fieldvalue1 =            " tabdirdevc-keyrange1  Field value for originality assignment
    iv_fieldvalue2 =            " tabdirdevc-keyrange2  Field value for originality assignment
    iv_devclass =               " devclass      Package
  EXCEPTIONS
    WRONG_GRANULARITY = 1       "
    ASSIGNMENT_NOT_POSSIBLE = 2  "
    .  "  CTS_ORLA_SET_TABDIRDEVC

ABAP code example for Function Module CTS_ORLA_SET_TABDIRDEVC

The ABAP code below is a full code listing to execute function module CTS_ORLA_SET_TABDIRDEVC 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_iv_tabname) = 'Check type of data required'.

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

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

SELECT single KEYRANGE1 
  FROM TABDIRDEVC 
  INTO @DATA(ld_iv_fieldvalue1).

 

SELECT single KEYRANGE2 
  FROM TABDIRDEVC 
  INTO @DATA(ld_iv_fieldvalue2).


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

CALL FUNCTION 'CTS_ORLA_SET_TABDIRDEVC'
  EXPORTING
    iv_tabname =                 ld_iv_tabname
    iv_granfield1 =              ld_iv_granfield1
    iv_granfield2 =              ld_iv_granfield2
    iv_fieldvalue1 =             ld_iv_fieldvalue1
    iv_fieldvalue2 =             ld_iv_fieldvalue2
    iv_devclass =                ld_iv_devclass
  EXCEPTIONS
    WRONG_GRANULARITY =          1
    ASSIGNMENT_NOT_POSSIBLE =    2
    .  "  CTS_ORLA_SET_TABDIRDEVC

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_iv_tabname
 
 TYPE TABNAME ,
ld_iv_granfield1
 
 TYPE FIELDNAME ,
ld_iv_granfield2
 
 TYPE FIELDNAME ,
ld_iv_fieldvalue1
 
 TYPE TABDIRDEVC-KEYRANGE1 ,
ld_iv_fieldvalue2
 
 TYPE TABDIRDEVC-KEYRANGE2 ,
ld_iv_devclass
 
 TYPE DEVCLASS .


ld_iv_tabname = 'Check type of data required'.
ld_iv_granfield1 = 'Check type of data required'.
ld_iv_granfield2 = 'Check type of data required'.

SELECT single KEYRANGE1 
  FROM TABDIRDEVC 
  INTO ld_iv_fieldvalue1.


SELECT single KEYRANGE2 
  FROM TABDIRDEVC 
  INTO ld_iv_fieldvalue2.

ld_iv_devclass = 'Check type of data required'.