SAP SWO_OBJECT_ID_GET Function Module for Read business object super object type
SWO_OBJECT_ID_GET is a standard swo object id 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 Read business object super object type 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 swo object id get FM, simply by entering the name SWO_OBJECT_ID_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWOR
Program Name: SAPLSWOR
Main Program: SAPLSWOR
Appliation area: S
Release date: 10-Aug-1995
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SWO_OBJECT_ID_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 'SWO_OBJECT_ID_GET'"Read business object super object type.
EXPORTING
OBJECT = "Runtime Object
IMPORTING
RETURN = "Return Value
OBJID = "
IMPORTING Parameters details for SWO_OBJECT_ID_GET
OBJECT - Runtime Object
Data type: SWOTRTIME-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SWO_OBJECT_ID_GET
RETURN - Return Value
Data type: SWOTRETURNOptional: No
Call by Reference: No ( called with pass by value option)
OBJID -
Data type: SWOTOBJIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWO_OBJECT_ID_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_object | TYPE SWOTRTIME-OBJECT, " | |||
| lv_return | TYPE SWOTRETURN, " | |||
| lv_objid | TYPE SWOTOBJID. " |
|   CALL FUNCTION 'SWO_OBJECT_ID_GET' "Read business object super object type |
| EXPORTING | ||
| OBJECT | = lv_object | |
| IMPORTING | ||
| RETURN | = lv_return | |
| OBJID | = lv_objid | |
| . " SWO_OBJECT_ID_GET | ||
ABAP code using 7.40 inline data declarations to call FM SWO_OBJECT_ID_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.| "SELECT single OBJECT FROM SWOTRTIME INTO @DATA(ld_object). | ||||
Search for further information about these or an SAP related objects