SAP IDOC_ARCHIVE_OBJECT Function Module for
IDOC_ARCHIVE_OBJECT is a standard idoc archive object 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 idoc archive object FM, simply by entering the name IDOC_ARCHIVE_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDI_ARCH
Program Name: SAPLEDI_ARCH
Main Program: SAPLEDI_ARCH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_ARCHIVE_OBJECT 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 'IDOC_ARCHIVE_OBJECT'".
EXPORTING
ARCHIVE_HANDLE = "
DOCNUM = "
* OBJECT_DELETE_FLAG = 'X' "
EXCEPTIONS
WRONG_ACCESS_TO_ARCHIVE = 1
IMPORTING Parameters details for IDOC_ARCHIVE_OBJECT
ARCHIVE_HANDLE -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
DOCNUM -
Data type: EDIDC-DOCNUMOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_DELETE_FLAG -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_ACCESS_TO_ARCHIVE - Incorrect archive access mode
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_ARCHIVE_OBJECT 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_archive_handle | TYPE SY-TABIX, " | |||
| lv_wrong_access_to_archive | TYPE SY, " | |||
| lv_docnum | TYPE EDIDC-DOCNUM, " | |||
| lv_object_delete_flag | TYPE EDIDC. " 'X' |
|   CALL FUNCTION 'IDOC_ARCHIVE_OBJECT' " |
| EXPORTING | ||
| ARCHIVE_HANDLE | = lv_archive_handle | |
| DOCNUM | = lv_docnum | |
| OBJECT_DELETE_FLAG | = lv_object_delete_flag | |
| EXCEPTIONS | ||
| WRONG_ACCESS_TO_ARCHIVE = 1 | ||
| . " IDOC_ARCHIVE_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_ARCHIVE_OBJECT
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 TABIX FROM SY INTO @DATA(ld_archive_handle). | ||||
| "SELECT single DOCNUM FROM EDIDC INTO @DATA(ld_docnum). | ||||
| DATA(ld_object_delete_flag) | = 'X'. | |||
Search for further information about these or an SAP related objects