SAP IBRT_CONFIGURATION_DATE Function Module for DE-EN-LANG-SWITCH-NO-TRANSLATION
IBRT_CONFIGURATION_DATE is a standard ibrt configuration date SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DE-EN-LANG-SWITCH-NO-TRANSLATION 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 ibrt configuration date FM, simply by entering the name IBRT_CONFIGURATION_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBRT_CORE
Program Name: SAPLIBRT_CORE
Main Program: SAPLIBRT_CORE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IBRT_CONFIGURATION_DATE 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 'IBRT_CONFIGURATION_DATE'"DE-EN-LANG-SWITCH-NO-TRANSLATION.
EXPORTING
I_INSTANCE = "Configuration (Internal Object Number)
* IS_OBSERVER = "CUIB: Business Object
* IV_MOMENT = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
IMPORTING
E_CFG_DATE = "Valid-From Date
EXCEPTIONS
INVALID_INSTANCE = 1
IMPORTING Parameters details for IBRT_CONFIGURATION_DATE
I_INSTANCE - Configuration (Internal Object Number)
Data type: CUIB_CUOBJOptional: No
Call by Reference: Yes
IS_OBSERVER - CUIB: Business Object
Data type: CUIB_BUSINESS_OBJECTOptional: Yes
Call by Reference: Yes
IV_MOMENT - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: TIMESTAMPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for IBRT_CONFIGURATION_DATE
E_CFG_DATE - Valid-From Date
Data type: CABN-DATUVOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INSTANCE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IBRT_CONFIGURATION_DATE 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_e_cfg_date | TYPE CABN-DATUV, " | |||
| lv_i_instance | TYPE CUIB_CUOBJ, " | |||
| lv_invalid_instance | TYPE CUIB_CUOBJ, " | |||
| lv_is_observer | TYPE CUIB_BUSINESS_OBJECT, " | |||
| lv_iv_moment | TYPE TIMESTAMP. " |
|   CALL FUNCTION 'IBRT_CONFIGURATION_DATE' "DE-EN-LANG-SWITCH-NO-TRANSLATION |
| EXPORTING | ||
| I_INSTANCE | = lv_i_instance | |
| IS_OBSERVER | = lv_is_observer | |
| IV_MOMENT | = lv_iv_moment | |
| IMPORTING | ||
| E_CFG_DATE | = lv_e_cfg_date | |
| EXCEPTIONS | ||
| INVALID_INSTANCE = 1 | ||
| . " IBRT_CONFIGURATION_DATE | ||
ABAP code using 7.40 inline data declarations to call FM IBRT_CONFIGURATION_DATE
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 DATUV FROM CABN INTO @DATA(ld_e_cfg_date). | ||||
Search for further information about these or an SAP related objects