SAP ALE_RSS_ADD_SCHEDULE Function Module for BAPI -> IDoc: ALE_RSS_ADD_SCHEDULE
ALE_RSS_ADD_SCHEDULE is a standard ale rss add schedule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_RSS_ADD_SCHEDULE 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 ale rss add schedule FM, simply by entering the name ALE_RSS_ADD_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.
Function Group: 1074
Program Name: SAPL1074
Main Program: SAPL1074
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_RSS_ADD_SCHEDULE 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_RSS_ADD_SCHEDULE'"BAPI -> IDoc: ALE_RSS_ADD_SCHEDULE.
EXPORTING
SECURITYNUMBER = "Security ID Number
* SETNAME = "Redemption Schedule Set
SCHEDULE = "Redemption Schedule Parameter Structure
* TESTRUN = "Switch to Simulation Mode for Write BAPIs
* OBJ_TYPE = 'BUS1074' "
* SERIAL_ID = '0' "
TABLES
REDEMPTIONS = "Redemption Parameter Structure
* REDEMPTIONCONDITIONS = "Redemption Conditions
* INTERESTCONDITIONS = "Interest Conditions
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_RSS_ADD_SCHEDULE
SECURITYNUMBER - Security ID Number
Data type: BAPI1074_SET-SECURITYNUMBEROptional: No
Call by Reference: No ( called with pass by value option)
SETNAME - Redemption Schedule Set
Data type: BAPI1074_SET-SETNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
SCHEDULE - Redemption Schedule Parameter Structure
Data type: BAPI1074_SCHEDULE_CREATEOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI1074_GEN-TESTRUNOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS1074'
Optional: 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_RSS_ADD_SCHEDULE
REDEMPTIONS - Redemption Parameter Structure
Data type: BAPI1074_REDEMPTION_CREATEOptional: No
Call by Reference: No ( called with pass by value option)
REDEMPTIONCONDITIONS - Redemption Conditions
Data type: BAPI1074_RED_COND_CREATEOptional: Yes
Call by Reference: No ( called with pass by value option)
INTERESTCONDITIONS - Interest Conditions
Data type: BAPI1074_INT_COND_CREATEOptional: 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_RSS_ADD_SCHEDULE 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: | ||||
| lt_redemptions | TYPE STANDARD TABLE OF BAPI1074_REDEMPTION_CREATE, " | |||
| lv_securitynumber | TYPE BAPI1074_SET-SECURITYNUMBER, " | |||
| lv_error_creating_idocs | TYPE BAPI1074_SET, " | |||
| lv_setname | TYPE BAPI1074_SET-SETNAME, " | |||
| lt_redemptionconditions | TYPE STANDARD TABLE OF BAPI1074_RED_COND_CREATE, " | |||
| lv_schedule | TYPE BAPI1074_SCHEDULE_CREATE, " | |||
| lt_interestconditions | TYPE STANDARD TABLE OF BAPI1074_INT_COND_CREATE, " | |||
| lv_testrun | TYPE BAPI1074_GEN-TESTRUN, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS1074' | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID. " |
|   CALL FUNCTION 'ALE_RSS_ADD_SCHEDULE' "BAPI -> IDoc: ALE_RSS_ADD_SCHEDULE |
| EXPORTING | ||
| SECURITYNUMBER | = lv_securitynumber | |
| SETNAME | = lv_setname | |
| SCHEDULE | = lv_schedule | |
| TESTRUN | = lv_testrun | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| REDEMPTIONS | = lt_redemptions | |
| REDEMPTIONCONDITIONS | = lt_redemptionconditions | |
| INTERESTCONDITIONS | = lt_interestconditions | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_RSS_ADD_SCHEDULE | ||
ABAP code using 7.40 inline data declarations to call FM ALE_RSS_ADD_SCHEDULE
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 SECURITYNUMBER FROM BAPI1074_SET INTO @DATA(ld_securitynumber). | ||||
| "SELECT single SETNAME FROM BAPI1074_SET INTO @DATA(ld_setname). | ||||
| "SELECT single TESTRUN FROM BAPI1074_GEN INTO @DATA(ld_testrun). | ||||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS1074'. | |||
| "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