SAP MSS_GET_LOGSIZE Function Module for SQL Server transaction log size
MSS_GET_LOGSIZE is a standard mss get logsize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SQL Server transaction log size 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 get logsize FM, simply by entering the name MSS_GET_LOGSIZE 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_GET_LOGSIZE 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_GET_LOGSIZE'"SQL Server transaction log size.
EXPORTING
DBNAME = "
IMPORTING
MSSDBLOGSIZE = "
IMPORTING Parameters details for MSS_GET_LOGSIZE
DBNAME -
Data type: MSSPROCINF-DBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MSS_GET_LOGSIZE
MSSDBLOGSIZE -
Data type: MSSDBLOGSZOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MSS_GET_LOGSIZE 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_dbname | TYPE MSSPROCINF-DBNAME, " | |||
| lv_mssdblogsize | TYPE MSSDBLOGSZ. " |
|   CALL FUNCTION 'MSS_GET_LOGSIZE' "SQL Server transaction log size |
| EXPORTING | ||
| DBNAME | = lv_dbname | |
| IMPORTING | ||
| MSSDBLOGSIZE | = lv_mssdblogsize | |
| . " MSS_GET_LOGSIZE | ||
ABAP code using 7.40 inline data declarations to call FM MSS_GET_LOGSIZE
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 DBNAME FROM MSSPROCINF INTO @DATA(ld_dbname). | ||||
Search for further information about these or an SAP related objects