SAP ALE_WFRES_CHANGEAVAILMULTI Function Module for
ALE_WFRES_CHANGEAVAILMULTI is a standard ale wfres changeavailmulti 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 ale wfres changeavailmulti FM, simply by entering the name ALE_WFRES_CHANGEAVAILMULTI into the relevant SAP transaction such as SE37 or SE38.
Function Group: BAPI_WFMRESOURCE
Program Name: SAPLBAPI_WFMRESOURCE
Main Program: SAPLBAPI_WFMRESOURCE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ALE_WFRES_CHANGEAVAILMULTI 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 'ALE_WFRES_CHANGEAVAILMULTI'".
EXPORTING
ADMINRECORD = "
* TESTRUN = "
* SERIAL_ID = '0' "
TABLES
RESOURCETIMERANGE = "
* RESOURCETIMESPEC = "
* TIMESPECTIMEINT = "
* INVALIDRESOURCES = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_WFRES_CHANGEAVAILMULTI
ADMINRECORD -
Data type: BAPI_WFM_ADMIN_RECORDOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN -
Data type: BAPI_WFM_TESTRUN-TESTRUNOptional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_WFRES_CHANGEAVAILMULTI
RESOURCETIMERANGE -
Data type: BAPI_WFM_RESOURCE_TIMEINTOptional: No
Call by Reference: No ( called with pass by value option)
RESOURCETIMESPEC -
Data type: BAPI_WFM_RES_TIMESPECOptional: Yes
Call by Reference: No ( called with pass by value option)
TIMESPECTIMEINT -
Data type: BAPI_WFM_TIMESPEC_TIMEINTOptional: Yes
Call by Reference: No ( called with pass by value option)
INVALIDRESOURCES -
Data type: BAPI_WFM_RESOURCE_STRUCTOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CREATING_IDOCS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ALE_WFRES_CHANGEAVAILMULTI 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_adminrecord | TYPE BAPI_WFM_ADMIN_RECORD, " | |||
lt_resourcetimerange | TYPE STANDARD TABLE OF BAPI_WFM_RESOURCE_TIMEINT, " | |||
lv_error_creating_idocs | TYPE BAPI_WFM_RESOURCE_TIMEINT, " | |||
lv_testrun | TYPE BAPI_WFM_TESTRUN-TESTRUN, " | |||
lt_resourcetimespec | TYPE STANDARD TABLE OF BAPI_WFM_RES_TIMESPEC, " | |||
lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
lt_timespectimeint | TYPE STANDARD TABLE OF BAPI_WFM_TIMESPEC_TIMEINT, " | |||
lt_invalidresources | TYPE STANDARD TABLE OF BAPI_WFM_RESOURCE_STRUCT, " | |||
lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID. " |
  CALL FUNCTION 'ALE_WFRES_CHANGEAVAILMULTI' " |
EXPORTING | ||
ADMINRECORD | = lv_adminrecord | |
TESTRUN | = lv_testrun | |
SERIAL_ID | = lv_serial_id | |
TABLES | ||
RESOURCETIMERANGE | = lt_resourcetimerange | |
RESOURCETIMESPEC | = lt_resourcetimespec | |
TIMESPECTIMEINT | = lt_timespectimeint | |
INVALIDRESOURCES | = lt_invalidresources | |
RECEIVERS | = lt_receivers | |
COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
APPLICATION_OBJECTS | = lt_application_objects | |
EXCEPTIONS | ||
ERROR_CREATING_IDOCS = 1 | ||
. " ALE_WFRES_CHANGEAVAILMULTI |
ABAP code using 7.40 inline data declarations to call FM ALE_WFRES_CHANGEAVAILMULTI
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 TESTRUN FROM BAPI_WFM_TESTRUN INTO @DATA(ld_testrun). | ||||
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects