SAP BAPI_RSS_CHANGE_SCHEDULE Function Module for Change Repayment Schedule Data
BAPI_RSS_CHANGE_SCHEDULE is a standard bapi rss change 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 Change Repayment Schedule Data 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 bapi rss change schedule FM, simply by entering the name BAPI_RSS_CHANGE_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.
Function Group: 1074
Program Name: SAPL1074
Main Program: SAPL1074
Appliation area:
Release date: 21-Jun-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_RSS_CHANGE_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 'BAPI_RSS_CHANGE_SCHEDULE'"Change Repayment Schedule Data.
EXPORTING
SECURITYNUMBER = "Security ID Number
SETNAME = "Redemption Schedule Set
VALIDFROM = "'Effective From' Date of Redemption Schedule
* SCHEDULE = "Change Redemption Schedule
* TESTRUN = 'X' "Switch to Simulation Mode for Write BAPIs
TABLES
* QUANTITY = "Change Repayment Amount
* PUBLICATIONDATE = "Change Publication Date
* RETURN = "Return Parameters
* REDEMPTIONS = "Redemption Parameter Structure
IMPORTING Parameters details for BAPI_RSS_CHANGE_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: No
Call by Reference: No ( called with pass by value option)
VALIDFROM - 'Effective From' Date of Redemption Schedule
Data type: BAPI1074_SCHEDULE-VALID_FROMOptional: No
Call by Reference: No ( called with pass by value option)
SCHEDULE - Change Redemption Schedule
Data type: BAPI1074_SCHEDULE_CHANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI1074_GEN-TESTRUNDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RSS_CHANGE_SCHEDULE
QUANTITY - Change Repayment Amount
Data type: BAPI1074_RED_QUANTITY_CHNGOptional: Yes
Call by Reference: Yes
PUBLICATIONDATE - Change Publication Date
Data type: BAPI1074_RED_PUB_DATE_CHNGOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
REDEMPTIONS - Redemption Parameter Structure
Data type: BAPI1074_REDEMPTION_CREATEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RSS_CHANGE_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_quantity | TYPE STANDARD TABLE OF BAPI1074_RED_QUANTITY_CHNG, " | |||
| lv_securitynumber | TYPE BAPI1074_SET-SECURITYNUMBER, " | |||
| lv_setname | TYPE BAPI1074_SET-SETNAME, " | |||
| lt_publicationdate | TYPE STANDARD TABLE OF BAPI1074_RED_PUB_DATE_CHNG, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_validfrom | TYPE BAPI1074_SCHEDULE-VALID_FROM, " | |||
| lv_schedule | TYPE BAPI1074_SCHEDULE_CHANGE, " | |||
| lt_redemptions | TYPE STANDARD TABLE OF BAPI1074_REDEMPTION_CREATE, " | |||
| lv_testrun | TYPE BAPI1074_GEN-TESTRUN. " 'X' |
|   CALL FUNCTION 'BAPI_RSS_CHANGE_SCHEDULE' "Change Repayment Schedule Data |
| EXPORTING | ||
| SECURITYNUMBER | = lv_securitynumber | |
| SETNAME | = lv_setname | |
| VALIDFROM | = lv_validfrom | |
| SCHEDULE | = lv_schedule | |
| TESTRUN | = lv_testrun | |
| TABLES | ||
| QUANTITY | = lt_quantity | |
| PUBLICATIONDATE | = lt_publicationdate | |
| RETURN | = lt_return | |
| REDEMPTIONS | = lt_redemptions | |
| . " BAPI_RSS_CHANGE_SCHEDULE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RSS_CHANGE_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 VALID_FROM FROM BAPI1074_SCHEDULE INTO @DATA(ld_validfrom). | ||||
| "SELECT single TESTRUN FROM BAPI1074_GEN INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = 'X'. | |||
Search for further information about these or an SAP related objects