DDIF_TABL_ACTIVATE SAP Function module - DD: Interface to activate a table

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

Associated Function Group: SDIF
Released Date: 08.05.1996
Processing type: Normal fucntion module

Pattern for FM DDIF_TABL_ACTIVATE - DDIF TABL ACTIVATE

CALL FUNCTION 'DDIF_TABL_ACTIVATE' "DD: Interface to activate a table
  EXPORTING
    name =                      " ddobjname     Name of the Table to be Activated
*   auth_chk = 'X'              " ddbool_d      'X': Perform Author. Check for DB Operations
*   prid = -1                   " sy-tabix      ID for Log Writer
*   excommit = 'X'              " dctablact-excommit  Specifies whether a commit is to be sent
  IMPORTING
    rc =                        " sy-subrc      Result of Activation
  EXCEPTIONS
    NOT_FOUND = 1               "               Table not Found
    PUT_FAILURE = 2             "               Table could not be Written
    .  "  DDIF_TABL_ACTIVATE

ABAP code example for Function Module DDIF_TABL_ACTIVATE

The ABAP code below is a full code listing to execute function module DDIF_TABL_ACTIVATE 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_rc  
 
 TYPE SY-SUBRC
.


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

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

DATA(ld_prid) = '123 '.


DATA(ld_excommit) = some text here
.

CALL FUNCTION 'DDIF_TABL_ACTIVATE'
  EXPORTING
    name =                       ld_name
*   auth_chk =                   ld_auth_chk
*   prid =                       ld_prid
*   excommit =                   ld_excommit
  IMPORTING
    rc =                         ld_rc
  EXCEPTIONS
    NOT_FOUND =                  1
    PUT_FAILURE =                2
    .  "  DDIF_TABL_ACTIVATE

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_rc
 
 TYPE SY-SUBRC ,
ld_name
 
 TYPE DDOBJNAME ,
ld_auth_chk
 
 TYPE DDBOOL_D ,
ld_prid
 
 TYPE SY-TABIX ,
ld_excommit
 
 TYPE DCTABLACT-EXCOMMIT .


ld_name = '123 '.
ld_auth_chk = '123 '.
ld_prid = '123 '.

ld_excommit = some text here

SAP Documentation for FM DDIF_TABL_ACTIVATE