SAP TB_DATAFEED_RATE_RECEIVE_ASYN Function Module for NOTRANSL: Datafeed: Empfangen von Datafeed-Daten asynchron
TB_DATAFEED_RATE_RECEIVE_ASYN is a standard tb datafeed rate receive asyn SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Datafeed: Empfangen von Datafeed-Daten asynchron 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 tb datafeed rate receive asyn FM, simply by entering the name TB_DATAFEED_RATE_RECEIVE_ASYN into the relevant SAP transaction such as SE37 or SE38.
Function Group: TBDF
Program Name: SAPLTBDF
Main Program: SAPLTBDF
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TB_DATAFEED_RATE_RECEIVE_ASYN 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 'TB_DATAFEED_RATE_RECEIVE_ASYN'"NOTRANSL: Datafeed: Empfangen von Datafeed-Daten asynchron.
EXPORTING
FEEDNAME = "Name of Feed
HISTORY = "Transfer historical data? 'X' = Yes
UPDATE = "Update operational SAP tables? 'X' = Yes
TABLES
ANSWER = "Input: Datafeed Replies
* ERROR = "Output: Error Messages in SAP Structure
* ERROR_DOKU = "Output: Long Texts for Error Messages
EXCEPTIONS
NO_AUTHORITY = 1 UPDATE_ERROR = 2 EMPTY_TABLE = 3 INVALID_FEEDNAME = 4 NO_PROTOCOL_CUSTOMIZING = 5
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLTBDF_001 Market Data: Interface for Reading Saved Rates
EXIT_SAPLTBDF_002 Market Data: Rate/Price Interface to Market Data Buffer VTB_MARKET
IMPORTING Parameters details for TB_DATAFEED_RATE_RECEIVE_ASYN
FEEDNAME - Name of Feed
Data type: VTBDFF-RFEEDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
HISTORY - Transfer historical data? 'X' = Yes
Data type: VTB_DFCU-RUPDHISTOptional: No
Call by Reference: No ( called with pass by value option)
UPDATE - Update operational SAP tables? 'X' = Yes
Data type: VTB_DFCU-RUPDHISTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TB_DATAFEED_RATE_RECEIVE_ASYN
ANSWER - Input: Datafeed Replies
Data type: VTB_DFANSOptional: No
Call by Reference: No ( called with pass by value option)
ERROR - Output: Error Messages in SAP Structure
Data type: MESGOptional: Yes
Call by Reference: No ( called with pass by value option)
ERROR_DOKU - Output: Long Texts for Error Messages
Data type: TLINEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORITY - No authorization for calling the function module
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_ERROR - Error in the datafeed replies
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EMPTY_TABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_FEEDNAME - Feed name is not recognized
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PROTOCOL_CUSTOMIZING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TB_DATAFEED_RATE_RECEIVE_ASYN 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_answer | TYPE STANDARD TABLE OF VTB_DFANS, " | |||
| lv_feedname | TYPE VTBDFF-RFEEDNAME, " | |||
| lv_no_authority | TYPE VTBDFF, " | |||
| lt_error | TYPE STANDARD TABLE OF MESG, " | |||
| lv_history | TYPE VTB_DFCU-RUPDHIST, " | |||
| lv_update_error | TYPE VTB_DFCU, " | |||
| lv_update | TYPE VTB_DFCU-RUPDHIST, " | |||
| lt_error_doku | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_empty_table | TYPE TLINE, " | |||
| lv_invalid_feedname | TYPE TLINE, " | |||
| lv_no_protocol_customizing | TYPE TLINE. " |
|   CALL FUNCTION 'TB_DATAFEED_RATE_RECEIVE_ASYN' "NOTRANSL: Datafeed: Empfangen von Datafeed-Daten asynchron |
| EXPORTING | ||
| FEEDNAME | = lv_feedname | |
| HISTORY | = lv_history | |
| UPDATE | = lv_update | |
| TABLES | ||
| ANSWER | = lt_answer | |
| ERROR | = lt_error | |
| ERROR_DOKU | = lt_error_doku | |
| EXCEPTIONS | ||
| NO_AUTHORITY = 1 | ||
| UPDATE_ERROR = 2 | ||
| EMPTY_TABLE = 3 | ||
| INVALID_FEEDNAME = 4 | ||
| NO_PROTOCOL_CUSTOMIZING = 5 | ||
| . " TB_DATAFEED_RATE_RECEIVE_ASYN | ||
ABAP code using 7.40 inline data declarations to call FM TB_DATAFEED_RATE_RECEIVE_ASYN
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 RFEEDNAME FROM VTBDFF INTO @DATA(ld_feedname). | ||||
| "SELECT single RUPDHIST FROM VTB_DFCU INTO @DATA(ld_history). | ||||
| "SELECT single RUPDHIST FROM VTB_DFCU INTO @DATA(ld_update). | ||||
Search for further information about these or an SAP related objects