SAP CUCQ_CHECK_VALIDITY_DATE_SHIFT Function Module for NOTRANSL: Prüfen Datumsverschiebung für Konfigurationsprofile









CUCQ_CHECK_VALIDITY_DATE_SHIFT is a standard cucq check validity date shift 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: Prüfen Datumsverschiebung für Konfigurationsprofile 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 cucq check validity date shift FM, simply by entering the name CUCQ_CHECK_VALIDITY_DATE_SHIFT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CUCQ
Program Name: SAPLCUCQ
Main Program: SAPLCUCQ
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CUCQ_CHECK_VALIDITY_DATE_SHIFT 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 'CUCQ_CHECK_VALIDITY_DATE_SHIFT'"NOTRANSL: Prüfen Datumsverschiebung für Konfigurationsprofile
EXPORTING
CHANGE_NUMBER = "DE-EN-LANG-SWITCH-NO-TRANSLATION
NEW_DATE = "New Date
OLD_DATE = "Old Date

EXCEPTIONS
FOREIGN_LOCK = 1 OBJECT_NOT_FOUND = 2 SYSTEM_FAILURE = 3 NO_AUTHORITY_FOR_OBJECT = 4 INCONSISTENCY_OF_PROFILES = 5
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCUCQ_001 Additional Logic for Selection of Configuration Profiles in FG CUCQ

IMPORTING Parameters details for CUCQ_CHECK_VALIDITY_DATE_SHIFT

CHANGE_NUMBER - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NEW_DATE - New Date

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

OLD_DATE - Old Date

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

EXCEPTIONS details

FOREIGN_LOCK -

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

OBJECT_NOT_FOUND -

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

SYSTEM_FAILURE -

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

NO_AUTHORITY_FOR_OBJECT -

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

INCONSISTENCY_OF_PROFILES -

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

Copy and paste ABAP code example for CUCQ_CHECK_VALIDITY_DATE_SHIFT 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_foreign_lock  TYPE STRING, "   
lv_change_number  TYPE AENR-AENNR, "   
lv_new_date  TYPE AENR-DATUV, "   
lv_object_not_found  TYPE AENR, "   
lv_old_date  TYPE AENR-DATUV, "   
lv_system_failure  TYPE AENR, "   
lv_no_authority_for_object  TYPE AENR, "   
lv_inconsistency_of_profiles  TYPE AENR. "   

  CALL FUNCTION 'CUCQ_CHECK_VALIDITY_DATE_SHIFT'  "NOTRANSL: Prüfen Datumsverschiebung für Konfigurationsprofile
    EXPORTING
         CHANGE_NUMBER = lv_change_number
         NEW_DATE = lv_new_date
         OLD_DATE = lv_old_date
    EXCEPTIONS
        FOREIGN_LOCK = 1
        OBJECT_NOT_FOUND = 2
        SYSTEM_FAILURE = 3
        NO_AUTHORITY_FOR_OBJECT = 4
        INCONSISTENCY_OF_PROFILES = 5
. " CUCQ_CHECK_VALIDITY_DATE_SHIFT




ABAP code using 7.40 inline data declarations to call FM CUCQ_CHECK_VALIDITY_DATE_SHIFT

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 AENNR FROM AENR INTO @DATA(ld_change_number).
 
"SELECT single DATUV FROM AENR INTO @DATA(ld_new_date).
 
 
"SELECT single DATUV FROM AENR INTO @DATA(ld_old_date).
 
 
 
 


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!