SAP SALK_XML_FILE_POLL Function Module for









SALK_XML_FILE_POLL is a standard salk xml file poll 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 salk xml file poll FM, simply by entering the name SALK_XML_FILE_POLL into the relevant SAP transaction such as SE37 or SE38.

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



Function SALK_XML_FILE_POLL 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 'SALK_XML_FILE_POLL'"
  EXPORTING
*  AGENT_DESTINATION =  "Logical Destination (Specified in Function Call)
*  DIRECTORY =  "Alert: monitoring type full name
*  FILE_SPECIFICATION =  "Alert: monitoring type full name
*  FILE_SELECTOR =  "Alert: Short Name of Monitoring Type
*  METHOD_NAME =  "Alert: Logical Name of Tool
*  CIMXML =  "'X' - XML Document in cimXML Format

TABLES
   MT_TOOL_INFO =  "Alert: Description of a tool instance to be executed

EXCEPTIONS
   INCOMPLETE_ARGUMENTS = 1    INCORRECT_ARGUMENTS = 2    LOCK_FILE_FOUND_NO_FILES_READ = 3    INTERNAL_ERROR_SEE_SELFMONI = 4
.



IMPORTING Parameters details for SALK_XML_FILE_POLL

AGENT_DESTINATION - Logical Destination (Specified in Function Call)

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

DIRECTORY - Alert: monitoring type full name

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

FILE_SPECIFICATION - Alert: monitoring type full name

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

FILE_SELECTOR - Alert: Short Name of Monitoring Type

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

METHOD_NAME - Alert: Logical Name of Tool

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

CIMXML - 'X' - XML Document in cimXML Format

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

TABLES Parameters details for SALK_XML_FILE_POLL

MT_TOOL_INFO - Alert: Description of a tool instance to be executed

Data type: ALTLEXDESC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INCOMPLETE_ARGUMENTS -

Data type:
Optional: No
Call by Reference: Yes

INCORRECT_ARGUMENTS -

Data type:
Optional: No
Call by Reference: Yes

LOCK_FILE_FOUND_NO_FILES_READ -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR_SEE_SELFMONI -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SALK_XML_FILE_POLL 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:
lt_mt_tool_info  TYPE STANDARD TABLE OF ALTLEXDESC, "   
lv_agent_destination  TYPE RFCDEST, "   
lv_incomplete_arguments  TYPE RFCDEST, "   
lv_directory  TYPE TEXT_512, "   
lv_incorrect_arguments  TYPE TEXT_512, "   
lv_file_specification  TYPE TEXT_512, "   
lv_lock_file_found_no_files_read  TYPE TEXT_512, "   
lv_file_selector  TYPE ALMTNAMESH, "   
lv_internal_error_see_selfmoni  TYPE ALMTNAMESH, "   
lv_method_name  TYPE ALTOOLKEY, "   
lv_cimxml  TYPE CHAR1. "   

  CALL FUNCTION 'SALK_XML_FILE_POLL'  "
    EXPORTING
         AGENT_DESTINATION = lv_agent_destination
         DIRECTORY = lv_directory
         FILE_SPECIFICATION = lv_file_specification
         FILE_SELECTOR = lv_file_selector
         METHOD_NAME = lv_method_name
         CIMXML = lv_cimxml
    TABLES
         MT_TOOL_INFO = lt_mt_tool_info
    EXCEPTIONS
        INCOMPLETE_ARGUMENTS = 1
        INCORRECT_ARGUMENTS = 2
        LOCK_FILE_FOUND_NO_FILES_READ = 3
        INTERNAL_ERROR_SEE_SELFMONI = 4
. " SALK_XML_FILE_POLL




ABAP code using 7.40 inline data declarations to call FM SALK_XML_FILE_POLL

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



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!