SAP MC_PERIO_GET_FIRST_AND_LASTDAY Function Module for NOTRANSL: zu einer Periode mit Periodenkennzeichen den 1. und letzten Tag
MC_PERIO_GET_FIRST_AND_LASTDAY is a standard mc perio get first and lastday 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: zu einer Periode mit Periodenkennzeichen den 1. und letzten Tag 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 mc perio get first and lastday FM, simply by entering the name MC_PERIO_GET_FIRST_AND_LASTDAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCP2
Program Name: SAPLMCP2
Main Program: SAPLMCP2
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MC_PERIO_GET_FIRST_AND_LASTDAY 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 'MC_PERIO_GET_FIRST_AND_LASTDAY'"NOTRANSL: zu einer Periode mit Periodenkennzeichen den 1. und letzten Tag.
EXPORTING
* IFABKL = ' ' "Factory calendar key
* IWERKS = ' ' "Plant
IPERKZ = "Period Indicator
* IPERIV = ' ' "Fiscal Year Variant
IPERID = "Period: day, week, month, posting period as rep. internally
IMPORTING
EFIRSTDAY = "Date for public holiday and factory calendars
ELASTDAY = "Date for public holiday and factory calendars
EXCEPTIONS
PERID_INVALID = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLMCP2_008 User Exit: Processing Header Data in a Purchase Order from an IDoc
EXIT_SAPLMCP2_009 User Exit: Processing Item Data in a Purchase Order from an IDoc
IMPORTING Parameters details for MC_PERIO_GET_FIRST_AND_LASTDAY
IFABKL - Factory calendar key
Data type: T001W-FABKLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IWERKS - Plant
Data type: RMCP2-WERKSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IPERKZ - Period Indicator
Data type: PGABV-PERKZOptional: No
Call by Reference: No ( called with pass by value option)
IPERIV - Fiscal Year Variant
Data type: PGABV-PERIVDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IPERID - Period: day, week, month, posting period as rep. internally
Data type: PGABV-PERIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MC_PERIO_GET_FIRST_AND_LASTDAY
EFIRSTDAY - Date for public holiday and factory calendars
Data type: SCAL-DATEOptional: No
Call by Reference: No ( called with pass by value option)
ELASTDAY - Date for public holiday and factory calendars
Data type: SCAL-DATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PERID_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MC_PERIO_GET_FIRST_AND_LASTDAY 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_ifabkl | TYPE T001W-FABKL, " SPACE | |||
| lv_efirstday | TYPE SCAL-DATE, " | |||
| lv_perid_invalid | TYPE SCAL, " | |||
| lv_iwerks | TYPE RMCP2-WERKS, " SPACE | |||
| lv_elastday | TYPE SCAL-DATE, " | |||
| lv_iperkz | TYPE PGABV-PERKZ, " | |||
| lv_iperiv | TYPE PGABV-PERIV, " SPACE | |||
| lv_iperid | TYPE PGABV-PERID. " |
|   CALL FUNCTION 'MC_PERIO_GET_FIRST_AND_LASTDAY' "NOTRANSL: zu einer Periode mit Periodenkennzeichen den 1. und letzten Tag |
| EXPORTING | ||
| IFABKL | = lv_ifabkl | |
| IWERKS | = lv_iwerks | |
| IPERKZ | = lv_iperkz | |
| IPERIV | = lv_iperiv | |
| IPERID | = lv_iperid | |
| IMPORTING | ||
| EFIRSTDAY | = lv_efirstday | |
| ELASTDAY | = lv_elastday | |
| EXCEPTIONS | ||
| PERID_INVALID = 1 | ||
| . " MC_PERIO_GET_FIRST_AND_LASTDAY | ||
ABAP code using 7.40 inline data declarations to call FM MC_PERIO_GET_FIRST_AND_LASTDAY
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 FABKL FROM T001W INTO @DATA(ld_ifabkl). | ||||
| DATA(ld_ifabkl) | = ' '. | |||
| "SELECT single DATE FROM SCAL INTO @DATA(ld_efirstday). | ||||
| "SELECT single WERKS FROM RMCP2 INTO @DATA(ld_iwerks). | ||||
| DATA(ld_iwerks) | = ' '. | |||
| "SELECT single DATE FROM SCAL INTO @DATA(ld_elastday). | ||||
| "SELECT single PERKZ FROM PGABV INTO @DATA(ld_iperkz). | ||||
| "SELECT single PERIV FROM PGABV INTO @DATA(ld_iperiv). | ||||
| DATA(ld_iperiv) | = ' '. | |||
| "SELECT single PERID FROM PGABV INTO @DATA(ld_iperid). | ||||
Search for further information about these or an SAP related objects