SAP CUOB_GET_OBJECT Function Module for









CUOB_GET_OBJECT is a standard cuob get object 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 cuob get object FM, simply by entering the name CUOB_GET_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function CUOB_GET_OBJECT 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 'CUOB_GET_OBJECT'"
EXPORTING
OBJECT_NUMBER = "Internal object number

IMPORTING
CLASS_NR = "Internal class no. of object to be configured
PROFILE = "Int. no. of configuration profile used
INOB_OBJECT = "
CLASS_TYPE = "Class type
OBJECT_ID = "Object key
ROOT = "Object key of the object to be configured
ROOT_ID = "Table of the object to be configured
STATUS = "Status of allocation
TABLE = "Table
ROOT_INSTANCE = "
PARENT_INSTANCE = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for CUOB_GET_OBJECT

OBJECT_NUMBER - Internal object number

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

EXPORTING Parameters details for CUOB_GET_OBJECT

CLASS_NR - Internal class no. of object to be configured

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

PROFILE - Int. no. of configuration profile used

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

INOB_OBJECT -

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

CLASS_TYPE - Class type

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

OBJECT_ID - Object key

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

ROOT - Object key of the object to be configured

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

ROOT_ID - Table of the object to be configured

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

STATUS - Status of allocation

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

TABLE - Table

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

ROOT_INSTANCE -

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

PARENT_INSTANCE -

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

EXCEPTIONS details

NOT_FOUND - Object number not found

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

Copy and paste ABAP code example for CUOB_GET_OBJECT 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_class_nr  TYPE KSSK-CLINT, "   
lv_not_found  TYPE KSSK, "   
lv_object_number  TYPE INOB-CUOBJ, "   
lv_profile  TYPE INOB-CUCOZHL, "   
lv_inob_object  TYPE INOB, "   
lv_class_type  TYPE TCLA-KLART, "   
lv_object_id  TYPE KSSK-OBJEK, "   
lv_root  TYPE KSSK-OBJEK, "   
lv_root_id  TYPE TCLA-OBTAB, "   
lv_status  TYPE KSSK-STATU, "   
lv_table  TYPE TCLA-OBTAB, "   
lv_root_instance  TYPE INOB-ROOT, "   
lv_parent_instance  TYPE INOB-PARENT. "   

  CALL FUNCTION 'CUOB_GET_OBJECT'  "
    EXPORTING
         OBJECT_NUMBER = lv_object_number
    IMPORTING
         CLASS_NR = lv_class_nr
         PROFILE = lv_profile
         INOB_OBJECT = lv_inob_object
         CLASS_TYPE = lv_class_type
         OBJECT_ID = lv_object_id
         ROOT = lv_root
         ROOT_ID = lv_root_id
         STATUS = lv_status
         TABLE = lv_table
         ROOT_INSTANCE = lv_root_instance
         PARENT_INSTANCE = lv_parent_instance
    EXCEPTIONS
        NOT_FOUND = 1
. " CUOB_GET_OBJECT




ABAP code using 7.40 inline data declarations to call FM CUOB_GET_OBJECT

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 CLINT FROM KSSK INTO @DATA(ld_class_nr).
 
 
"SELECT single CUOBJ FROM INOB INTO @DATA(ld_object_number).
 
"SELECT single CUCOZHL FROM INOB INTO @DATA(ld_profile).
 
 
"SELECT single KLART FROM TCLA INTO @DATA(ld_class_type).
 
"SELECT single OBJEK FROM KSSK INTO @DATA(ld_object_id).
 
"SELECT single OBJEK FROM KSSK INTO @DATA(ld_root).
 
"SELECT single OBTAB FROM TCLA INTO @DATA(ld_root_id).
 
"SELECT single STATU FROM KSSK INTO @DATA(ld_status).
 
"SELECT single OBTAB FROM TCLA INTO @DATA(ld_table).
 
"SELECT single ROOT FROM INOB INTO @DATA(ld_root_instance).
 
"SELECT single PARENT FROM INOB INTO @DATA(ld_parent_instance).
 


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!