SAP DD_DBUT_OBJ_STATE Function Module for
DD_DBUT_OBJ_STATE is a standard dd dbut obj state 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 dd dbut obj state FM, simply by entering the name DD_DBUT_OBJ_STATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDDD
Program Name: SAPLSDDD
Main Program: SAPLSDDD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_DBUT_OBJ_STATE 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 'DD_DBUT_OBJ_STATE'".
EXPORTING
OBJNAME = "
* IDNAME = ' ' "
OBJTYPE = "
IMPORTING
REQUEST = "
REQUEST_AUTHOR = "
JOBNAME = "
JOBCOUNT = "
JOBSTATE = "
SCHEDULE_DATE = "
SCHEDULE_TIME = "
FCT = "
TABLES
* TEXT = "
IMPORTING Parameters details for DD_DBUT_OBJ_STATE
OBJNAME -
Data type: TBATG-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IDNAME -
Data type: DD12L-INDEXNAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJTYPE -
Data type: TBATG-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_DBUT_OBJ_STATE
REQUEST -
Data type: DDDBUTREFS-REQUESTOptional: No
Call by Reference: No ( called with pass by value option)
REQUEST_AUTHOR -
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
JOBNAME -
Data type: TBTCJOB-JOBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
JOBCOUNT -
Data type: TBTCJOB-JOBCOUNTOptional: No
Call by Reference: No ( called with pass by value option)
JOBSTATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SCHEDULE_DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
SCHEDULE_TIME -
Data type: SY-UZEITOptional: No
Call by Reference: No ( called with pass by value option)
FCT -
Data type: TBATG-FCTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DD_DBUT_OBJ_STATE
TEXT -
Data type: DDPRTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_DBUT_OBJ_STATE 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: | ||||
| lt_text | TYPE STANDARD TABLE OF DDPRTXT, " | |||
| lv_objname | TYPE TBATG-TABNAME, " | |||
| lv_request | TYPE DDDBUTREFS-REQUEST, " | |||
| lv_idname | TYPE DD12L-INDEXNAME, " SPACE | |||
| lv_request_author | TYPE SY-UNAME, " | |||
| lv_jobname | TYPE TBTCJOB-JOBNAME, " | |||
| lv_objtype | TYPE TBATG-OBJECT, " | |||
| lv_jobcount | TYPE TBTCJOB-JOBCOUNT, " | |||
| lv_jobstate | TYPE TBTCJOB, " | |||
| lv_schedule_date | TYPE SY-DATUM, " | |||
| lv_schedule_time | TYPE SY-UZEIT, " | |||
| lv_fct | TYPE TBATG-FCT. " |
|   CALL FUNCTION 'DD_DBUT_OBJ_STATE' " |
| EXPORTING | ||
| OBJNAME | = lv_objname | |
| IDNAME | = lv_idname | |
| OBJTYPE | = lv_objtype | |
| IMPORTING | ||
| REQUEST | = lv_request | |
| REQUEST_AUTHOR | = lv_request_author | |
| JOBNAME | = lv_jobname | |
| JOBCOUNT | = lv_jobcount | |
| JOBSTATE | = lv_jobstate | |
| SCHEDULE_DATE | = lv_schedule_date | |
| SCHEDULE_TIME | = lv_schedule_time | |
| FCT | = lv_fct | |
| TABLES | ||
| TEXT | = lt_text | |
| . " DD_DBUT_OBJ_STATE | ||
ABAP code using 7.40 inline data declarations to call FM DD_DBUT_OBJ_STATE
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 TABNAME FROM TBATG INTO @DATA(ld_objname). | ||||
| "SELECT single REQUEST FROM DDDBUTREFS INTO @DATA(ld_request). | ||||
| "SELECT single INDEXNAME FROM DD12L INTO @DATA(ld_idname). | ||||
| DATA(ld_idname) | = ' '. | |||
| "SELECT single UNAME FROM SY INTO @DATA(ld_request_author). | ||||
| "SELECT single JOBNAME FROM TBTCJOB INTO @DATA(ld_jobname). | ||||
| "SELECT single OBJECT FROM TBATG INTO @DATA(ld_objtype). | ||||
| "SELECT single JOBCOUNT FROM TBTCJOB INTO @DATA(ld_jobcount). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_schedule_date). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_schedule_time). | ||||
| "SELECT single FCT FROM TBATG INTO @DATA(ld_fct). | ||||
Search for further information about these or an SAP related objects