SAP D_250_PERKZ_WARN Function Module for NOTRANSL: Prüfung Periodenkennzeichen / Verbrauchswerte
D_250_PERKZ_WARN is a standard d 250 perkz warn 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: Prüfung Periodenkennzeichen / Verbrauchswerte 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 d 250 perkz warn FM, simply by entering the name D_250_PERKZ_WARN into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG10
Program Name: SAPLMG10
Main Program: SAPLMG10
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function D_250_PERKZ_WARN 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 'D_250_PERKZ_WARN'"NOTRANSL: Prüfung Periodenkennzeichen / Verbrauchswerte.
EXPORTING
P_PERKZ_DB = "
* P_KZ_NO_WARN = ' ' "
P_PERKZ = "
P_PERIV_DB = "
P_PERIV = "
* P_KZRFB = ' ' "
P_MARA_MATNR = "
P_MARC_WERKS = "
P_ALTPERKZ = "
P_ALTPERIV = "
IMPORTING
P_FLGMVER = "Ind.: Consumption values involved
P_FLGPROGWERTE = "Ind.: Forecast values chosen
TABLES
* MESSAGE_TAB = "
EXCEPTIONS
P_ERR_D_250_PERKZ_WARN = 1
IMPORTING Parameters details for D_250_PERKZ_WARN
P_PERKZ_DB -
Data type: MARC-PERKZOptional: No
Call by Reference: No ( called with pass by value option)
P_KZ_NO_WARN -
Data type: RMMG08_012-MSGTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
P_PERKZ -
Data type: MARC-PERKZOptional: No
Call by Reference: No ( called with pass by value option)
P_PERIV_DB -
Data type: MARC-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
P_PERIV -
Data type: MARC-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
P_KZRFB -
Data type: MTCOM-KZRFBDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
P_MARA_MATNR -
Data type: MARA-MATNROptional: No
Call by Reference: No ( called with pass by value option)
P_MARC_WERKS -
Data type: MARC-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
P_ALTPERKZ -
Data type: MARC-PERKZOptional: No
Call by Reference: No ( called with pass by value option)
P_ALTPERIV -
Data type: MARC-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for D_250_PERKZ_WARN
P_FLGMVER - Ind.: Consumption values involved
Data type: T130F-KZREFOptional: No
Call by Reference: No ( called with pass by value option)
P_FLGPROGWERTE - Ind.: Forecast values chosen
Data type: T130F-KZREFOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for D_250_PERKZ_WARN
MESSAGE_TAB -
Data type: MATMESSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
P_ERR_D_250_PERKZ_WARN - Check error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for D_250_PERKZ_WARN 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_p_flgmver | TYPE T130F-KZREF, " | |||
| lv_p_perkz_db | TYPE MARC-PERKZ, " | |||
| lt_message_tab | TYPE STANDARD TABLE OF MATMESS, " | |||
| lv_p_err_d_250_perkz_warn | TYPE MATMESS, " | |||
| lv_p_kz_no_warn | TYPE RMMG08_012-MSGTYP, " SPACE | |||
| lv_p_perkz | TYPE MARC-PERKZ, " | |||
| lv_p_flgprogwerte | TYPE T130F-KZREF, " | |||
| lv_p_periv_db | TYPE MARC-PERIV, " | |||
| lv_p_periv | TYPE MARC-PERIV, " | |||
| lv_p_kzrfb | TYPE MTCOM-KZRFB, " SPACE | |||
| lv_p_mara_matnr | TYPE MARA-MATNR, " | |||
| lv_p_marc_werks | TYPE MARC-WERKS, " | |||
| lv_p_altperkz | TYPE MARC-PERKZ, " | |||
| lv_p_altperiv | TYPE MARC-PERIV. " |
|   CALL FUNCTION 'D_250_PERKZ_WARN' "NOTRANSL: Prüfung Periodenkennzeichen / Verbrauchswerte |
| EXPORTING | ||
| P_PERKZ_DB | = lv_p_perkz_db | |
| P_KZ_NO_WARN | = lv_p_kz_no_warn | |
| P_PERKZ | = lv_p_perkz | |
| P_PERIV_DB | = lv_p_periv_db | |
| P_PERIV | = lv_p_periv | |
| P_KZRFB | = lv_p_kzrfb | |
| P_MARA_MATNR | = lv_p_mara_matnr | |
| P_MARC_WERKS | = lv_p_marc_werks | |
| P_ALTPERKZ | = lv_p_altperkz | |
| P_ALTPERIV | = lv_p_altperiv | |
| IMPORTING | ||
| P_FLGMVER | = lv_p_flgmver | |
| P_FLGPROGWERTE | = lv_p_flgprogwerte | |
| TABLES | ||
| MESSAGE_TAB | = lt_message_tab | |
| EXCEPTIONS | ||
| P_ERR_D_250_PERKZ_WARN = 1 | ||
| . " D_250_PERKZ_WARN | ||
ABAP code using 7.40 inline data declarations to call FM D_250_PERKZ_WARN
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 KZREF FROM T130F INTO @DATA(ld_p_flgmver). | ||||
| "SELECT single PERKZ FROM MARC INTO @DATA(ld_p_perkz_db). | ||||
| "SELECT single MSGTYP FROM RMMG08_012 INTO @DATA(ld_p_kz_no_warn). | ||||
| DATA(ld_p_kz_no_warn) | = ' '. | |||
| "SELECT single PERKZ FROM MARC INTO @DATA(ld_p_perkz). | ||||
| "SELECT single KZREF FROM T130F INTO @DATA(ld_p_flgprogwerte). | ||||
| "SELECT single PERIV FROM MARC INTO @DATA(ld_p_periv_db). | ||||
| "SELECT single PERIV FROM MARC INTO @DATA(ld_p_periv). | ||||
| "SELECT single KZRFB FROM MTCOM INTO @DATA(ld_p_kzrfb). | ||||
| DATA(ld_p_kzrfb) | = ' '. | |||
| "SELECT single MATNR FROM MARA INTO @DATA(ld_p_mara_matnr). | ||||
| "SELECT single WERKS FROM MARC INTO @DATA(ld_p_marc_werks). | ||||
| "SELECT single PERKZ FROM MARC INTO @DATA(ld_p_altperkz). | ||||
| "SELECT single PERIV FROM MARC INTO @DATA(ld_p_altperiv). | ||||
Search for further information about these or an SAP related objects