SAP MARC_PLIFZ Function Module for NOTRANSL: Prüfung Planlieferzeit









MARC_PLIFZ is a standard marc plifz 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 Planlieferzeit 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 marc plifz FM, simply by entering the name MARC_PLIFZ into the relevant SAP transaction such as SE37 or SE38.

Function Group: MG10
Program Name: SAPLMG10
Main Program: SAPLMG10
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MARC_PLIFZ 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 'MARC_PLIFZ'"NOTRANSL: Prüfung Planlieferzeit
EXPORTING
P_DISMM = "MRP Procedure
P_BESKZ = "
P_PLIFZ = "Planned Delivery Time
* P_KZ_NO_WARN = ' ' "

EXCEPTIONS
P_ERR_MARC_PLIFZ = 1 ERR_T438A = 2
.



IMPORTING Parameters details for MARC_PLIFZ

P_DISMM - MRP Procedure

Data type: MARC-DISMM
Optional: No
Call by Reference: No ( called with pass by value option)

P_BESKZ -

Data type: MARC-BESKZ
Optional: No
Call by Reference: No ( called with pass by value option)

P_PLIFZ - Planned Delivery Time

Data type: MARC-PLIFZ
Optional: No
Call by Reference: No ( called with pass by value option)

P_KZ_NO_WARN -

Data type: RMMG08_012-MSGTYP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

P_ERR_MARC_PLIFZ - Check Error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERR_T438A -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MARC_PLIFZ 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_dismm  TYPE MARC-DISMM, "   
lv_p_err_marc_plifz  TYPE MARC, "   
lv_p_beskz  TYPE MARC-BESKZ, "   
lv_err_t438a  TYPE MARC, "   
lv_p_plifz  TYPE MARC-PLIFZ, "   
lv_p_kz_no_warn  TYPE RMMG08_012-MSGTYP. "   SPACE

  CALL FUNCTION 'MARC_PLIFZ'  "NOTRANSL: Prüfung Planlieferzeit
    EXPORTING
         P_DISMM = lv_p_dismm
         P_BESKZ = lv_p_beskz
         P_PLIFZ = lv_p_plifz
         P_KZ_NO_WARN = lv_p_kz_no_warn
    EXCEPTIONS
        P_ERR_MARC_PLIFZ = 1
        ERR_T438A = 2
. " MARC_PLIFZ




ABAP code using 7.40 inline data declarations to call FM MARC_PLIFZ

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 DISMM FROM MARC INTO @DATA(ld_p_dismm).
 
 
"SELECT single BESKZ FROM MARC INTO @DATA(ld_p_beskz).
 
 
"SELECT single PLIFZ FROM MARC INTO @DATA(ld_p_plifz).
 
"SELECT single MSGTYP FROM RMMG08_012 INTO @DATA(ld_p_kz_no_warn).
DATA(ld_p_kz_no_warn) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!