SAP GET_CONFIG_USED Function Module for

Search SAP Function Modules

GET_CONFIG_USED is a standard get config used 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 get config used FM, simply by entering the name GET_CONFIG_USED into the relevant SAP transaction such as SE37 or SE38.

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

Function GET_CONFIG_USED 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 'GET_CONFIG_USED'"
  EXPORTING
*  LOCAL_REMOTE = 'LOCAL' "Values are 'LOCAL' or 'REMOTE'
*  LOGICAL_DESTINATION =  "Logical RFC call destination

 IMPORTING
   F_CONFIG_USED_READ =  "Label: table read = YES - table not read = NO
   ACTIVEFLAG =  "
   INTERVAL =  "
   DETAILSCOLL =  "
   DETAILSREQI =  "
   DETAILSMODE =  "
   LASTCOLLWRT =  "
   LASTCOLLINT =  "
   NORMCOLLINT =  "

TABLES
   TF_CONFIG_USED =  "Table for used system configuration
*  TF_CONFIG_USED_CHR =  "

EXCEPTIONS
   INTERNAL_ERROR_ADRESS_FAILED = 1    COMMUNICATION_FAILURE = 10    INTERNAL_ERROR_DIFFERENT_FIELD = 2    INTERNAL_ERROR_NO_NEW_LINE = 3    COLLECTOR_NOT_RUNNING = 4    SHARED_MEMORY_NOT_AVAILABLE = 5    COLLECTOR_BUSY = 6    VERSION_CONFLICT = 7    NO_NETWORK_COLLECTOR_RUNNING = 8    SYSTEM_FAILURE = 9 

.

IMPORTING Parameters details for GET_CONFIG_USED

LOCAL_REMOTE - Values are 'LOCAL' or 'REMOTE'

Data type: DEF_PAR_FU-LOC_REMOTE
Default: 'LOCAL'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOGICAL_DESTINATION - Logical RFC call destination

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

EXPORTING Parameters details for GET_CONFIG_USED

F_CONFIG_USED_READ - Label: table read = YES - table not read = NO

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

ACTIVEFLAG -

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

INTERVAL -

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

DETAILSCOLL -

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

DETAILSREQI -

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

DETAILSMODE -

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

LASTCOLLWRT -

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

LASTCOLLINT -

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

NORMCOLLINT -

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

TABLES Parameters details for GET_CONFIG_USED

TF_CONFIG_USED - Table for used system configuration

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

TF_CONFIG_USED_CHR -

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

EXCEPTIONS details

INTERNAL_ERROR_ADRESS_FAILED - Wrong adress of shared Memory

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

COMMUNICATION_FAILURE - Remote host not reached

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

INTERNAL_ERROR_DIFFERENT_FIELD - Different field length of input parameter

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

INTERNAL_ERROR_NO_NEW_LINE - Append of internal table failed

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

COLLECTOR_NOT_RUNNING - 'SAPOSCOL' is not running on the host

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

SHARED_MEMORY_NOT_AVAILABLE - Shared memory is not available

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

COLLECTOR_BUSY - 'SAPOSCOL' writes to shared memory

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

VERSION_CONFLICT - Shared Memory Data are different from 'SAPOSCOL'

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

NO_NETWORK_COLLECTOR_RUNNING - No network collector (RMON-MIB) running

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

SYSTEM_FAILURE - System failure on the remote host

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

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

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