SAP SD_DEADLINE_MAINTAIN Function Module for









SD_DEADLINE_MAINTAIN is a standard sd deadline maintain 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 sd deadline maintain FM, simply by entering the name SD_DEADLINE_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_DEADLINE_MAINTAIN 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 'SD_DEADLINE_MAINTAIN'"
EXPORTING
* DEADLINE_NO_IN = ' ' "
* DEADLINE_PROFILE_IN = 'SD01' "
* FCODE_IN = 'SDV1' "
* TRTYP_IN = 'H' "
* SCREEN_TEXT_IN = ' ' "
* CUA_TEXT_IN = ' ' "

IMPORTING
DEADLINE_NO_OUT = "
FLAG_CHANGE_OUT = "

EXCEPTIONS
INVALID_TCODE = 1 NO_DEADLINES = 2 INVALID_PROFILE = 3
.



IMPORTING Parameters details for SD_DEADLINE_MAINTAIN

DEADLINE_NO_IN -

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

DEADLINE_PROFILE_IN -

Data type: TCN41-PROFIDNETZ
Default: 'SD01'
Optional: Yes
Call by Reference: No ( called with pass by value option)

FCODE_IN -

Data type: T185-FCODE
Default: 'SDV1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRTYP_IN -

Data type: T180-TRTYP
Default: 'H'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCREEN_TEXT_IN -

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

CUA_TEXT_IN -

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

EXPORTING Parameters details for SD_DEADLINE_MAINTAIN

DEADLINE_NO_OUT -

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

FLAG_CHANGE_OUT -

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

EXCEPTIONS details

INVALID_TCODE -

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

NO_DEADLINES -

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

INVALID_PROFILE -

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

Copy and paste ABAP code example for SD_DEADLINE_MAINTAIN 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_invalid_tcode  TYPE STRING, "   
lv_deadline_no_in  TYPE CAUFVD-AUFNR, "   SPACE
lv_deadline_no_out  TYPE CAUFVD-AUFNR, "   
lv_no_deadlines  TYPE CAUFVD, "   
lv_flag_change_out  TYPE R185D-DATALOSS, "   
lv_deadline_profile_in  TYPE TCN41-PROFIDNETZ, "   'SD01'
lv_fcode_in  TYPE T185-FCODE, "   'SDV1'
lv_invalid_profile  TYPE T185, "   
lv_trtyp_in  TYPE T180-TRTYP, "   'H'
lv_screen_text_in  TYPE T180, "   SPACE
lv_cua_text_in  TYPE T180. "   SPACE

  CALL FUNCTION 'SD_DEADLINE_MAINTAIN'  "
    EXPORTING
         DEADLINE_NO_IN = lv_deadline_no_in
         DEADLINE_PROFILE_IN = lv_deadline_profile_in
         FCODE_IN = lv_fcode_in
         TRTYP_IN = lv_trtyp_in
         SCREEN_TEXT_IN = lv_screen_text_in
         CUA_TEXT_IN = lv_cua_text_in
    IMPORTING
         DEADLINE_NO_OUT = lv_deadline_no_out
         FLAG_CHANGE_OUT = lv_flag_change_out
    EXCEPTIONS
        INVALID_TCODE = 1
        NO_DEADLINES = 2
        INVALID_PROFILE = 3
. " SD_DEADLINE_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM SD_DEADLINE_MAINTAIN

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 AUFNR FROM CAUFVD INTO @DATA(ld_deadline_no_in).
DATA(ld_deadline_no_in) = ' '.
 
"SELECT single AUFNR FROM CAUFVD INTO @DATA(ld_deadline_no_out).
 
 
"SELECT single DATALOSS FROM R185D INTO @DATA(ld_flag_change_out).
 
"SELECT single PROFIDNETZ FROM TCN41 INTO @DATA(ld_deadline_profile_in).
DATA(ld_deadline_profile_in) = 'SD01'.
 
"SELECT single FCODE FROM T185 INTO @DATA(ld_fcode_in).
DATA(ld_fcode_in) = 'SDV1'.
 
 
"SELECT single TRTYP FROM T180 INTO @DATA(ld_trtyp_in).
DATA(ld_trtyp_in) = 'H'.
 
DATA(ld_screen_text_in) = ' '.
 
DATA(ld_cua_text_in) = ' '.
 


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!