SAP ARCHIV_CONNECTION_INSERTUPDATE Function Module for
ARCHIV_CONNECTION_INSERTUPDATE is a standard archiv connection insertupdate 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 archiv connection insertupdate FM, simply by entering the name ARCHIV_CONNECTION_INSERTUPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OPTB
Program Name: SAPLOPTB
Main Program: SAPLOPTB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1
Function ARCHIV_CONNECTION_INSERTUPDATE 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 'ARCHIV_CONNECTION_INSERTUPDATE'".
EXPORTING
* ARCHIV_ID = "
* BARCODE = ' ' "Bar Code
ARC_DOC_ID = "
* AR_DATE = ' ' "
AR_OBJECT = "Object type to be archived
* DEL_DATE = ' ' "
* MANDANT = ' ' "
OBJECT_ID = "Unique object key of application
SAP_OBJECT = "Calling Application
* DOC_TYPE = ' ' "
EXCEPTIONS
ERROR_CONNECTIONTABLE = 1
IMPORTING Parameters details for ARCHIV_CONNECTION_INSERTUPDATE
ARCHIV_ID -
Data type: TOAV0-ARCHIV_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
BARCODE - Bar Code
Data type: TOAV0-ARC_DOC_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ARC_DOC_ID -
Data type: TOAV0-ARC_DOC_IDOptional: No
Call by Reference: No ( called with pass by value option)
AR_DATE -
Data type: TOAV0-AR_DATEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
AR_OBJECT - Object type to be archived
Data type: TOAOM-AR_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
DEL_DATE -
Data type: TOAV0-DEL_DATEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDANT -
Data type: TOA_ARCAS-MANDANTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_ID - Unique object key of application
Data type: SAPB-SAPOBJIDOptional: No
Call by Reference: No ( called with pass by value option)
SAP_OBJECT - Calling Application
Data type: TOAOM-SAP_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
DOC_TYPE -
Data type: TOADV-DOC_TYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CONNECTIONTABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ARCHIV_CONNECTION_INSERTUPDATE 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_archiv_id | TYPE TOAV0-ARCHIV_ID, " | |||
| lv_error_connectiontable | TYPE TOAV0, " | |||
| lv_barcode | TYPE TOAV0-ARC_DOC_ID, " SPACE | |||
| lv_arc_doc_id | TYPE TOAV0-ARC_DOC_ID, " | |||
| lv_ar_date | TYPE TOAV0-AR_DATE, " SPACE | |||
| lv_ar_object | TYPE TOAOM-AR_OBJECT, " | |||
| lv_del_date | TYPE TOAV0-DEL_DATE, " SPACE | |||
| lv_mandant | TYPE TOA_ARCAS-MANDANT, " SPACE | |||
| lv_object_id | TYPE SAPB-SAPOBJID, " | |||
| lv_sap_object | TYPE TOAOM-SAP_OBJECT, " | |||
| lv_doc_type | TYPE TOADV-DOC_TYPE. " SPACE |
| CALL FUNCTION 'ARCHIV_CONNECTION_INSERTUPDATE' " |
| EXPORTING | ||
| ARCHIV_ID | = lv_archiv_id | |
| BARCODE | = lv_barcode | |
| ARC_DOC_ID | = lv_arc_doc_id | |
| AR_DATE | = lv_ar_date | |
| AR_OBJECT | = lv_ar_object | |
| DEL_DATE | = lv_del_date | |
| MANDANT | = lv_mandant | |
| OBJECT_ID | = lv_object_id | |
| SAP_OBJECT | = lv_sap_object | |
| DOC_TYPE | = lv_doc_type | |
| EXCEPTIONS | ||
| ERROR_CONNECTIONTABLE = 1 | ||
| . " ARCHIV_CONNECTION_INSERTUPDATE | ||
ABAP code using 7.40 inline data declarations to call FM ARCHIV_CONNECTION_INSERTUPDATE
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 TOAV0 INTO @DATA(ld_archiv_id). | ||||
| "SELECT single ARC_DOC_ID FROM TOAV0 INTO @DATA(ld_barcode). | ||||
| DATA(ld_barcode) | = ' '. | |||
| "SELECT single ARC_DOC_ID FROM TOAV0 INTO @DATA(ld_arc_doc_id). | ||||
| "SELECT single AR_DATE FROM TOAV0 INTO @DATA(ld_ar_date). | ||||
| DATA(ld_ar_date) | = ' '. | |||
| "SELECT single AR_OBJECT FROM TOAOM INTO @DATA(ld_ar_object). | ||||
| "SELECT single DEL_DATE FROM TOAV0 INTO @DATA(ld_del_date). | ||||
| DATA(ld_del_date) | = ' '. | |||
| "SELECT single MANDANT FROM TOA_ARCAS INTO @DATA(ld_mandant). | ||||
| DATA(ld_mandant) | = ' '. | |||
| "SELECT single SAPOBJID FROM SAPB INTO @DATA(ld_object_id). | ||||
| "SELECT single SAP_OBJECT FROM TOAOM INTO @DATA(ld_sap_object). | ||||
| "SELECT single DOC_TYPE FROM TOADV INTO @DATA(ld_doc_type). | ||||
| DATA(ld_doc_type) | = ' '. | |||
Search for further information about these or an SAP related objects