SAP SD_DEADLINE_PAI_INTERFACE Function Module for NOTRANSL: Interfaceroutine für PAI-Module zur Terminbearbeitung
SD_DEADLINE_PAI_INTERFACE is a standard sd deadline pai interface 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: Interfaceroutine für PAI-Module zur Terminbearbeitung 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 sd deadline pai interface FM, simply by entering the name SD_DEADLINE_PAI_INTERFACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V51T
Program Name: SAPLV51T
Main Program: SAPLV51T
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_DEADLINE_PAI_INTERFACE 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_PAI_INTERFACE'"NOTRANSL: Interfaceroutine für PAI-Module zur Terminbearbeitung.
EXPORTING
IF_EVENT = "Function Code
IMPORTING
EF_MODIF = "
EXCEPTIONS
HANDLE_NOT_FOUND = 1 FATAL_ERROR = 2
IMPORTING Parameters details for SD_DEADLINE_PAI_INTERFACE
IF_EVENT - Function Code
Data type: FCODEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_DEADLINE_PAI_INTERFACE
EF_MODIF -
Data type: FLAGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
HANDLE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FATAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_DEADLINE_PAI_INTERFACE 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_ef_modif | TYPE FLAG, " | |||
| lv_if_event | TYPE FCODE, " | |||
| lv_handle_not_found | TYPE FCODE, " | |||
| lv_fatal_error | TYPE FCODE. " |
|   CALL FUNCTION 'SD_DEADLINE_PAI_INTERFACE' "NOTRANSL: Interfaceroutine für PAI-Module zur Terminbearbeitung |
| EXPORTING | ||
| IF_EVENT | = lv_if_event | |
| IMPORTING | ||
| EF_MODIF | = lv_ef_modif | |
| EXCEPTIONS | ||
| HANDLE_NOT_FOUND = 1 | ||
| FATAL_ERROR = 2 | ||
| . " SD_DEADLINE_PAI_INTERFACE | ||
ABAP code using 7.40 inline data declarations to call FM SD_DEADLINE_PAI_INTERFACE
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