SAP ISU_DB_TE417_SELECT_PERIOD Function Module for INTERNAL: Read TE417 via Date / Billing Transaction to Determine Period
ISU_DB_TE417_SELECT_PERIOD is a standard isu db te417 select period SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Read TE417 via Date / Billing Transaction to Determine Period 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 isu db te417 select period FM, simply by entering the name ISU_DB_TE417_SELECT_PERIOD into the relevant SAP transaction such as SE37 or SE38.
Function Group: EE15
Program Name: SAPLEE15
Main Program: SAPLEE15
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_TE417_SELECT_PERIOD 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 'ISU_DB_TE417_SELECT_PERIOD'"INTERNAL: Read TE417 via Date / Billing Transaction to Determine Period.
EXPORTING
X_TERMSCHL = "Term Key
X_DATUM = "Date
X_ABRVORG = "Billing Transaction
* X_MAXCOUNT = 0 "
* X_SORT = "Sorting ('K' = Key, ' ' = No Sorting)
IMPORTING
Y_TE417 = "Firtst entry found
Y_COUNT = "Number
Y_OVERFLOW = "Overflow
TABLES
* T_TE417 = "
EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2 NOT_QUALIFIED = 3
IMPORTING Parameters details for ISU_DB_TE417_SELECT_PERIOD
X_TERMSCHL - Term Key
Data type: TE417-TERMSCHLOptional: No
Call by Reference: No ( called with pass by value option)
X_DATUM - Date
Data type: TE417-TERMTDATOptional: No
Call by Reference: No ( called with pass by value option)
X_ABRVORG - Billing Transaction
Data type: TE417-ABRVORGOptional: No
Call by Reference: No ( called with pass by value option)
X_MAXCOUNT -
Data type: REGEN-MAXCOUNTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_SORT - Sorting ('K' = Key, SPACE = No Sorting)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_DB_TE417_SELECT_PERIOD
Y_TE417 - Firtst entry found
Data type: TE417Optional: No
Call by Reference: No ( called with pass by value option)
Y_COUNT - Number
Data type: REGEN-MAXCOUNTOptional: No
Call by Reference: No ( called with pass by value option)
Y_OVERFLOW - Overflow
Data type: REGEN-OVERFLOWOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_DB_TE417_SELECT_PERIOD
T_TE417 -
Data type: TE417Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No Object Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_ERROR - Other Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_QUALIFIED - Input Parameters Are not Qualified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DB_TE417_SELECT_PERIOD 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: | ||||
| lt_t_te417 | TYPE STANDARD TABLE OF TE417, " | |||
| lv_y_te417 | TYPE TE417, " | |||
| lv_not_found | TYPE TE417, " | |||
| lv_x_termschl | TYPE TE417-TERMSCHL, " | |||
| lv_x_datum | TYPE TE417-TERMTDAT, " | |||
| lv_y_count | TYPE REGEN-MAXCOUNT, " | |||
| lv_system_error | TYPE REGEN, " | |||
| lv_x_abrvorg | TYPE TE417-ABRVORG, " | |||
| lv_y_overflow | TYPE REGEN-OVERFLOW, " | |||
| lv_not_qualified | TYPE REGEN, " | |||
| lv_x_maxcount | TYPE REGEN-MAXCOUNT, " 0 | |||
| lv_x_sort | TYPE REGEN. " |
|   CALL FUNCTION 'ISU_DB_TE417_SELECT_PERIOD' "INTERNAL: Read TE417 via Date / Billing Transaction to Determine Period |
| EXPORTING | ||
| X_TERMSCHL | = lv_x_termschl | |
| X_DATUM | = lv_x_datum | |
| X_ABRVORG | = lv_x_abrvorg | |
| X_MAXCOUNT | = lv_x_maxcount | |
| X_SORT | = lv_x_sort | |
| IMPORTING | ||
| Y_TE417 | = lv_y_te417 | |
| Y_COUNT | = lv_y_count | |
| Y_OVERFLOW | = lv_y_overflow | |
| TABLES | ||
| T_TE417 | = lt_t_te417 | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| SYSTEM_ERROR = 2 | ||
| NOT_QUALIFIED = 3 | ||
| . " ISU_DB_TE417_SELECT_PERIOD | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_TE417_SELECT_PERIOD
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 TERMSCHL FROM TE417 INTO @DATA(ld_x_termschl). | ||||
| "SELECT single TERMTDAT FROM TE417 INTO @DATA(ld_x_datum). | ||||
| "SELECT single MAXCOUNT FROM REGEN INTO @DATA(ld_y_count). | ||||
| "SELECT single ABRVORG FROM TE417 INTO @DATA(ld_x_abrvorg). | ||||
| "SELECT single OVERFLOW FROM REGEN INTO @DATA(ld_y_overflow). | ||||
| "SELECT single MAXCOUNT FROM REGEN INTO @DATA(ld_x_maxcount). | ||||
Search for further information about these or an SAP related objects