SAP LAW_ANALYZE_SYSTEM_DATA Function Module for









LAW_ANALYZE_SYSTEM_DATA is a standard law analyze system data 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 law analyze system data FM, simply by entering the name LAW_ANALYZE_SYSTEM_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function LAW_ANALYZE_SYSTEM_DATA 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 'LAW_ANALYZE_SYSTEM_DATA'"
 IMPORTING
   DATE =  "Date and Time, Current (Application Server) Date
   TIME =  "Date and Time, Current Application Server Time
   USER =  "SAP System, User Logon Name
   DATABASE =  "R/3 System, Name of Central Database System
   STATUS =  "Value for measurement data
   RELEASE =  "R/3 System, system release
   SYSTEM_NUMBER =  "Value for measurement data

TABLES
   TT_DATA =  "System Measurement Data
*  PRICELISTS =  "Price lists in the SAP System
.



EXPORTING Parameters details for LAW_ANALYZE_SYSTEM_DATA

DATE - Date and Time, Current (Application Server) Date

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

TIME - Date and Time, Current Application Server Time

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

USER - SAP System, User Logon Name

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

DATABASE - R/3 System, Name of Central Database System

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

STATUS - Value for measurement data

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

RELEASE - R/3 System, system release

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

SYSTEM_NUMBER - Value for measurement data

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

TABLES Parameters details for LAW_ANALYZE_SYSTEM_DATA

TT_DATA - System Measurement Data

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

PRICELISTS - Price lists in the SAP System

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

Copy and paste ABAP code example for LAW_ANALYZE_SYSTEM_DATA 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_date  TYPE SY-DATUM, "   
lt_tt_data  TYPE STANDARD TABLE OF SYMDA_LAW, "   
lv_time  TYPE SY-UZEIT, "   
lt_pricelists  TYPE STANDARD TABLE OF TUPL, "   
lv_user  TYPE SY-UNAME, "   
lv_database  TYPE SY-DBSYS, "   
lv_status  TYPE SYMDA_LAW-SYM_VAL_L, "   
lv_release  TYPE SY-SAPRL, "   
lv_system_number  TYPE SYMDA_LAW-SYM_VAL_L. "   

  CALL FUNCTION 'LAW_ANALYZE_SYSTEM_DATA'  "
    IMPORTING
         DATE = lv_date
         TIME = lv_time
         USER = lv_user
         DATABASE = lv_database
         STATUS = lv_status
         RELEASE = lv_release
         SYSTEM_NUMBER = lv_system_number
    TABLES
         TT_DATA = lt_tt_data
         PRICELISTS = lt_pricelists
. " LAW_ANALYZE_SYSTEM_DATA




ABAP code using 7.40 inline data declarations to call FM LAW_ANALYZE_SYSTEM_DATA

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 DATUM FROM SY INTO @DATA(ld_date).
 
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_time).
 
 
"SELECT single UNAME FROM SY INTO @DATA(ld_user).
 
"SELECT single DBSYS FROM SY INTO @DATA(ld_database).
 
"SELECT single SYM_VAL_L FROM SYMDA_LAW INTO @DATA(ld_status).
 
"SELECT single SAPRL FROM SY INTO @DATA(ld_release).
 
"SELECT single SYM_VAL_L FROM SYMDA_LAW INTO @DATA(ld_system_number).
 


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!