SAP SECURITY_READ_INFO Function Module for Read Info









SECURITY_READ_INFO is a standard security read info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Info 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 info FM, simply by entering the name SECURITY_READ_INFO into the relevant SAP transaction such as SE37 or SE38.

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



Function SECURITY_READ_INFO 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_INFO'"Read Info
  EXPORTING
   I_SECURITY_ID =  "Security ID number
*  I_TRANSACTION_DATE =  "Date and Time, Current (Application Server) Date
*  I_CHK_FIN_DUE_DATE =  "Prüfung auf Laufzeitende als Fehler oder Warnung

 IMPORTING
   E_STATUS =  "Status of a security
   E_QUOTATION =  "Quotation Indicator
   E_SHORT_TEXT =  "Short Description
   E_LONG_TEXT =  "Long Name
   E_HOME_EXCHANGE =  "Handelsplatz (Heimatbörse)
   E_LISTING_CURRENCY =  "Quotation Currency
   E_MESSAGES =  "Error Messages Table
   E_ROUNDING_RULE =  "Rounding Rule
   E_CURRENCY_UNIT =  "Währungseinheit eines Commodity-Futures
.



IMPORTING Parameters details for SECURITY_READ_INFO

I_SECURITY_ID - Security ID number

Data type: WP_RANL
Optional: No
Call by Reference: Yes

I_TRANSACTION_DATE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_CHK_FIN_DUE_DATE - Prüfung auf Laufzeitende als Fehler oder Warnung

Data type: C
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SECURITY_READ_INFO

E_STATUS - Status of a security

Data type: SEC_STATUS
Optional: No
Call by Reference: Yes

E_QUOTATION - Quotation Indicator

Data type: SNOTI
Optional: No
Call by Reference: Yes

E_SHORT_TEXT - Short Description

Data type: XALKZ
Optional: No
Call by Reference: Yes

E_LONG_TEXT - Long Name

Data type: XALLB
Optional: No
Call by Reference: Yes

E_HOME_EXCHANGE - Handelsplatz (Heimatbörse)

Data type: VVRHANDPL
Optional: No
Call by Reference: Yes

E_LISTING_CURRENCY - Quotation Currency

Data type: WAERS
Optional: No
Call by Reference: Yes

E_MESSAGES - Error Messages Table

Data type: TSMESG
Optional: No
Call by Reference: Yes

E_ROUNDING_RULE - Rounding Rule

Data type: TPM_ROUNDING_RULE
Optional: No
Call by Reference: Yes

E_CURRENCY_UNIT - Währungseinheit eines Commodity-Futures

Data type: VVSRUNIT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SECURITY_READ_INFO 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_e_status  TYPE SEC_STATUS, "   
lv_i_security_id  TYPE WP_RANL, "   
lv_e_quotation  TYPE SNOTI, "   
lv_i_transaction_date  TYPE SY-DATUM, "   
lv_e_short_text  TYPE XALKZ, "   
lv_i_chk_fin_due_date  TYPE C, "   
lv_e_long_text  TYPE XALLB, "   
lv_e_home_exchange  TYPE VVRHANDPL, "   
lv_e_listing_currency  TYPE WAERS, "   
lv_e_messages  TYPE TSMESG, "   
lv_e_rounding_rule  TYPE TPM_ROUNDING_RULE, "   
lv_e_currency_unit  TYPE VVSRUNIT. "   

  CALL FUNCTION 'SECURITY_READ_INFO'  "Read Info
    EXPORTING
         I_SECURITY_ID = lv_i_security_id
         I_TRANSACTION_DATE = lv_i_transaction_date
         I_CHK_FIN_DUE_DATE = lv_i_chk_fin_due_date
    IMPORTING
         E_STATUS = lv_e_status
         E_QUOTATION = lv_e_quotation
         E_SHORT_TEXT = lv_e_short_text
         E_LONG_TEXT = lv_e_long_text
         E_HOME_EXCHANGE = lv_e_home_exchange
         E_LISTING_CURRENCY = lv_e_listing_currency
         E_MESSAGES = lv_e_messages
         E_ROUNDING_RULE = lv_e_rounding_rule
         E_CURRENCY_UNIT = lv_e_currency_unit
. " SECURITY_READ_INFO




ABAP code using 7.40 inline data declarations to call FM SECURITY_READ_INFO

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 DATUM FROM SY INTO @DATA(ld_i_transaction_date).
 
 
 
 
 
 
 
 
 


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!