SAP SUSR_PUT_ARCHIVED_DATA_TO_DB Function Module for
SUSR_PUT_ARCHIVED_DATA_TO_DB is a standard susr put archived data to db 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 susr put archived data to db FM, simply by entering the name SUSR_PUT_ARCHIVED_DATA_TO_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: SULA
Program Name: SAPLSULA
Main Program: SAPLSULA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SUSR_PUT_ARCHIVED_DATA_TO_DB 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 'SUSR_PUT_ARCHIVED_DATA_TO_DB'".
EXPORTING
* IT_ARCHIVE_RUNS_02 = "
* IT_ARCHIVE_RUNS_04 = "
* IT_ARCHIVE_RUNS_CD = "
* IT_ARCHIVE_RUNS_10 = "
* IT_ARCHIVE_RUNS_12 = "
IP_DONT_OVERWRITE = "
CHANGING
* CT_STATUS_02 = "
* CT_STATUS_04 = "
* CT_STATUS_CD = "
* CT_STATUS_10 = "
* CT_STATUS_12 = "
IMPORTING Parameters details for SUSR_PUT_ARCHIVED_DATA_TO_DB
IT_ARCHIVE_RUNS_02 -
Data type: ARCH_T_RUNSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ARCHIVE_RUNS_04 -
Data type: ARCH_T_RUNSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ARCHIVE_RUNS_CD -
Data type: ARCH_T_RUNSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ARCHIVE_RUNS_10 -
Data type: ARCH_T_RUNSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ARCHIVE_RUNS_12 -
Data type: ARCH_T_RUNSOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_DONT_OVERWRITE -
Data type: OS_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SUSR_PUT_ARCHIVED_DATA_TO_DB
CT_STATUS_02 -
Data type: SUSR_T_ARCSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_STATUS_04 -
Data type: SUSR_T_ARCSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_STATUS_CD -
Data type: SUSR_T_ARCSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_STATUS_10 -
Data type: SUSR_T_ARCSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_STATUS_12 -
Data type: SUSR_T_ARCSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUSR_PUT_ARCHIVED_DATA_TO_DB 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_ct_status_02 | TYPE SUSR_T_ARCSTAT, " | |||
lv_it_archive_runs_02 | TYPE ARCH_T_RUNS, " | |||
lv_ct_status_04 | TYPE SUSR_T_ARCSTAT, " | |||
lv_it_archive_runs_04 | TYPE ARCH_T_RUNS, " | |||
lv_ct_status_cd | TYPE SUSR_T_ARCSTAT, " | |||
lv_it_archive_runs_cd | TYPE ARCH_T_RUNS, " | |||
lv_ct_status_10 | TYPE SUSR_T_ARCSTAT, " | |||
lv_it_archive_runs_10 | TYPE ARCH_T_RUNS, " | |||
lv_ct_status_12 | TYPE SUSR_T_ARCSTAT, " | |||
lv_it_archive_runs_12 | TYPE ARCH_T_RUNS, " | |||
lv_ip_dont_overwrite | TYPE OS_BOOLEAN. " |
  CALL FUNCTION 'SUSR_PUT_ARCHIVED_DATA_TO_DB' " |
EXPORTING | ||
IT_ARCHIVE_RUNS_02 | = lv_it_archive_runs_02 | |
IT_ARCHIVE_RUNS_04 | = lv_it_archive_runs_04 | |
IT_ARCHIVE_RUNS_CD | = lv_it_archive_runs_cd | |
IT_ARCHIVE_RUNS_10 | = lv_it_archive_runs_10 | |
IT_ARCHIVE_RUNS_12 | = lv_it_archive_runs_12 | |
IP_DONT_OVERWRITE | = lv_ip_dont_overwrite | |
CHANGING | ||
CT_STATUS_02 | = lv_ct_status_02 | |
CT_STATUS_04 | = lv_ct_status_04 | |
CT_STATUS_CD | = lv_ct_status_cd | |
CT_STATUS_10 | = lv_ct_status_10 | |
CT_STATUS_12 | = lv_ct_status_12 | |
. " SUSR_PUT_ARCHIVED_DATA_TO_DB |
ABAP code using 7.40 inline data declarations to call FM SUSR_PUT_ARCHIVED_DATA_TO_DB
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.Search for further information about these or an SAP related objects