SAP MD_SAFETY_TIME_DEC Function Module for NOTRANSL: Untertägiger Bedarfsvorlauf









MD_SAFETY_TIME_DEC is a standard md safety time dec 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: Untertägiger Bedarfsvorlauf 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 md safety time dec FM, simply by entering the name MD_SAFETY_TIME_DEC into the relevant SAP transaction such as SE37 or SE38.

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



Function MD_SAFETY_TIME_DEC 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 'MD_SAFETY_TIME_DEC'"NOTRANSL: Untertägiger Bedarfsvorlauf
EXPORTING
EMT61D = "Material Master: MRP
ECM61M = "MRP control indicator -material level-
ECM61X = "MRP Control Indicator -Transaction Level-
ECM61B = "
EPLSC = "Planning Scenarios in Long-Term Planning

CHANGING
EMDKP = "

TABLES
CT_MDPSX = "Item in MRP Document
.



IMPORTING Parameters details for MD_SAFETY_TIME_DEC

EMT61D - Material Master: MRP

Data type: MT61D
Optional: No
Call by Reference: Yes

ECM61M - MRP control indicator -material level-

Data type: CM61M
Optional: No
Call by Reference: Yes

ECM61X - MRP Control Indicator -Transaction Level-

Data type: CM61X
Optional: No
Call by Reference: Yes

ECM61B -

Data type: M61X_CM61B
Optional: No
Call by Reference: Yes

EPLSC - Planning Scenarios in Long-Term Planning

Data type: PLSC
Optional: No
Call by Reference: Yes

CHANGING Parameters details for MD_SAFETY_TIME_DEC

EMDKP -

Data type: MDKP
Optional: No
Call by Reference: Yes

TABLES Parameters details for MD_SAFETY_TIME_DEC

CT_MDPSX - Item in MRP Document

Data type: MDPS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MD_SAFETY_TIME_DEC 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_emdkp  TYPE MDKP, "   
lv_emt61d  TYPE MT61D, "   
lt_ct_mdpsx  TYPE STANDARD TABLE OF MDPS, "   
lv_ecm61m  TYPE CM61M, "   
lv_ecm61x  TYPE CM61X, "   
lv_ecm61b  TYPE M61X_CM61B, "   
lv_eplsc  TYPE PLSC. "   

  CALL FUNCTION 'MD_SAFETY_TIME_DEC'  "NOTRANSL: Untertägiger Bedarfsvorlauf
    EXPORTING
         EMT61D = lv_emt61d
         ECM61M = lv_ecm61m
         ECM61X = lv_ecm61x
         ECM61B = lv_ecm61b
         EPLSC = lv_eplsc
    CHANGING
         EMDKP = lv_emdkp
    TABLES
         CT_MDPSX = lt_ct_mdpsx
. " MD_SAFETY_TIME_DEC




ABAP code using 7.40 inline data declarations to call FM MD_SAFETY_TIME_DEC

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



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!