SAP ADK_MON_FILE_DELETED Function Module for









ADK_MON_FILE_DELETED is a standard adk mon file deleted 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 adk mon file deleted FM, simply by entering the name ADK_MON_FILE_DELETED into the relevant SAP transaction such as SE37 or SE38.

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



Function ADK_MON_FILE_DELETED 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 'ADK_MON_FILE_DELETED'"
EXPORTING
OBJECT = "Archiving object name
SESSION = "Archiving Session According to Archive Management
FILEKEY = "
* JOBNAME = ' ' "
* JOBCOUNT = ' ' "
.



IMPORTING Parameters details for ADK_MON_FILE_DELETED

OBJECT - Archiving object name

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

SESSION - Archiving Session According to Archive Management

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

FILEKEY -

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

JOBNAME -

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

JOBCOUNT -

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

Copy and paste ABAP code example for ADK_MON_FILE_DELETED 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_object  TYPE ARCH_OBJ-OBJECT, "   
lv_session  TYPE ADMI_RUN-DOCUMENT, "   
lv_filekey  TYPE ADMI_FILES-ARCHIV_KEY, "   
lv_jobname  TYPE TBTCJOB-JOBNAME, "   SPACE
lv_jobcount  TYPE TBTCJOB-JOBCOUNT. "   SPACE

  CALL FUNCTION 'ADK_MON_FILE_DELETED'  "
    EXPORTING
         OBJECT = lv_object
         SESSION = lv_session
         FILEKEY = lv_filekey
         JOBNAME = lv_jobname
         JOBCOUNT = lv_jobcount
. " ADK_MON_FILE_DELETED




ABAP code using 7.40 inline data declarations to call FM ADK_MON_FILE_DELETED

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 OBJECT FROM ARCH_OBJ INTO @DATA(ld_object).
 
"SELECT single DOCUMENT FROM ADMI_RUN INTO @DATA(ld_session).
 
"SELECT single ARCHIV_KEY FROM ADMI_FILES INTO @DATA(ld_filekey).
 
"SELECT single JOBNAME FROM TBTCJOB INTO @DATA(ld_jobname).
DATA(ld_jobname) = ' '.
 
"SELECT single JOBCOUNT FROM TBTCJOB INTO @DATA(ld_jobcount).
DATA(ld_jobcount) = ' '.
 


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!