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

Function ARCH0817_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 'ARCH0817_ARCHIVE_OBJECT'".
EXPORTING
ARCHIVE_HANDLE = "
DATA_ENTRY = "
* CLIENT = SY-MANDT "
* OBJECT_DELETE_FLAG = 'X' "
IMPORTING Parameters details for ARCH0817_ARCHIVE_OBJECT
ARCHIVE_HANDLE -
Data type: SY-TABIXOptional: No
Call by Reference: Yes
DATA_ENTRY -
Data type: TOADLOptional: No
Call by Reference: Yes
CLIENT -
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: Yes
OBJECT_DELETE_FLAG -
Data type: TOAOM-AR_STATUSDefault: 'X'
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ARCH0817_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_data_entry | TYPE TOADL, " | |||
| lv_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_object_delete_flag | TYPE TOAOM-AR_STATUS. " 'X' |
|   CALL FUNCTION 'ARCH0817_ARCHIVE_OBJECT' " |
| EXPORTING | ||
| ARCHIVE_HANDLE | = lv_archive_handle | |
| DATA_ENTRY | = lv_data_entry | |
| CLIENT | = lv_client | |
| OBJECT_DELETE_FLAG | = lv_object_delete_flag | |
| . " ARCH0817_ARCHIVE_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM ARCH0817_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 MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single AR_STATUS FROM TOAOM INTO @DATA(ld_object_delete_flag). | ||||
| DATA(ld_object_delete_flag) | = 'X'. | |||
Search for further information about these or an SAP related objects