SAP CUCB_CONFIG_EFFECTIVITY Function Module for NOTRANSL: Konfigurationsdatum bestimmen

Search SAP Function Modules

CUCB_CONFIG_EFFECTIVITY is a standard cucb config effectivity 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: Konfigurationsdatum bestimmen 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 cucb config effectivity FM, simply by entering the name CUCB_CONFIG_EFFECTIVITY into the relevant SAP transaction such as SE37 or SE38.

Function Group: CUCB
Program Name: SAPLCUCB
Main Program: SAPLCUCB
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUCB_CONFIG_EFFECTIVITY 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 'CUCB_CONFIG_EFFECTIVITY'"NOTRANSL: Konfigurationsdatum bestimmen
  EXPORTING
   INSTANCE =  "CUIB: System-Dependent Configuration Reference
*  IV_MOMENT =  "IB: Time Stamp of Owner's or Observer's Version

 IMPORTING
   EFFECTIVITY =  "Validity

EXCEPTIONS
   INVALID_INSTANCE = 1    NO_OWNER_FOUND = 2    INSTANCE_IS_A_CLASSIFICATION = 3 

.

IMPORTING Parameters details for CUCB_CONFIG_EFFECTIVITY

INSTANCE - CUIB: System-Dependent Configuration Reference

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

IV_MOMENT - IB: Time Stamp of Owner's or Observer's Version

Data type: TIMESTAMP
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CUCB_CONFIG_EFFECTIVITY

EFFECTIVITY - Validity

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

EXCEPTIONS details

INVALID_INSTANCE -

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

NO_OWNER_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INSTANCE_IS_A_CLASSIFICATION -

Data type:
Optional: No
Call by Reference: Yes

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

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