SRM_RECORD_DELETE SAP Function module

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

Associated Function Group: SRM_BAPI_RECORD
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM SRM_RECORD_DELETE - SRM RECORD DELETE

CALL FUNCTION 'SRM_RECORD_DELETE' "
  EXPORTING
    objectid =                  " bapisrmrec-guid
    documentclass =             " bapisrmrec-docclass
*   doc_context =               " bapidoccontext
  IMPORTING
    return =                    " bapiret2      Return Code
  EXCEPTIONS
    CONTAINER_IS_LOCKED = 1     "
    NOT_AUTHORIZED = 2          "
    INTERNAL_ERROR = 3          "               Internal Error
    PARAMETER_ERROR = 4         "               Parameter error
    CONTAINER_NOT_FOUND = 5     "
    CONTAINER_NOT_DELETEABLE = 6  "
    .  "  SRM_RECORD_DELETE

ABAP code example for Function Module SRM_RECORD_DELETE

The ABAP code below is a full code listing to execute function module SRM_RECORD_DELETE 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_return  
 
 TYPE BAPIRET2
.



DATA(ld_objectid) = some text here


DATA(ld_documentclass) = some text here

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

CALL FUNCTION 'SRM_RECORD_DELETE'
  EXPORTING
    objectid =                   ld_objectid
    documentclass =              ld_documentclass
*   doc_context =                ld_doc_context
  IMPORTING
    return =                     ld_return
  EXCEPTIONS
    CONTAINER_IS_LOCKED =        1
    NOT_AUTHORIZED =             2
    INTERNAL_ERROR =             3
    PARAMETER_ERROR =            4
    CONTAINER_NOT_FOUND =        5
    CONTAINER_NOT_DELETEABLE =    6
    .  "  SRM_RECORD_DELETE

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_return
 
 TYPE BAPIRET2 ,
ld_objectid
 
 TYPE BAPISRMREC-GUID ,
ld_documentclass
 
 TYPE BAPISRMREC-DOCCLASS ,
ld_doc_context
 
 TYPE BAPIDOCCONTEXT .



ld_objectid = some text here

ld_documentclass = some text here
ld_doc_context = 'Check type of data required'.