SAP CB_OBJ_INITIALIZE Function Module for









CB_OBJ_INITIALIZE is a standard cb obj initialize 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 cb obj initialize FM, simply by entering the name CB_OBJ_INITIALIZE into the relevant SAP transaction such as SE37 or SE38.

Function Group: OM_INTERFACE_TEMPLATES
Program Name: SAPLOM_INTERFACE_TEMPLATES
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CB_OBJ_INITIALIZE 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 'CB_OBJ_INITIALIZE'"
  EXPORTING
   SCENARIO =  "OM: Object Manager Scenario
   PLANVERSION =  "
   TRANSACTION_START =  "
   CHANGEMODE =  "
   TIMEDEPENDENT =  "
   USER_SETTINGS_EXIST =  "

 IMPORTING
   DATA_VALID =  "

CHANGING
   LPNODE =  "OM: Description of Node in Search Tree
   SEARCHTOOL =  "Class Name
   SHOW_LAUNCHPAD =  "General Flag

TABLES
   SEARCH_CRITERIA =  "Org. Management: Table of search attributes (name, value)
   ST_OBJECTS =  "Org. Management: Table of Object Entries
   ST_STRUCTURE =  "Org. Management: Table of Structure Entries
.



IMPORTING Parameters details for CB_OBJ_INITIALIZE

SCENARIO - OM: Object Manager Scenario

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

PLANVERSION -

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

TRANSACTION_START -

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

CHANGEMODE -

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

TIMEDEPENDENT -

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

USER_SETTINGS_EXIST -

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

EXPORTING Parameters details for CB_OBJ_INITIALIZE

DATA_VALID -

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

CHANGING Parameters details for CB_OBJ_INITIALIZE

LPNODE - OM: Description of Node in Search Tree

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

SEARCHTOOL - Class Name

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

SHOW_LAUNCHPAD - General Flag

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

TABLES Parameters details for CB_OBJ_INITIALIZE

SEARCH_CRITERIA - Org. Management: Table of search attributes (name, value)

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

ST_OBJECTS - Org. Management: Table of Object Entries

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

ST_STRUCTURE - Org. Management: Table of Structure Entries

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

Copy and paste ABAP code example for CB_OBJ_INITIALIZE 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_lpnode  TYPE OMSEANODE, "   
lv_scenario  TYPE OMOBJSCEN, "   
lv_data_valid  TYPE FLAG, "   
lt_search_criteria  TYPE STANDARD TABLE OF OMSEAATTAB, "   
lv_searchtool  TYPE SEOCLSNAME, "   
lt_st_objects  TYPE STANDARD TABLE OF OBJEC_T, "   
lv_planversion  TYPE PLVAR, "   
lt_st_structure  TYPE STANDARD TABLE OF STRUC_T, "   
lv_show_launchpad  TYPE FLAG, "   
lv_transaction_start  TYPE FLAG, "   
lv_changemode  TYPE OMACTMODE, "   
lv_timedependent  TYPE HROMTIMEFL, "   
lv_user_settings_exist  TYPE FLAG. "   

  CALL FUNCTION 'CB_OBJ_INITIALIZE'  "
    EXPORTING
         SCENARIO = lv_scenario
         PLANVERSION = lv_planversion
         TRANSACTION_START = lv_transaction_start
         CHANGEMODE = lv_changemode
         TIMEDEPENDENT = lv_timedependent
         USER_SETTINGS_EXIST = lv_user_settings_exist
    IMPORTING
         DATA_VALID = lv_data_valid
    CHANGING
         LPNODE = lv_lpnode
         SEARCHTOOL = lv_searchtool
         SHOW_LAUNCHPAD = lv_show_launchpad
    TABLES
         SEARCH_CRITERIA = lt_search_criteria
         ST_OBJECTS = lt_st_objects
         ST_STRUCTURE = lt_st_structure
. " CB_OBJ_INITIALIZE




ABAP code using 7.40 inline data declarations to call FM CB_OBJ_INITIALIZE

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



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!