TERM_INSERT_ENTRY SAP Function module

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

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

Pattern for FM TERM_INSERT_ENTRY - TERM INSERT ENTRY

CALL FUNCTION 'TERM_INSERT_ENTRY' "
  EXPORTING
    concept =                   " sterm_head-concept
*   project_id =                " sterm_prj_head-project_key
  IMPORTING
    object =                    " sterm_link-object
    gl_project_id =             " sterm_prj_head-project_key
  CHANGING
    entry_attributes =          " sterm_link
    entry_values =              " sterm_text
*   entry_can_form =            " sterm_txtc
  EXCEPTIONS
    CONCEPT_MISSING = 1         "
    ERROR_IN_INSERT = 2         "
    AUTHORIZATION_FAILED = 3    "
    .  "  TERM_INSERT_ENTRY

ABAP code example for Function Module TERM_INSERT_ENTRY

The ABAP code below is a full code listing to execute function module TERM_INSERT_ENTRY 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_object  
 
 TYPE STERM_LINK-OBJECT
,
ld_gl_project_id  
 
 TYPE STERM_PRJ_HEAD-PROJECT_KEY
.


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

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

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

SELECT single CONCEPT 
  FROM STERM_HEAD 
  INTO @DATA(ld_concept).

 

SELECT single PROJECT_KEY 
  FROM STERM_PRJ_HEAD 
  INTO @DATA(ld_project_id).

.

CALL FUNCTION 'TERM_INSERT_ENTRY'
  EXPORTING
    concept =                    ld_concept
*   project_id =                 ld_project_id
  IMPORTING
    object =                     ld_object
    gl_project_id =              ld_gl_project_id
  CHANGING
    entry_attributes =           ld_entry_attributes
    entry_values =               ld_entry_values
*   entry_can_form =             ld_entry_can_form
  EXCEPTIONS
    CONCEPT_MISSING =            1
    ERROR_IN_INSERT =            2
    AUTHORIZATION_FAILED =       3
    .  "  TERM_INSERT_ENTRY

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
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_entry_attributes
 
 TYPE STERM_LINK ,
ld_object
 
 TYPE STERM_LINK-OBJECT ,
ld_concept
 
 TYPE STERM_HEAD-CONCEPT ,
ld_entry_values
 
 TYPE STERM_TEXT ,
ld_gl_project_id
 
 TYPE STERM_PRJ_HEAD-PROJECT_KEY ,
ld_project_id
 
 TYPE STERM_PRJ_HEAD-PROJECT_KEY ,
ld_entry_can_form
 
 TYPE STERM_TXTC .


ld_entry_attributes = 'Check type of data required'.

SELECT single CONCEPT 
  FROM STERM_HEAD 
  INTO ld_concept.

ld_entry_values = 'Check type of data required'.

SELECT single PROJECT_KEY 
  FROM STERM_PRJ_HEAD 
  INTO ld_project_id.

ld_entry_can_form = 'Check type of data required'.