SAP SECURITY_READ_BOND_CALL Function Module for FM: Read Cancellation Data of a Bond
SECURITY_READ_BOND_CALL is a standard security read bond call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM: Read Cancellation Data of a Bond 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 security read bond call FM, simply by entering the name SECURITY_READ_BOND_CALL into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVW3
Program Name: SAPLFVW3
Main Program: SAPLFVW3
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SECURITY_READ_BOND_CALL 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 'SECURITY_READ_BOND_CALL'"FM: Read Cancellation Data of a Bond.
EXPORTING
I_RANL = "Wertpapierkennnumer
I_PUTCALL = "Put/Call Kennzeichen
I_SETDATE = "Key Date
* I_CLEAR_BUFFER = ' ' "Delete Buffer
IMPORTING
E_CALLDATE = "Cancellation date
E_PRICE = "Notice Amount
E_CURRENCY1 = "Währung des Kündigungsbetrages
E_BASICRATE = "
EXCEPTIONS
READ_RIGHTS_ERROR = 1 INPUT_ERROR = 2
IMPORTING Parameters details for SECURITY_READ_BOND_CALL
I_RANL - Wertpapierkennnumer
Data type: TERSINTERFACE-RANLOptional: No
Call by Reference: No ( called with pass by value option)
I_PUTCALL - Put/Call Kennzeichen
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_SETDATE - Key Date
Data type: DOptional: No
Call by Reference: No ( called with pass by value option)
I_CLEAR_BUFFER - Delete Buffer
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SECURITY_READ_BOND_CALL
E_CALLDATE - Cancellation date
Data type: DOptional: No
Call by Reference: No ( called with pass by value option)
E_PRICE - Notice Amount
Data type: TERSMULTIPLEDATA-PRICEOptional: No
Call by Reference: No ( called with pass by value option)
E_CURRENCY1 - Währung des Kündigungsbetrages
Data type: TERSMULTIPLEDATA-CURRENCY1Optional: No
Call by Reference: No ( called with pass by value option)
E_BASICRATE -
Data type: TERSMULTIPLEDATA-BASICRATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
READ_RIGHTS_ERROR - Fehler beim Lesen der Ausübungsrechte
Data type:Optional: No
Call by Reference: Yes
INPUT_ERROR - Falscher Übergabeparameter
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SECURITY_READ_BOND_CALL 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_ranl | TYPE TERSINTERFACE-RANL, " | |||
| lv_e_calldate | TYPE D, " | |||
| lv_read_rights_error | TYPE D, " | |||
| lv_e_price | TYPE TERSMULTIPLEDATA-PRICE, " | |||
| lv_i_putcall | TYPE C, " | |||
| lv_input_error | TYPE C, " | |||
| lv_i_setdate | TYPE D, " | |||
| lv_e_currency1 | TYPE TERSMULTIPLEDATA-CURRENCY1, " | |||
| lv_e_basicrate | TYPE TERSMULTIPLEDATA-BASICRATE, " | |||
| lv_i_clear_buffer | TYPE C. " SPACE |
|   CALL FUNCTION 'SECURITY_READ_BOND_CALL' "FM: Read Cancellation Data of a Bond |
| EXPORTING | ||
| I_RANL | = lv_i_ranl | |
| I_PUTCALL | = lv_i_putcall | |
| I_SETDATE | = lv_i_setdate | |
| I_CLEAR_BUFFER | = lv_i_clear_buffer | |
| IMPORTING | ||
| E_CALLDATE | = lv_e_calldate | |
| E_PRICE | = lv_e_price | |
| E_CURRENCY1 | = lv_e_currency1 | |
| E_BASICRATE | = lv_e_basicrate | |
| EXCEPTIONS | ||
| READ_RIGHTS_ERROR = 1 | ||
| INPUT_ERROR = 2 | ||
| . " SECURITY_READ_BOND_CALL | ||
ABAP code using 7.40 inline data declarations to call FM SECURITY_READ_BOND_CALL
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 RANL FROM TERSINTERFACE INTO @DATA(ld_i_ranl). | ||||
| "SELECT single PRICE FROM TERSMULTIPLEDATA INTO @DATA(ld_e_price). | ||||
| "SELECT single CURRENCY1 FROM TERSMULTIPLEDATA INTO @DATA(ld_e_currency1). | ||||
| "SELECT single BASICRATE FROM TERSMULTIPLEDATA INTO @DATA(ld_e_basicrate). | ||||
| DATA(ld_i_clear_buffer) | = ' '. | |||
Search for further information about these or an SAP related objects