RFZUA_ERRORS SAP (Error Table for Automatic Clearing of Overpayments) Structure details
Description: Error Table for Automatic Clearing of Overpayments
Structure field list including key, data, relationships and ABAP select examples
RFZUA_ERRORS 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 "Error Table for Automatic Clearing of Overpayments" 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_RFZUA_ERRORS TYPE RFZUA_ERRORS.
The RFZUA_ERRORS table consists of various fields, each holding specific information or linking keys about Error Table for Automatic Clearing of Overpayments data available in SAP. These include BUKRS (Company Code), RANL (Contract Number), BETR (Amount in Local Currency), WAERS (Currency Key).. 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: Cannot Be Enhanced
SAP RFZUA_ERRORS 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 |
SACHB | Employee ID | RBEAR | CHAR | 12 | SYCHAR12 | ||||
BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
RANL | Contract Number | RANL | CHAR | 13 | ALPHA | RANL | RAN | ||
BETR | Amount in Local Currency | DMBTR | CURR | 13(2) | WERT7 | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
KZ | Object Type Processed During Auto. Clearing of Overpayments | TB_FZUA_OBJECT_TYPE | CHAR | 1 | T_FZUA_OBJECT_TYPE | ||||
TIMESTAMP | Time Stamp - Short Format | TZNTSTMPSL | NUMC | 15 | TSTPS | TZNTSTMPSL | |||
MSG | 0 | ||||||||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
MSGID | Message Class | SYMSGID | CHAR | 20 | ARBGB | ||||
MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV1_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
MSGV2_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
MSGV3_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
MSGV4_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
DETLEVEL | Application Log: Level of detail | BALLEVEL | CHAR | 1 | BALLEVEL | ||||
PROBCLASS | Application log: Message problem class | BALPROBCL | CHAR | 1 | BALPROBCL | ||||
ALSORT | Application log: Sort criterion/grouping | BALSORT | CHAR | 3 | CHAR3 | ||||
TIME_STMP | Application Log: Message time stamp | BALTIMSTMP | DEC | 21(7) | TZNTSTMPL | ||||
MSG_COUNT | Application Log: Cumulated message count | BALCNTCUM | INT4 | 10 | BALCOUNT | ||||
CONTEXT | 0 | ||||||||
TABNAME | Application Log: Context: DDIC structure name | BALTABNAME | CHAR | 30 | AS4TAB | DTB | |||
VALUE | Application Log: Context data | BALCVAL | CHAR | 256 | BALCVAL | ||||
PARAMS | 0 | ||||||||
T_PAR | 0 | ||||||||
CALLBACK | 0 | ||||||||
USEREXITP | Application Log: Callback: Program name | BALUEP | CHAR | 40 | PROGNAME | ||||
USEREXITF | Application Log: Callback: Routine name | BALUEF | CHAR | 30 | CHAR30 | ||||
USEREXITT | Application Log: Callback: Type (Ext. Perform, FM, etc.) | BALUET | CHAR | 1 | BALUET | ||||
ALTEXT | Application log: Standard text | BALTEXT | CHAR | 28 | CHAR28 | ||||
TRLO_MESG | 0 | ||||||||
GRUPPE | Line Number | DZEILE | NUMC | 3 | ZEILE | POS | |||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
TEXT | TR-LO error message text | TRLOMSGTXT | CHAR | 255 | TEXT255 | ||||
MSGID | Message Class | SYMSGID | CHAR | 20 | ARBGB | ||||
MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
INFO | TR-LO error message text | TRLOMSGTXT | CHAR | 255 | TEXT255 |
Key field | Non-key field |
How do I retrieve data from SAP structure RFZUA_ERRORS using ABAP code?
As RFZUA_ERRORS 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 RFZUA_ERRORS as there is no data to select.How to access SAP table RFZUA_ERRORS
Within an ECC or HANA version of SAP you can also view further information about RFZUA_ERRORS 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