SAP ARCHIVE_ADMIN_CHECK_STATUS Function Module for Status Information Is Transferred to Archiving Object

Search SAP Function Modules

ARCHIVE_ADMIN_CHECK_STATUS is a standard archive admin check status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Status Information Is Transferred to Archiving Object processing and below is the pattern details for this FM, 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 archive admin check status FM, simply by entering the name ARCHIVE_ADMIN_CHECK_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: AADM
Program Name: SAPLAADM
Main Program: SAPLAADM
Appliation area: S
Release date: 03-Jan-1995
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ARCHIVE_ADMIN_CHECK_STATUS 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 'ARCHIVE_ADMIN_CHECK_STATUS'"Status Information Is Transferred to Archiving Object
  EXPORTING
   OBJECT =  "Archiving Object
*  DISREGARD_OWN_JOB = ' ' "Do Not Consider Own Job
*  ARCHIVING_SESSION =  "Archiving Session Number

 IMPORTING
   ARCHIVE_PROGRAM_IS_RUNNING =  "Archive Program Running
   NOT_DELETED_FILE_EXISTS =  "Undeleted Files Exist
   INTERRUPTED_SESSIONS =  "Interrupted Sessions Exist

TABLES
*  RUNNING_JOBS =  "Running Archiving Jobs

EXCEPTIONS
   OBJECT_NOT_FOUND = 1 

.

IMPORTING Parameters details for ARCHIVE_ADMIN_CHECK_STATUS

OBJECT - Archiving Object

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

DISREGARD_OWN_JOB - Do Not Consider Own Job

Data type: BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: Yes

ARCHIVING_SESSION - Archiving Session Number

Data type: ADMI_RUN_D
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ARCHIVE_ADMIN_CHECK_STATUS

ARCHIVE_PROGRAM_IS_RUNNING - Archive Program Running

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

NOT_DELETED_FILE_EXISTS - Undeleted Files Exist

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

INTERRUPTED_SESSIONS - Interrupted Sessions Exist

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

TABLES Parameters details for ARCHIVE_ADMIN_CHECK_STATUS

RUNNING_JOBS - Running Archiving Jobs

Data type: ADMI_JOBS
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

OBJECT_NOT_FOUND - Unknown Object

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

Copy and paste ABAP code example for ARCHIVE_ADMIN_CHECK_STATUS 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.

ABAP code using 7.40 inline data declarations to call FM ARCHIVE_ADMIN_CHECK_STATUS

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