SAP OXT_GET_TOOLSTATE Function Module for Get State of OXT Tool

Search SAP Function Modules

OXT_GET_TOOLSTATE is a standard oxt get toolstate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get State of OXT Tool 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 oxt get toolstate FM, simply by entering the name OXT_GET_TOOLSTATE into the relevant SAP transaction such as SE37 or SE38.

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

Function OXT_GET_TOOLSTATE 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 'OXT_GET_TOOLSTATE'"Get State of OXT Tool
 IMPORTING
   ER_TOOL_STATE =  "Object Extension Tool - State
   EV_OPERATION =  "WB Request: Operation in the Development Environment
   EV_SEMANTIC_NAME =  "Text (80 Characters)

.

EXPORTING Parameters details for OXT_GET_TOOLSTATE

ER_TOOL_STATE - Object Extension Tool - State

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

EV_OPERATION - WB Request: Operation in the Development Environment

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

EV_SEMANTIC_NAME - Text (80 Characters)

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

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

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