SAP ALE_REQUEST_ADDSPECIALDATES Function Module for









ALE_REQUEST_ADDSPECIALDATES is a standard ale request addspecialdates 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 request addspecialdates FM, simply by entering the name ALE_REQUEST_ADDSPECIALDATES into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_REQUEST_ADDSPECIALDATES 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_REQUEST_ADDSPECIALDATES'"
EXPORTING
REQUESTNUMBER = "Request Number
* EXECUTIONPERIOD = "Execution Period of a Standing Request
* REQUESTCONTROL = "BAPI Processing Control for Requests
* OBJ_TYPE = 'CA_REQUEST' "
* SERIAL_ID = '0' "

TABLES
* REQUESTDUEDATAIN = "BAPI Import: Due Dates of Request
* REQUESTDUEDATAOUT = "BAPI Export: Due Dates of Request
* EXTENSIONIN = "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "

EXCEPTIONS
ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_REQUEST_ADDSPECIALDATES

REQUESTNUMBER - Request Number

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

EXECUTIONPERIOD - Execution Period of a Standing Request

Data type: BAPIREQUEST_DUE_IN-EXECUTION_PERIOD
Optional: Yes
Call by Reference: No ( called with pass by value option)

REQUESTCONTROL - BAPI Processing Control for Requests

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'CA_REQUEST'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_REQUEST_ADDSPECIALDATES

REQUESTDUEDATAIN - BAPI Import: Due Dates of Request

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

REQUESTDUEDATAOUT - BAPI Export: Due Dates of Request

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

EXTENSIONIN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

Data type: SWOTOBJID
Optional: 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_REQUEST_ADDSPECIALDATES 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_requestnumber  TYPE BAPIREQUEST_KEY-REQUESTNUMBER, "   
lt_requestduedatain  TYPE STANDARD TABLE OF BAPIREQUEST_DUE_IN, "   
lv_error_creating_idocs  TYPE BAPIREQUEST_DUE_IN, "   
lv_executionperiod  TYPE BAPIREQUEST_DUE_IN-EXECUTION_PERIOD, "   
lt_requestduedataout  TYPE STANDARD TABLE OF BAPIREQUEST_DUE_OUT, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_requestcontrol  TYPE BAPIREQUEST_CONTROL, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'CA_REQUEST'
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID. "   

  CALL FUNCTION 'ALE_REQUEST_ADDSPECIALDATES'  "
    EXPORTING
         REQUESTNUMBER = lv_requestnumber
         EXECUTIONPERIOD = lv_executionperiod
         REQUESTCONTROL = lv_requestcontrol
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         REQUESTDUEDATAIN = lt_requestduedatain
         REQUESTDUEDATAOUT = lt_requestduedataout
         EXTENSIONIN = lt_extensionin
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_REQUEST_ADDSPECIALDATES




ABAP code using 7.40 inline data declarations to call FM ALE_REQUEST_ADDSPECIALDATES

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 REQUESTNUMBER FROM BAPIREQUEST_KEY INTO @DATA(ld_requestnumber).
 
 
 
"SELECT single EXECUTION_PERIOD FROM BAPIREQUEST_DUE_IN INTO @DATA(ld_executionperiod).
 
 
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'CA_REQUEST'.
 
 
"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



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!