SAP ARCHIVOBJECT_DELETE Function Module for









ARCHIVOBJECT_DELETE is a standard archivobject delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for archivobject delete FM, simply by entering the name ARCHIVOBJECT_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ARCHIVOBJECT
Program Name: SAPLARCHIVOBJECT
Main Program: SAPLARCHIVOBJECT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARCHIVOBJECT_DELETE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ARCHIVOBJECT_DELETE'"
EXPORTING
ARCHIV_DOC_ID = "Identifier of document to be deleted
* OBJECT_ID = "
ARCHIV_ID = "Identification of the archive
* SIGN = ' ' "
* DOC_TYPE = ' ' "
* COMPID = ' ' "
* SAP_OBJECT = "
* AR_OBJECT = "
* AR_DATE = "
* DEL_DATE = "

EXCEPTIONS
ERROR_ARCHIV = 1 ERROR_COMMUNICATIONTABLE = 2 ERROR_KERNEL = 3
.



IMPORTING Parameters details for ARCHIVOBJECT_DELETE

ARCHIV_DOC_ID - Identifier of document to be deleted

Data type: SAPB-SAPADOKID
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_ID -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARCHIV_ID - Identification of the archive

Data type: TOAAR-ARCHIV_ID
Optional: No
Call by Reference: No ( called with pass by value option)

SIGN -

Data type: SAPB-SAPBZZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOC_TYPE -

Data type: TOADV-DOC_TYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

COMPID -

Data type: HTTP_API-COMPID
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SAP_OBJECT -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

AR_OBJECT -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

AR_DATE -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEL_DATE -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_ARCHIV -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_COMMUNICATIONTABLE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_KERNEL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ARCHIVOBJECT_DELETE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_error_archiv  TYPE STRING, "   
lv_archiv_doc_id  TYPE SAPB-SAPADOKID, "   
lv_object_id  TYPE C, "   
lv_archiv_id  TYPE TOAAR-ARCHIV_ID, "   
lv_error_communicationtable  TYPE TOAAR, "   
lv_sign  TYPE SAPB-SAPBZZ, "   SPACE
lv_error_kernel  TYPE SAPB, "   
lv_doc_type  TYPE TOADV-DOC_TYPE, "   SPACE
lv_compid  TYPE HTTP_API-COMPID, "   SPACE
lv_sap_object  TYPE C, "   
lv_ar_object  TYPE C, "   
lv_ar_date  TYPE C, "   
lv_del_date  TYPE C. "   

  CALL FUNCTION 'ARCHIVOBJECT_DELETE'  "
    EXPORTING
         ARCHIV_DOC_ID = lv_archiv_doc_id
         OBJECT_ID = lv_object_id
         ARCHIV_ID = lv_archiv_id
         SIGN = lv_sign
         DOC_TYPE = lv_doc_type
         COMPID = lv_compid
         SAP_OBJECT = lv_sap_object
         AR_OBJECT = lv_ar_object
         AR_DATE = lv_ar_date
         DEL_DATE = lv_del_date
    EXCEPTIONS
        ERROR_ARCHIV = 1
        ERROR_COMMUNICATIONTABLE = 2
        ERROR_KERNEL = 3
. " ARCHIVOBJECT_DELETE




ABAP code using 7.40 inline data declarations to call FM ARCHIVOBJECT_DELETE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single SAPADOKID FROM SAPB INTO @DATA(ld_archiv_doc_id).
 
 
"SELECT single ARCHIV_ID FROM TOAAR INTO @DATA(ld_archiv_id).
 
 
"SELECT single SAPBZZ FROM SAPB INTO @DATA(ld_sign).
DATA(ld_sign) = ' '.
 
 
"SELECT single DOC_TYPE FROM TOADV INTO @DATA(ld_doc_type).
DATA(ld_doc_type) = ' '.
 
"SELECT single COMPID FROM HTTP_API INTO @DATA(ld_compid).
DATA(ld_compid) = ' '.
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!