SAP TEST_PERIODENGRENZE Function Module for
TEST_PERIODENGRENZE is a standard test periodengrenze SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 test periodengrenze FM, simply by entering the name TEST_PERIODENGRENZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RKMA
Program Name: SAPLRKMA
Main Program: SAPLRKMA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEST_PERIODENGRENZE 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 'TEST_PERIODENGRENZE'".
EXPORTING
DATAB = "Lower Interval Limit
DATBI = "Upper Range Limit
PERIV = "Version of the period determinatio
IMPORTING
FDATUM = "first calendar day
LDATUM = "last calendar day
PGRENZE = "
EXCEPTIONS
T009_NOTFOUND = 1 T009B_NOTFOUND = 2
IMPORTING Parameters details for TEST_PERIODENGRENZE
DATAB - Lower Interval Limit
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
DATBI - Upper Range Limit
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
PERIV - Version of the period determinatio
Data type: T009-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TEST_PERIODENGRENZE
FDATUM - first calendar day
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
LDATUM - last calendar day
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
PGRENZE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
T009_NOTFOUND - Entry does not exist in table T009
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
T009B_NOTFOUND - Entry does not exist in table T009
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TEST_PERIODENGRENZE 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_datab | TYPE SY-DATUM, " | |||
| lv_fdatum | TYPE SY-DATUM, " | |||
| lv_t009_notfound | TYPE SY, " | |||
| lv_datbi | TYPE SY-DATUM, " | |||
| lv_ldatum | TYPE SY-DATUM, " | |||
| lv_t009b_notfound | TYPE SY, " | |||
| lv_periv | TYPE T009-PERIV, " | |||
| lv_pgrenze | TYPE T009. " |
|   CALL FUNCTION 'TEST_PERIODENGRENZE' " |
| EXPORTING | ||
| DATAB | = lv_datab | |
| DATBI | = lv_datbi | |
| PERIV | = lv_periv | |
| IMPORTING | ||
| FDATUM | = lv_fdatum | |
| LDATUM | = lv_ldatum | |
| PGRENZE | = lv_pgrenze | |
| EXCEPTIONS | ||
| T009_NOTFOUND = 1 | ||
| T009B_NOTFOUND = 2 | ||
| . " TEST_PERIODENGRENZE | ||
ABAP code using 7.40 inline data declarations to call FM TEST_PERIODENGRENZE
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_datab). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_fdatum). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_datbi). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_ldatum). | ||||
| "SELECT single PERIV FROM T009 INTO @DATA(ld_periv). | ||||
Search for further information about these or an SAP related objects