VTBKORES_TEXT SAP (Correspondence: VTBKORES + Text and Editing Fields) Structure details
Dictionary Type: Structure
Description: Correspondence: VTBKORES + Text and Editing Fields
Description: Correspondence: VTBKORES + Text and Editing Fields
ABAP Code to SELECT data from VTBKORES_TEXT
Related tables to VTBKORES_TEXT
Access table VTBKORES_TEXT
Related tables to VTBKORES_TEXT
Access table VTBKORES_TEXT
Structure field list including key, data, relationships and ABAP select examples
VTBKORES_TEXT 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 "Correspondence: VTBKORES + Text and Editing Fields" 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_VTBKORES_TEXT TYPE VTBKORES_TEXT.
The VTBKORES_TEXT table consists of various fields, each holding specific information or linking keys about Correspondence: VTBKORES + Text and Editing Fields data available in SAP. These include MANDT (Client), BUKRS (Company Code), RFHA (Financial Transaction), RFHAZU (Transaction activity).. 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: Can be enhanced (character-type or numeric)
SAP VTBKORES_TEXT 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| RFHA | Financial Transaction | TB_RFHA | CHAR | 13 | VTBFHA | ALPHA | T_RFHA | FAN | VTBA |
| RFHAZU | Transaction activity | TB_RFHAZU | NUMC | 5 | T_RFHAZU | FAS | |||
| RORDER | Order key | RORDER | CHAR | 12 | RORDER | ||||
| DCRDAT | Entered On | TB_DCRDAT | DATS | 8 | DATUM | ||||
| TCTRIM | Entry Time | TB_TCRTIM | TIMS | 6 | UZEIT | ||||
| RLFDNR | Sequential No. VRBKORES Data Record per Activity (Key Field) | TB_RLFDNR | NUMC | 2 | T_LFDNR2 | ||||
| SPLAN | Planned record | TB_SPLAN | CHAR | 1 | XFELD | ||||
| SFGZUSTT | Transaction Activity Category | TB_SFGZUTY | NUMC | 2 | Assigned to domain | T_SFGZUTY | C_AT02 | ||
| SFUNKTL | Latest function used in editing activity | TB_SFUNKTL | CHAR | 4 | Assigned to domain | T_FUNKTION | |||
| CORTYP | Correspondence type | TB_CORTYP | CHAR | 3 | AT81 | T_CORTYP | T80 | ||
| SPRINT | Correspondence medium: print | TB_SPRINT | CHAR | 1 | XFELD | ||||
| SFAX | Correspondence medium: fax | TB_SFAX | CHAR | 1 | XFELD | ||||
| SSWIFT | Correspondence medium: SWIFT file | TB_SSWIFT | CHAR | 1 | XFELD | ||||
| SIDOC | Correspondence medium: IDoc | TB_SIDOC | CHAR | 1 | XFELD | ||||
| SEMAIL | Correspondence Medium: Internet Mail | TB_SEMAIL | CHAR | 1 | XFELD | ||||
| DCIDAT | Date scheduled | TB_DCIDAT | DATS | 8 | DATUM | ||||
| TCIDAT | Dispatch time | TB_TCIDAT | TIMS | 6 | UZEIT | ||||
| JSENDEN | Send correspondence | TB_JSENDEN | CHAR | 1 | XFELD | ||||
| DEXDAT | Execution date | TB_DEXDAT | DATS | 8 | DATUM | ||||
| TEXDAT | Execution time | TB_TEXDAT | TIMS | 6 | UZEIT | ||||
| UEXNAM | User | TB_UEXNAM | CHAR | 12 | USNAM | ||||
| TDSPOOLID | Spool request number | RSPOID | INT4 | 10 | RSPOID | ||||
| TDOBJ_NO | Object: Number from ID | SO_OBJ_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
| SRECONFIRM | Counterconfirmation | TB_RECONF | NUMC | 1 | TB_RECONF | ||||
| DREDAT | Counterconfirmation Date | TB_DREDAT | DATS | 8 | DATUM | ||||
| TREDAT | Counterconfirmation time | TB_TREDAT | TIMS | 6 | UZEIT | ||||
| URENAM | Counterconfirmation Executed by (User Responsible) | TB_URENAM | CHAR | 12 | USNAM | ||||
| FORMULAR | Form Name | TDFORM | CHAR | 16 | TDFORM | ||||
| SWIFT_DAT | Format for SWIFT files | TB_SWI_DAT | CHAR | 8 | TB_SWI_DAT | ||||
| KONTRH | Business Partner Number | TB_KUNNR_NEW | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| ROLETYP | Business Partner Role | TB_CORR_ROLETYP | CHAR | 6 | Assigned to domain | BU_ROLE | BUPA_ROLE | ||
| URCNAM | Recipient | TB_URCNAM | CHAR | 12 | UNAME | ||||
| CORR_AD | Alternative Address for Correspondence | TB_CORR_A | CHAR | 10 | Assigned to domain | BU_ADRKIND | |||
| CRUSER | Entered by | TB_CRUSER | CHAR | 12 | SYCHAR12 | ||||
| UPUSER | Last Changed by | TB_UPUSER | CHAR | 12 | SYCHAR12 | ||||
| DUPDAT | Changed on | TB_DUPDAT | DATS | 8 | DATUM | ||||
| TUPTIM | Time changed | TB_TUPTIM | TIMS | 6 | UZEIT | ||||
| JAUTOMAT | Entry generated automatically when correspondence is created | TB_JAUTOM | CHAR | 1 | XFELD | ||||
| CORAUT | Generate correspondence automatically | TB_CORAUT | CHAR | 1 | XFELD | ||||
| SSTATUS | Status relevance indicator | TB_STCORR | CHAR | 1 | XFELD | ||||
| SSTATCHG | 'Status for outgoing confirmation' indicator modified | TB_STCHNG | CHAR | 1 | XFELD | ||||
| SREPEAT | Repeat correspondence? | TB_REPEAT | CHAR | 1 | XFELD | ||||
| LAUFD | SWIFT: Date of Confirmation Run | LAUFDT | DATS | 8 | DATUM | ||||
| LAUFI | Additional Identification | LAUFI | CHAR | 6 | LAUFI | ||||
| DTKEY | Additional field for the TemSe key fields | TDTKEY_D | CHAR | 16 | TEXT16 | ||||
| LFDNR | Sequence Number | TLFDNU | NUMC | 3 | NUMC3 | ||||
| SWIFTREF | Field 20 (with day ID) in SWIFT format: Transaction ref.no. | MT3XX_20 | CHAR | 20 | CHAR20 | ||||
| DOCNUM | Number of IDoc (Outgoing) | TB_EDI_DOCNUM_OUT | NUMC | 16 | EDI_DOCNUM | DCN | |||
| DOCNUM_IN | Number of IDoc (Incoming) | TB_EDI_DOCNUM_IN | NUMC | 16 | EDI_DOCNUM | DCN | |||
| SFORMCT | Form Category | TB_FRMCAT | NUMC | 1 | T_FRMCAT | ||||
| SANLF | Product Category | SANLF | NUMC | 3 | Assigned to domain | VVSANLF | |||
| SGSART | Product Type | VVSART | CHAR | 3 | Assigned to domain | VVSART | SAN | VVSART_APPL_BAS | |
| RANL | Security ID Number | VVRANLW | CHAR | 13 | Assigned to domain | ALPHA | WP_RANL | RAN | SECURITY_F4 |
| RLDEPO | Securities Account | VRLDEPO | CHAR | 10 | Assigned to domain | RLDEPO | DEP | ||
| XSGSART | Product description | TB_XSGSART | CHAR | 30 | T_XTEXT30 | ||||
| SFGTYP | Transaction Category | TB_SFGTYP | NUMC | 3 | Assigned to domain | T_SFGTYP | |||
| SFHAART | Financial Transaction Type | TB_SFHAART | CHAR | 3 | Assigned to domain | T_SFHAART | T02 | C_AT10 | |
| DVTRAB | Contract Conclusion Date | TB_DVTRAB | DATS | 8 | DATUM | ||||
| TVTRAB | Time of contract conclusion | TB_TVTRAB | TIMS | 6 | UZEIT | ||||
| XFATEXT | Name of Transaction Type | TB_FATEXT | CHAR | 30 | T_XTEXT30 | ||||
| XVTYP | Name of activity category | TB_XTTEXT | CHAR | 30 | TEXT30 | ||||
| XKONTRH | Name and address of business partner | TB_XKONTRH | CHAR | 80 | TEXT80 | ||||
| XRECONFIRM | Counterconfirmation | TB_XRECONFIRM | CHAR | 60 | TEXT60 | ||||
| SLIGHTS | Processing Status for Correspondence Data Records | TB_STATE_ICON | CHAR | 4 | Assigned to domain | ICON | |||
| SLIGHTS_SORT | Sort field for processing status (icon) | TB_STATE_SORTFIELD | NUMC | 4 | NUMC4 | ||||
| XSLIGHTS | Description of next processing step | TB_STATE_TEXT | CHAR | 60 | DDTEXT | ||||
| XCORR_MEDIUM | Correspondence medium | TB_XCORR_MEDIUM | CHAR | 60 | DDTEXT | ||||
| IDOC_STATUS | Status of IDoc | EDI_STATUS | CHAR | 2 | Assigned to domain | EDI_STATUS | |||
| IDOC_STATUS_ICON | Status Grouping | EDI_STGR | CHAR | 5 | CHAR5 | ||||
| IDOC_STATUS_DESCRP | Short description of object | EDI_TEXT60 | CHAR | 60 | TEXT60 | ||||
| ICON_CHECKED | Processing indicator | TB_ICON_CHECKED | CHAR | 4 | CHAR4 | ||||
| MARKFIELD | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| XFORMCT | UI: Form Category Text | TB_XFORMCT | CHAR | 60 | DDTEXT |
| Key field | Non-key field |
How do I retrieve data from SAP structure VTBKORES_TEXT using ABAP code?
As VTBKORES_TEXT 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 VTBKORES_TEXT as there is no data to select.How to access SAP table VTBKORES_TEXT
Within an ECC or HANA version of SAP you can also view further information about VTBKORES_TEXT 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