SAP DNO_OW_TASK_GET_AVAIL_MULTI Function Module for
DNO_OW_TASK_GET_AVAIL_MULTI is a standard dno ow task get avail multi 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 dno ow task get avail multi FM, simply by entering the name DNO_OW_TASK_GET_AVAIL_MULTI into the relevant SAP transaction such as SE37 or SE38.
Function Group: DNO_OW_TASK
Program Name: SAPLDNO_OW_TASK
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DNO_OW_TASK_GET_AVAIL_MULTI 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 'DNO_OW_TASK_GET_AVAIL_MULTI'".
EXPORTING
I_DATE_START = "Field of Type DATS
I_DATE_END = "Field of Type DATS
TABLES
TI_PROCESSOR = "Person Responsible
TE_AVAILABILITY = "Availability of Processors
IMPORTING Parameters details for DNO_OW_TASK_GET_AVAIL_MULTI
I_DATE_START - Field of Type DATS
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_END - Field of Type DATS
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DNO_OW_TASK_GET_AVAIL_MULTI
TI_PROCESSOR - Person Responsible
Data type: DNOS_PROCESSOROptional: No
Call by Reference: Yes
TE_AVAILABILITY - Availability of Processors
Data type: DNOS_AVAILABILITYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DNO_OW_TASK_GET_AVAIL_MULTI 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_i_date_start | TYPE DATS, " | |||
| lt_ti_processor | TYPE STANDARD TABLE OF DNOS_PROCESSOR, " | |||
| lv_i_date_end | TYPE DATS, " | |||
| lt_te_availability | TYPE STANDARD TABLE OF DNOS_AVAILABILITY. " |
|   CALL FUNCTION 'DNO_OW_TASK_GET_AVAIL_MULTI' " |
| EXPORTING | ||
| I_DATE_START | = lv_i_date_start | |
| I_DATE_END | = lv_i_date_end | |
| TABLES | ||
| TI_PROCESSOR | = lt_ti_processor | |
| TE_AVAILABILITY | = lt_te_availability | |
| . " DNO_OW_TASK_GET_AVAIL_MULTI | ||
ABAP code using 7.40 inline data declarations to call FM DNO_OW_TASK_GET_AVAIL_MULTI
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