SAP DDIF_STATE_GET Function Module for DD: Interface for Determining the Status of an ABAP Dictionary Object
DDIF_STATE_GET is a standard ddif state get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: Interface for Determining the Status of an ABAP Dictionary Object 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 ddif state get FM, simply by entering the name DDIF_STATE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDIF
Program Name: SAPLSDIF
Main Program: SAPLSDIF
Appliation area: S
Release date: 30-Apr-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DDIF_STATE_GET 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 'DDIF_STATE_GET'"DD: Interface for Determining the Status of an ABAP Dictionary Object.
EXPORTING
TYPE = "Type of the ABAP Dictionary Object
NAME = "Name of the ABAP Dictionary Object
* ID = "Additional Identification of the ABAP Dictionary Object
* STATE = 'M' "Read Status of the ABAP Dictionary Object
IMPORTING
GOTSTATE = "Status of the ABAP Dictionary Object
EXCEPTIONS
ILLEGAL_INPUT = 1
IMPORTING Parameters details for DDIF_STATE_GET
TYPE - Type of the ABAP Dictionary Object
Data type: DDOBJTYPOptional: No
Call by Reference: No ( called with pass by value option)
NAME - Name of the ABAP Dictionary Object
Data type: DDOBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
ID - Additional Identification of the ABAP Dictionary Object
Data type: DDOBJECTIDOptional: Yes
Call by Reference: No ( called with pass by value option)
STATE - Read Status of the ABAP Dictionary Object
Data type: DDOBJSTATEDefault: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DDIF_STATE_GET
GOTSTATE - Status of the ABAP Dictionary Object
Data type: DDGOTSTATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_INPUT - Value not Allowed for Parameter
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DDIF_STATE_GET 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_type | TYPE DDOBJTYP, " | |||
| lv_gotstate | TYPE DDGOTSTATE, " | |||
| lv_illegal_input | TYPE DDGOTSTATE, " | |||
| lv_name | TYPE DDOBJNAME, " | |||
| lv_id | TYPE DDOBJECTID, " | |||
| lv_state | TYPE DDOBJSTATE. " 'M' |
|   CALL FUNCTION 'DDIF_STATE_GET' "DD: Interface for Determining the Status of an ABAP Dictionary Object |
| EXPORTING | ||
| TYPE | = lv_type | |
| NAME | = lv_name | |
| ID | = lv_id | |
| STATE | = lv_state | |
| IMPORTING | ||
| GOTSTATE | = lv_gotstate | |
| EXCEPTIONS | ||
| ILLEGAL_INPUT = 1 | ||
| . " DDIF_STATE_GET | ||
ABAP code using 7.40 inline data declarations to call FM DDIF_STATE_GET
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.| DATA(ld_state) | = 'M'. | |||
Search for further information about these or an SAP related objects