SAP CU_SINGLE_DDB_HAS_OBJECT Function Module for Configuration general information during configuration

Search SAP Function Modules

CU_SINGLE_DDB_HAS_OBJECT is a standard cu single ddb has object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Configuration general information during configuration 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 cu single ddb has object FM, simply by entering the name CU_SINGLE_DDB_HAS_OBJECT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CU_SINGLE
Program Name: SAPLCU_SINGLE
Main Program: SAPLCU_SINGLE
Appliation area:
Release date: 10-Mar-2003
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CU_SINGLE_DDB_HAS_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 'CU_SINGLE_DDB_HAS_OBJECT'"Configuration general information during configuration
 IMPORTING
   EV_OBJECT =  "Key of Configurable Object
   EV_OBJECT_TYPE =  "Name of Database Table for Object
   EV_DATE =  "Date and Time, Current (Application Server) Date
   EV_INSTANCE =  "CUIB: System-Dependent Configuration Reference
   EV_OBJECT_INSTANCE =  "Instance Number Within DDB (Configuration)

EXCEPTIONS
   NOT_LOADED = 1 

.

EXPORTING Parameters details for CU_SINGLE_DDB_HAS_OBJECT

EV_OBJECT - Key of Configurable Object

Data type: CUCO-OBJEK
Optional: No
Call by Reference: Yes

EV_OBJECT_TYPE - Name of Database Table for Object

Data type: CUCO-OBTAB
Optional: No
Call by Reference: Yes

EV_DATE - Date and Time, Current (Application Server) Date

Data type: SYDATUM
Optional: No
Call by Reference: Yes

EV_INSTANCE - CUIB: System-Dependent Configuration Reference

Data type: CUIB_CUOBJ
Optional: No
Call by Reference: Yes

EV_OBJECT_INSTANCE - Instance Number Within DDB (Configuration)

Data type: CDDB-INSTANCE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_LOADED - No configuration activity

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CU_SINGLE_DDB_HAS_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.

ABAP code using 7.40 inline data declarations to call FM CU_SINGLE_DDB_HAS_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.

Search for further information about these or an SAP related objects