SAP V45CU_CONFIG_HAS_CHANGES Function Module for NOTRANSL: Änderungsaussagen zu einer Konfiguration









V45CU_CONFIG_HAS_CHANGES is a standard v45cu config has changes 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: Änderungsaussagen zu einer Konfiguration 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 v45cu config has changes FM, simply by entering the name V45CU_CONFIG_HAS_CHANGES into the relevant SAP transaction such as SE37 or SE38.

Function Group: V45CU
Program Name: SAPLV45CU
Main Program: SAPLV45CU
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function V45CU_CONFIG_HAS_CHANGES 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 'V45CU_CONFIG_HAS_CHANGES'"NOTRANSL: Änderungsaussagen zu einer Konfiguration
EXPORTING
IV_INSTANCE = "Configuration (internal object number)

TABLES
* ET_INSTANCES_CHANGED = "
.



IMPORTING Parameters details for V45CU_CONFIG_HAS_CHANGES

IV_INSTANCE - Configuration (internal object number)

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

TABLES Parameters details for V45CU_CONFIG_HAS_CHANGES

ET_INSTANCES_CHANGED -

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

Copy and paste ABAP code example for V45CU_CONFIG_HAS_CHANGES 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_iv_instance  TYPE INOB-CUOBJ, "   
lt_et_instances_changed  TYPE STANDARD TABLE OF INOB. "   

  CALL FUNCTION 'V45CU_CONFIG_HAS_CHANGES'  "NOTRANSL: Änderungsaussagen zu einer Konfiguration
    EXPORTING
         IV_INSTANCE = lv_iv_instance
    TABLES
         ET_INSTANCES_CHANGED = lt_et_instances_changed
. " V45CU_CONFIG_HAS_CHANGES




ABAP code using 7.40 inline data declarations to call FM V45CU_CONFIG_HAS_CHANGES

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 CUOBJ FROM INOB INTO @DATA(ld_iv_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!