RFC_PRA SAP (RFC Interface: Payment Request Header Data) Structure details
Description: RFC Interface: Payment Request Header Data
Structure field list including key, data, relationships and ABAP select examples
RFC_PRA is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "RFC Interface: Payment Request Header Data" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_RFC_PRA TYPE RFC_PRA.
The RFC_PRA table consists of various fields, each holding specific information or linking keys about RFC Interface: Payment Request Header Data data available in SAP. These include BUDAT (Character Field Length = 10), BLDAT (Character Field Length = 10), BUKRS (Not More Closely Defined Area, Possibly Used for Patchlevels), WAERS (R/2 table).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP RFC_PRA structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| BLART | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
| BUDAT | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| BLDAT | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| BUKRS | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| WAERS | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| WWERT | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| KURSF | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| XBLNR | Field of length 16 | CHAR16 | CHAR | 16 | CHAR16 | ||||
| BKTXT | User field for cluster PC (national) | CHAR25 | CHAR | 25 | CHAR25 | ||||
| LIFNR | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| XSKZG | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| UMSKZ | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| XHKZG | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| WRBTR | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| WMWST | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| MWSKZ | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
| PAMTF | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| PACUR | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| ZWERT | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| ZUONR | Field length 18 | CHAR18 | CHAR | 18 | CHAR18 | ||||
| SGTXT | Comment | CHAR50 | CHAR | 50 | TEXT50 | ||||
| ZFBDT | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| ZTERM | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| HLP_VALUT | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| XVALUT | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| ZLSPR | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| XURGE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| HBKID | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| HKTID | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| RZAWE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| UZAWE | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
| SWTXT1 | Character field, length 70 | CHAR70 | CHAR | 70 | CHAR70 | ||||
| SWTXT2 | Character field, length 70 | CHAR70 | CHAR | 70 | CHAR70 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RFC_PRA using ABAP code?
As RFC_PRA is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on RFC_PRA as there is no data to select.How to access SAP table RFC_PRA
Within an ECC or HANA version of SAP you can also view further information about RFC_PRA and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects