SAP TSTR_PERIODS_WEEKS Function Module for Generate Time Stream for Weeks (first day of the week is Monday)
TSTR_PERIODS_WEEKS is a standard tstr periods weeks SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate Time Stream for Weeks (first day of the week is Monday) 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 tstr periods weeks FM, simply by entering the name TSTR_PERIODS_WEEKS into the relevant SAP transaction such as SE37 or SE38.
Function Group: STS2
Program Name: SAPLSTS2
Main Program: SAPLSTS2
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TSTR_PERIODS_WEEKS 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 'TSTR_PERIODS_WEEKS'"Generate Time Stream for Weeks (first day of the week is Monday).
EXPORTING
IT_YEARTAB = "
IS_TTSTR = "
IMPORTING
ET_GENSEGTAB = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for TSTR_PERIODS_WEEKS
IT_YEARTAB -
Data type: TSTR_YEARTABOptional: No
Call by Reference: Yes
IS_TTSTR -
Data type: TTSTROptional: No
Call by Reference: Yes
EXPORTING Parameters details for TSTR_PERIODS_WEEKS
ET_GENSEGTAB -
Data type: TSTR_GENSEGYEARTABOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TSTR_PERIODS_WEEKS 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_error | TYPE STRING, " | |||
| lv_it_yeartab | TYPE TSTR_YEARTAB, " | |||
| lv_et_gensegtab | TYPE TSTR_GENSEGYEARTAB, " | |||
| lv_is_ttstr | TYPE TTSTR. " |
|   CALL FUNCTION 'TSTR_PERIODS_WEEKS' "Generate Time Stream for Weeks (first day of the week is Monday) |
| EXPORTING | ||
| IT_YEARTAB | = lv_it_yeartab | |
| IS_TTSTR | = lv_is_ttstr | |
| IMPORTING | ||
| ET_GENSEGTAB | = lv_et_gensegtab | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " TSTR_PERIODS_WEEKS | ||
ABAP code using 7.40 inline data declarations to call FM TSTR_PERIODS_WEEKS
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.Search for further information about these or an SAP related objects