SAP ARCHIVOBJECT_APPEND_DIALOG Function Module for









ARCHIVOBJECT_APPEND_DIALOG is a standard archivobject append dialog 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 dialog FM, simply by entering the name ARCHIVOBJECT_APPEND_DIALOG into the relevant SAP transaction such as SE37 or SE38.

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



Function ARCHIVOBJECT_APPEND_DIALOG 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_DIALOG'"
  EXPORTING
*  SIGN = ' ' "
*  OBJECT_ID = ' ' "SAP ArchiveLink: Object ID (Object Identifier)
*  SAP_OBJECT =  "SAP ArchiveLink: Object type of business object

 IMPORTING
   ARCHIV_DOC_ID =  "ID of document to be archived
   ARCHIV_ID =  "ID of referenced archive
   RETURNCODE =  "
   DOCUMENT_TYPE =  "
   AR_OBJECT =  "Document Type

EXCEPTIONS
   ERROR_ARCHIV = 1    ERROR_KERNEL = 2    NOT_UNIQUE = 3    NOVIEWER = 4    CANCEL_BUTT = 5
.



IMPORTING Parameters details for ARCHIVOBJECT_APPEND_DIALOG

SIGN -

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

OBJECT_ID - SAP ArchiveLink: Object ID (Object Identifier)

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

SAP_OBJECT - SAP ArchiveLink: Object type of business object

Data type: TOAV0-SAP_OBJECT
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ARCHIVOBJECT_APPEND_DIALOG

ARCHIV_DOC_ID - ID of document to be archived

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

ARCHIV_ID - ID of referenced archive

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

RETURNCODE -

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

DOCUMENT_TYPE -

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

AR_OBJECT - Document Type

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

EXCEPTIONS details

ERROR_ARCHIV - Error in archive system/archive interface

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

ERROR_KERNEL - Error in SAP kernel

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

NOT_UNIQUE -

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

NOVIEWER -

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

CANCEL_BUTT -

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

Copy and paste ABAP code example for ARCHIVOBJECT_APPEND_DIALOG 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_sign  TYPE SAPB-SAPBZZ, "   SPACE
lv_error_archiv  TYPE SAPB, "   
lv_archiv_doc_id  TYPE SAPB-SAPADOKID, "   
lv_archiv_id  TYPE TOAAR-ARCHIV_ID, "   
lv_object_id  TYPE TOAV0-OBJECT_ID, "   SPACE
lv_error_kernel  TYPE TOAV0, "   
lv_not_unique  TYPE TOAV0, "   
lv_returncode  TYPE TOAV0, "   
lv_sap_object  TYPE TOAV0-SAP_OBJECT, "   
lv_noviewer  TYPE TOAV0, "   
lv_document_type  TYPE TOADV-DOC_TYPE, "   
lv_ar_object  TYPE TOAOM-AR_OBJECT, "   
lv_cancel_butt  TYPE TOAOM. "   

  CALL FUNCTION 'ARCHIVOBJECT_APPEND_DIALOG'  "
    EXPORTING
         SIGN = lv_sign
         OBJECT_ID = lv_object_id
         SAP_OBJECT = lv_sap_object
    IMPORTING
         ARCHIV_DOC_ID = lv_archiv_doc_id
         ARCHIV_ID = lv_archiv_id
         RETURNCODE = lv_returncode
         DOCUMENT_TYPE = lv_document_type
         AR_OBJECT = lv_ar_object
    EXCEPTIONS
        ERROR_ARCHIV = 1
        ERROR_KERNEL = 2
        NOT_UNIQUE = 3
        NOVIEWER = 4
        CANCEL_BUTT = 5
. " ARCHIVOBJECT_APPEND_DIALOG




ABAP code using 7.40 inline data declarations to call FM ARCHIVOBJECT_APPEND_DIALOG

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 SAPBZZ FROM SAPB INTO @DATA(ld_sign).
DATA(ld_sign) = ' '.
 
 
"SELECT single SAPADOKID FROM SAPB INTO @DATA(ld_archiv_doc_id).
 
"SELECT single ARCHIV_ID FROM TOAAR INTO @DATA(ld_archiv_id).
 
"SELECT single OBJECT_ID FROM TOAV0 INTO @DATA(ld_object_id).
DATA(ld_object_id) = ' '.
 
 
 
 
"SELECT single SAP_OBJECT FROM TOAV0 INTO @DATA(ld_sap_object).
 
 
"SELECT single DOC_TYPE FROM TOADV INTO @DATA(ld_document_type).
 
"SELECT single AR_OBJECT FROM TOAOM INTO @DATA(ld_ar_object).
 
 


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!