SOTR_DELETE_CONCEPT_ENTRY SAP Function module

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

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

Pattern for FM SOTR_DELETE_CONCEPT_ENTRY - SOTR DELETE CONCEPT ENTRY

CALL FUNCTION 'SOTR_DELETE_CONCEPT_ENTRY' "
  EXPORTING
    concept =                   " sotr_text-concept
*   object =                    " sotr_text-object
*   langu =                     " sy-langu
*   in_update_task =            " bapiflag
*   flag_correction_entry =     " as4flag       Flag (X or blank)
  EXCEPTIONS
    NO_ENTRY_FOUND = 1          "
    INVALID_PACKAGE = 2         "
    TEXT_NOT_CHANGEABLE = 3     "
    TEXT_ENQUEUED = 4           "
    NO_CORRECTION = 5           "
    PARAMETER_ERROR = 6         "
    .  "  SOTR_DELETE_CONCEPT_ENTRY

ABAP code example for Function Module SOTR_DELETE_CONCEPT_ENTRY

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

 

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

 

SELECT single OBJECT 
  FROM SOTR_TEXT 
  INTO @DATA(ld_object).


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

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

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

CALL FUNCTION 'SOTR_DELETE_CONCEPT_ENTRY'
  EXPORTING
    concept =                    ld_concept
*   object =                     ld_object
*   langu =                      ld_langu
*   in_update_task =             ld_in_update_task
*   flag_correction_entry =      ld_flag_correction_entry
  EXCEPTIONS
    NO_ENTRY_FOUND =             1
    INVALID_PACKAGE =            2
    TEXT_NOT_CHANGEABLE =        3
    TEXT_ENQUEUED =              4
    NO_CORRECTION =              5
    PARAMETER_ERROR =            6
    .  "  SOTR_DELETE_CONCEPT_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
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "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_concept
 
 TYPE SOTR_TEXT-CONCEPT ,
ld_object
 
 TYPE SOTR_TEXT-OBJECT ,
ld_langu
 
 TYPE SY-LANGU ,
ld_in_update_task
 
 TYPE BAPIFLAG ,
ld_flag_correction_entry
 
 TYPE AS4FLAG .



SELECT single CONCEPT 
  FROM SOTR_TEXT 
  INTO ld_concept.


SELECT single OBJECT 
  FROM SOTR_TEXT 
  INTO ld_object.

ld_langu = 'Check type of data required'.
ld_in_update_task = 'Check type of data required'.
ld_flag_correction_entry = 'Check type of data required'.