SAP NF_CHANGE_KEYDATE Function Module for Change Selection Date









NF_CHANGE_KEYDATE is a standard nf change keydate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Selection Date 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 nf change keydate FM, simply by entering the name NF_CHANGE_KEYDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function NF_CHANGE_KEYDATE 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 'NF_CHANGE_KEYDATE'"Change Selection Date
IMPORTING
CHANGED = "

CHANGING
SEL_DATE = "
.



EXPORTING Parameters details for NF_CHANGE_KEYDATE

CHANGED -

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

CHANGING Parameters details for NF_CHANGE_KEYDATE

SEL_DATE -

Data type: SY-DATUM
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for NF_CHANGE_KEYDATE 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_changed  TYPE FLAG, "   
lv_sel_date  TYPE SY-DATUM. "   

  CALL FUNCTION 'NF_CHANGE_KEYDATE'  "Change Selection Date
    IMPORTING
         CHANGED = lv_changed
    CHANGING
         SEL_DATE = lv_sel_date
. " NF_CHANGE_KEYDATE




ABAP code using 7.40 inline data declarations to call FM NF_CHANGE_KEYDATE

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 DATUM FROM SY INTO @DATA(ld_sel_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!