VVTBSTA2 SAP (Change Document Structure; Generated by RSSCD000) Structure details
Description: Change Document Structure; Generated by RSSCD000
Structure field list including key, data, relationships and ABAP select examples
VVTBSTA2 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 "Change Document Structure; Generated by RSSCD000" 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_VVTBSTA2 TYPE VVTBSTA2.
The VVTBSTA2 table consists of various fields, each holding specific information or linking keys about Change Document Structure; Generated by RSSCD000 data available in SAP. These include MANDT (Client), PARTNR (Business Partner Number), BUKRS (Company Code), RANTYP (Contract Type).. 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)
SAP VVTBSTA2 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 | |||
PARTNR | Business Partner Number | BP_PARTNR_NEW | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
RANTYP | Contract Type | RANTYP | CHAR | 1 | RANTYP | ||||
SANLF | Product Category | SANLF | NUMC | 3 | TZAF | VVSANLF | |||
SGSART | Product Type | VVSART | CHAR | 3 | TZPA | VVSART | SAN | VVSART_APPL_BAS | |
SFHAART | Financial Transaction Type | TB_SFHAART | CHAR | 3 | AT10 | T_SFHAART | T02 | C_AT10 | |
CORTYP | Correspondence type | TB_CORTYP | CHAR | 3 | AT81 | T_CORTYP | T80 | ||
DCRDAT | Entered On | TB_DCRDAT | DATS | 8 | DATUM | ||||
TCRTIM | Entry Time | TB_TCRTIM | TIMS | 6 | UZEIT | ||||
CRUSER | Entered by | TB_CRUSER | CHAR | 12 | SYCHAR12 | ||||
DUPDAT | Changed on | TB_DUPDAT | DATS | 8 | DATUM | ||||
TUPTIM | Time changed | TB_TUPTIM | TIMS | 6 | UZEIT | ||||
UPUSER | Last Changed by | TB_UPUSER | CHAR | 12 | SYCHAR12 | ||||
CORR_PR | Print Correspondence | TB_CORR_PR | CHAR | 1 | XFELD | ||||
CORR_FX | Fax Correspondence | TB_CORR_FX | CHAR | 1 | XFELD | ||||
CORR_SW | Generate Correspondence SWIFT File | TB_CORR_SW | CHAR | 1 | XFELD | ||||
CORR_ID | Generate Correspondence IDoc | TB_CORR_ID | CHAR | 1 | XFELD | ||||
CORR_EM | Activate Correspondence for E-Mail | TB_CORR_EM | CHAR | 1 | XFELD | ||||
CORR_AD | Alternative Address for Correspondence | TB_CORR_AD_NEW | CHAR | 10 | TB009 | BU_ADRKIND | |||
CORR_STAT | Principal correspondence medium for correspondence status | TB_CORR_ST | CHAR | 1 | TB_CORR_ST | ||||
SOBLRECONF | Counterconfirmation required? | TB_OBLRECO | CHAR | 1 | XFELD | ||||
SNODUNNING | Block dunning? (no application) | TB_NODUNNG | CHAR | 1 | XFELD | ||||
REPL_RE | Indicator: Correspondence reply required | TB_REPL_RE | CHAR | 1 | XFELD | ||||
REPL_TI | Period in days for correspondence reply | TB_REPL_TI | NUMC | 2 | TB_REPL_TI | ||||
REPL_KU | Grace period in days for correspondence reply | TB_REPL_KU | NUMC | 2 | TB_REPL_KU | ||||
KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
Key field | Non-key field |
How do I retrieve data from SAP structure VVTBSTA2 using ABAP code?
As VVTBSTA2 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 VVTBSTA2 as there is no data to select.How to access SAP table VVTBSTA2
Within an ECC or HANA version of SAP you can also view further information about VVTBSTA2 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