SAP EHSB_ST01_OBJ_STATUS_CHANGE Function Module for NOTRANSL: EHS-BAS: Statuswechsel eines Objektes (Nr) durchführen
EHSB_ST01_OBJ_STATUS_CHANGE is a standard ehsb st01 obj status change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EHS-BAS: Statuswechsel eines Objektes (Nr) durchführen 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 ehsb st01 obj status change FM, simply by entering the name EHSB_ST01_OBJ_STATUS_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHSB_ST01
Program Name: SAPLEHSB_ST01
Main Program: SAPLEHSB_ST01
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHSB_ST01_OBJ_STATUS_CHANGE 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 'EHSB_ST01_OBJ_STATUS_CHANGE'"NOTRANSL: EHS-BAS: Statuswechsel eines Objektes (Nr) durchführen.
EXPORTING
I_OBJCAT = "
I_OBJNR = "Object Number
* I_CURR_STATUS = "Active Status
* I_NEXT_STATUS = "Status To Be Set
IMPORTING
E_NEXT_STATUS = "
EXCEPTIONS
LAST_STATUS = 1 OBJECT_NOT_FOUND = 2 NEXT_STATUS_INVALID = 3 CURR_STATUS_INVALID = 4 STATUS_CHANGE_FAILED = 5
IMPORTING Parameters details for EHSB_ST01_OBJ_STATUS_CHANGE
I_OBJCAT -
Data type: J_OBARTOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJNR - Object Number
Data type: J_OBJNROptional: No
Call by Reference: No ( called with pass by value option)
I_CURR_STATUS - Active Status
Data type: J_STATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NEXT_STATUS - Status To Be Set
Data type: J_STATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EHSB_ST01_OBJ_STATUS_CHANGE
E_NEXT_STATUS -
Data type: J_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LAST_STATUS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NEXT_STATUS_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CURR_STATUS_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STATUS_CHANGE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EHSB_ST01_OBJ_STATUS_CHANGE 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_i_objcat | TYPE J_OBART, " | |||
| lv_last_status | TYPE J_OBART, " | |||
| lv_e_next_status | TYPE J_STATUS, " | |||
| lv_i_objnr | TYPE J_OBJNR, " | |||
| lv_object_not_found | TYPE J_OBJNR, " | |||
| lv_i_curr_status | TYPE J_STATUS, " | |||
| lv_next_status_invalid | TYPE J_STATUS, " | |||
| lv_i_next_status | TYPE J_STATUS, " | |||
| lv_curr_status_invalid | TYPE J_STATUS, " | |||
| lv_status_change_failed | TYPE J_STATUS. " |
|   CALL FUNCTION 'EHSB_ST01_OBJ_STATUS_CHANGE' "NOTRANSL: EHS-BAS: Statuswechsel eines Objektes (Nr) durchführen |
| EXPORTING | ||
| I_OBJCAT | = lv_i_objcat | |
| I_OBJNR | = lv_i_objnr | |
| I_CURR_STATUS | = lv_i_curr_status | |
| I_NEXT_STATUS | = lv_i_next_status | |
| IMPORTING | ||
| E_NEXT_STATUS | = lv_e_next_status | |
| EXCEPTIONS | ||
| LAST_STATUS = 1 | ||
| OBJECT_NOT_FOUND = 2 | ||
| NEXT_STATUS_INVALID = 3 | ||
| CURR_STATUS_INVALID = 4 | ||
| STATUS_CHANGE_FAILED = 5 | ||
| . " EHSB_ST01_OBJ_STATUS_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM EHSB_ST01_OBJ_STATUS_CHANGE
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