SAP ARCHIVOBJECT_APPEND Function Module for
ARCHIVOBJECT_APPEND is a standard archivobject append 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 append FM, simply by entering the name ARCHIVOBJECT_APPEND 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_APPEND 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_APPEND'".
EXPORTING
ARCHIVE_ID = "
ARCHIVEDOC_ID = "
DOCUMENTCLASS = "
* LENGTH = 0 "
COMPID = "
* SIGNATURE = 'X' "
* VSCAN_PROFILE = '/SCMS/KPRO_CREATE' "
TABLES
* ARCHIVEOBJECT = "
* BINARCHIVOBJECT = "Buffer Table for Storing Table Data up to Length 1024
EXCEPTIONS
ERROR_ARCHIV = 1 BLOCKED_BY_POLICY = 2
IMPORTING Parameters details for ARCHIVOBJECT_APPEND
ARCHIVE_ID -
Data type: TOAAR-ARCHIV_IDOptional: No
Call by Reference: No ( called with pass by value option)
ARCHIVEDOC_ID -
Data type: TOAV0-ARC_DOC_IDOptional: No
Call by Reference: No ( called with pass by value option)
DOCUMENTCLASS -
Data type: TOADD-DOC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
LENGTH -
Data type: SAPB-LENGTHOptional: Yes
Call by Reference: No ( called with pass by value option)
COMPID -
Data type: HTTP_API-COMPIDOptional: No
Call by Reference: No ( called with pass by value option)
SIGNATURE -
Data type: TOAOM-AR_STATUSDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
VSCAN_PROFILE -
Data type: VSCAN_PROFILEDefault: '/SCMS/KPRO_CREATE'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ARCHIVOBJECT_APPEND
ARCHIVEOBJECT -
Data type: DOCSOptional: Yes
Call by Reference: Yes
BINARCHIVOBJECT - Buffer Table for Storing Table Data up to Length 1024
Data type: TBL1024Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_ARCHIV -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BLOCKED_BY_POLICY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ARCHIVOBJECT_APPEND 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_id | TYPE TOAAR-ARCHIV_ID, " | |||
| lv_error_archiv | TYPE TOAAR, " | |||
| lt_archiveobject | TYPE STANDARD TABLE OF DOCS, " | |||
| lv_archivedoc_id | TYPE TOAV0-ARC_DOC_ID, " | |||
| lt_binarchivobject | TYPE STANDARD TABLE OF TBL1024, " | |||
| lv_blocked_by_policy | TYPE TBL1024, " | |||
| lv_documentclass | TYPE TOADD-DOC_TYPE, " | |||
| lv_length | TYPE SAPB-LENGTH, " 0 | |||
| lv_compid | TYPE HTTP_API-COMPID, " | |||
| lv_signature | TYPE TOAOM-AR_STATUS, " 'X' | |||
| lv_vscan_profile | TYPE VSCAN_PROFILE. " '/SCMS/KPRO_CREATE' |
|   CALL FUNCTION 'ARCHIVOBJECT_APPEND' " |
| EXPORTING | ||
| ARCHIVE_ID | = lv_archive_id | |
| ARCHIVEDOC_ID | = lv_archivedoc_id | |
| DOCUMENTCLASS | = lv_documentclass | |
| LENGTH | = lv_length | |
| COMPID | = lv_compid | |
| SIGNATURE | = lv_signature | |
| VSCAN_PROFILE | = lv_vscan_profile | |
| TABLES | ||
| ARCHIVEOBJECT | = lt_archiveobject | |
| BINARCHIVOBJECT | = lt_binarchivobject | |
| EXCEPTIONS | ||
| ERROR_ARCHIV = 1 | ||
| BLOCKED_BY_POLICY = 2 | ||
| . " ARCHIVOBJECT_APPEND | ||
ABAP code using 7.40 inline data declarations to call FM ARCHIVOBJECT_APPEND
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 ARCHIV_ID FROM TOAAR INTO @DATA(ld_archive_id). | ||||
| "SELECT single ARC_DOC_ID FROM TOAV0 INTO @DATA(ld_archivedoc_id). | ||||
| "SELECT single DOC_TYPE FROM TOADD INTO @DATA(ld_documentclass). | ||||
| "SELECT single LENGTH FROM SAPB INTO @DATA(ld_length). | ||||
| "SELECT single COMPID FROM HTTP_API INTO @DATA(ld_compid). | ||||
| "SELECT single AR_STATUS FROM TOAOM INTO @DATA(ld_signature). | ||||
| DATA(ld_signature) | = 'X'. | |||
| DATA(ld_vscan_profile) | = '/SCMS/KPRO_CREATE'. | |||
Search for further information about these or an SAP related objects