SAP TYPD_GET_STATE_FOR_SE11 Function Module for









TYPD_GET_STATE_FOR_SE11 is a standard typd get state for se11 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 typd get state for se11 FM, simply by entering the name TYPD_GET_STATE_FOR_SE11 into the relevant SAP transaction such as SE37 or SE38.

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



Function TYPD_GET_STATE_FOR_SE11 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 'TYPD_GET_STATE_FOR_SE11'"
EXPORTING
TYPDNAME = "

IMPORTING
STATE = "

EXCEPTIONS
REPS_NOT_EXIST = 1
.



IMPORTING Parameters details for TYPD_GET_STATE_FOR_SE11

TYPDNAME -

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

EXPORTING Parameters details for TYPD_GET_STATE_FOR_SE11

STATE -

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

EXCEPTIONS details

REPS_NOT_EXIST -

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

Copy and paste ABAP code example for TYPD_GET_STATE_FOR_SE11 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_state  TYPE DDOBJSTATE, "   
lv_typdname  TYPE RSEDD0-TYPEGROUP, "   
lv_reps_not_exist  TYPE RSEDD0. "   

  CALL FUNCTION 'TYPD_GET_STATE_FOR_SE11'  "
    EXPORTING
         TYPDNAME = lv_typdname
    IMPORTING
         STATE = lv_state
    EXCEPTIONS
        REPS_NOT_EXIST = 1
. " TYPD_GET_STATE_FOR_SE11




ABAP code using 7.40 inline data declarations to call FM TYPD_GET_STATE_FOR_SE11

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 TYPEGROUP FROM RSEDD0 INTO @DATA(ld_typdname).
 
 


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!