SAP SD_CD_TIMEVAKEAKT_TO_XKONDAT Function Module for NOTRANSL: Change documents: Periods from time_vake_akt to xkondat and ykon









SD_CD_TIMEVAKEAKT_TO_XKONDAT is a standard sd cd timevakeakt to xkondat 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: Change documents: Periods from time_vake_akt to xkondat and ykon 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 sd cd timevakeakt to xkondat FM, simply by entering the name SD_CD_TIMEVAKEAKT_TO_XKONDAT into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_CD_TIMEVAKEAKT_TO_XKONDAT 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 'SD_CD_TIMEVAKEAKT_TO_XKONDAT'"NOTRANSL: Change documents: Periods from time_vake_akt to xkondat and ykon
EXPORTING
I_XVAKE = "
I_KNUMH = "

TABLES
DB_XKONDAT = "
DB_YKONDAT = "
TIMETAB = "
.



IMPORTING Parameters details for SD_CD_TIMEVAKEAKT_TO_XKONDAT

I_XVAKE -

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

I_KNUMH -

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

TABLES Parameters details for SD_CD_TIMEVAKEAKT_TO_XKONDAT

DB_XKONDAT -

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

DB_YKONDAT -

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

TIMETAB -

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

Copy and paste ABAP code example for SD_CD_TIMEVAKEAKT_TO_XKONDAT 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_i_xvake  TYPE VAKEVB, "   
lt_db_xkondat  TYPE STANDARD TABLE OF VKONDAT, "   
lv_i_knumh  TYPE VAKE-KNUMH, "   
lt_db_ykondat  TYPE STANDARD TABLE OF VKONDAT, "   
lt_timetab  TYPE STANDARD TABLE OF VKONDAT. "   

  CALL FUNCTION 'SD_CD_TIMEVAKEAKT_TO_XKONDAT'  "NOTRANSL: Change documents: Periods from time_vake_akt to xkondat and ykon
    EXPORTING
         I_XVAKE = lv_i_xvake
         I_KNUMH = lv_i_knumh
    TABLES
         DB_XKONDAT = lt_db_xkondat
         DB_YKONDAT = lt_db_ykondat
         TIMETAB = lt_timetab
. " SD_CD_TIMEVAKEAKT_TO_XKONDAT




ABAP code using 7.40 inline data declarations to call FM SD_CD_TIMEVAKEAKT_TO_XKONDAT

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 KNUMH FROM VAKE INTO @DATA(ld_i_knumh).
 
 
 


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!