SAP MSS_FILLING_PROCESSES Function Module for MS SQL Server filling additonal information for processes monitor

Search SAP Function Modules

MSS_FILLING_PROCESSES is a standard mss filling processes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MS SQL Server filling additonal information for processes monitor 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 mss filling processes FM, simply by entering the name MSS_FILLING_PROCESSES into the relevant SAP transaction such as SE37 or SE38.

Function Group: SMSSDATA1
Program Name: SAPLSMSSDATA1
Main Program: SAPLSMSSDATA1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MSS_FILLING_PROCESSES 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 'MSS_FILLING_PROCESSES'"MS SQL Server filling additonal information for processes monitor
  EXPORTING
*  EX_STATUS =  "SQL Server process status; ie sleeping, running etc.
*  ONE_WP = 'N' "Name of the application program which owns the connection.
*  IN_STATUS =  "SQL Server process status; ie sleeping, running etc.
*  SAP_SPIDS =  "Single-character flag
*  RES_LOCKS =  "Single-character flag
*  CON_NAME = 'DEFAULT' "Logical name for a database connection
*  SCHEMA = ' ' "Schema name
*  LOCALSYS = ' ' "Local SAP system or not ('X' / ' ')
*  ONE_LOGIN = 'N' "SQL Server DB Object Name
*  ONE_HOST = 'N' "Hostname of the application server logged into SQL Server.

TABLES
   SQLPROCESSES =  "

EXCEPTIONS
   INVALID_EX_STATUS = 1    INVALID_IN_STATUS = 2    INVALID_SAP_SPIDS = 3    INVALID_RES_LOCKS = 4    DB_ERROR = 5    INTERNAL_ERROR = 6    CONNECT_ERROR = 7 

.

IMPORTING Parameters details for MSS_FILLING_PROCESSES

EX_STATUS - SQL Server process status; ie sleeping, running etc.

Data type: MSQ_PROCES-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

ONE_WP - Name of the application program which owns the connection.

Data type: MSQ_PROCES-PROGNAME
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_STATUS - SQL Server process status; ie sleeping, running etc.

Data type: MSQ_PROCES-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

SAP_SPIDS - Single-character flag

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

RES_LOCKS - Single-character flag

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

CON_NAME - Logical name for a database connection

Data type: DBCON-CON_NAME
Default: 'DEFAULT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCHEMA - Schema name

Data type: MSSSCHEMA
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOCALSYS - Local SAP system or not ('X' / ' ')

Data type: MSSCONNDATA-LOCALSYS
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

ONE_LOGIN - SQL Server DB Object Name

Data type: MSSSYSNAME
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ONE_HOST - Hostname of the application server logged into SQL Server.

Data type: MSQ_PROCES-HOSTNAME
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MSS_FILLING_PROCESSES

SQLPROCESSES -

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

EXCEPTIONS details

INVALID_EX_STATUS - parameter ex_status( exclude ) is invalid

Data type:
Optional: No
Call by Reference: Yes

INVALID_IN_STATUS - parameter in_status(include) is invalid

Data type:
Optional: No
Call by Reference: Yes

INVALID_SAP_SPIDS - parameter sap_spids 'Y' or 'N' or NULL

Data type:
Optional: No
Call by Reference: Yes

INVALID_RES_LOCKS - parameter res_locks 'Y' or 'N'

Data type:
Optional: No
Call by Reference: Yes

DB_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CONNECT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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