SAP SD_CONDITION_TIME_INTERVAL_GET Function Module for NOTRANSL: Alle Gültigkeitszeiträume zu einer Konditionsart
SD_CONDITION_TIME_INTERVAL_GET is a standard sd condition time interval get 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: Alle Gültigkeitszeiträume zu einer Konditionsart 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 condition time interval get FM, simply by entering the name SD_CONDITION_TIME_INTERVAL_GET 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_CONDITION_TIME_INTERVAL_GET 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_CONDITION_TIME_INTERVAL_GET'"NOTRANSL: Alle Gültigkeitszeiträume zu einer Konditionsart.
EXPORTING
* KOMG_I = "Communication block
* KOMK_I = "
* KOMP_I = "
DATVO_I = "Date from
DATBI_I = "Date to
* KVEWE_I = 'A' "Usage
* KAPPL_I = 'V ' "Application
* KOMK_KOMP_FIELDS_I = ' ' "
TABLES
PERIODS_TAB = "Dates with all changes
KSCHL_TAB = "Input table with condition types
EXCEPTIONS
NO_CONDITIONS = 1
IMPORTING Parameters details for SD_CONDITION_TIME_INTERVAL_GET
KOMG_I - Communication block
Data type: KOMGOptional: Yes
Call by Reference: No ( called with pass by value option)
KOMK_I -
Data type: KOMKOptional: Yes
Call by Reference: No ( called with pass by value option)
KOMP_I -
Data type: KOMPOptional: Yes
Call by Reference: No ( called with pass by value option)
DATVO_I - Date from
Data type: A000-DATABOptional: No
Call by Reference: No ( called with pass by value option)
DATBI_I - Date to
Data type: A000-DATBIOptional: No
Call by Reference: No ( called with pass by value option)
KVEWE_I - Usage
Data type: T681V-KVEWEDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
KAPPL_I - Application
Data type: T681A-KAPPLDefault: 'V '
Optional: Yes
Call by Reference: No ( called with pass by value option)
KOMK_KOMP_FIELDS_I -
Data type: SY-MARKYDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SD_CONDITION_TIME_INTERVAL_GET
PERIODS_TAB - Dates with all changes
Data type: WPPERIODOptional: No
Call by Reference: No ( called with pass by value option)
KSCHL_TAB - Input table with condition types
Data type: WPKSCHLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CONDITIONS - No Conditions Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_CONDITION_TIME_INTERVAL_GET 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_komg_i | TYPE KOMG, " | |||
| lt_periods_tab | TYPE STANDARD TABLE OF WPPERIOD, " | |||
| lv_no_conditions | TYPE WPPERIOD, " | |||
| lv_komk_i | TYPE KOMK, " | |||
| lt_kschl_tab | TYPE STANDARD TABLE OF WPKSCHL, " | |||
| lv_komp_i | TYPE KOMP, " | |||
| lv_datvo_i | TYPE A000-DATAB, " | |||
| lv_datbi_i | TYPE A000-DATBI, " | |||
| lv_kvewe_i | TYPE T681V-KVEWE, " 'A' | |||
| lv_kappl_i | TYPE T681A-KAPPL, " 'V ' | |||
| lv_komk_komp_fields_i | TYPE SY-MARKY. " ' ' |
|   CALL FUNCTION 'SD_CONDITION_TIME_INTERVAL_GET' "NOTRANSL: Alle Gültigkeitszeiträume zu einer Konditionsart |
| EXPORTING | ||
| KOMG_I | = lv_komg_i | |
| KOMK_I | = lv_komk_i | |
| KOMP_I | = lv_komp_i | |
| DATVO_I | = lv_datvo_i | |
| DATBI_I | = lv_datbi_i | |
| KVEWE_I | = lv_kvewe_i | |
| KAPPL_I | = lv_kappl_i | |
| KOMK_KOMP_FIELDS_I | = lv_komk_komp_fields_i | |
| TABLES | ||
| PERIODS_TAB | = lt_periods_tab | |
| KSCHL_TAB | = lt_kschl_tab | |
| EXCEPTIONS | ||
| NO_CONDITIONS = 1 | ||
| . " SD_CONDITION_TIME_INTERVAL_GET | ||
ABAP code using 7.40 inline data declarations to call FM SD_CONDITION_TIME_INTERVAL_GET
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 DATAB FROM A000 INTO @DATA(ld_datvo_i). | ||||
| "SELECT single DATBI FROM A000 INTO @DATA(ld_datbi_i). | ||||
| "SELECT single KVEWE FROM T681V INTO @DATA(ld_kvewe_i). | ||||
| DATA(ld_kvewe_i) | = 'A'. | |||
| "SELECT single KAPPL FROM T681A INTO @DATA(ld_kappl_i). | ||||
| DATA(ld_kappl_i) | = 'V '. | |||
| "SELECT single MARKY FROM SY INTO @DATA(ld_komk_komp_fields_i). | ||||
| DATA(ld_komk_komp_fields_i) | = ' '. | |||
Search for further information about these or an SAP related objects