VEPATTR SAP (Attribute of a Virtual Interface) Structure details
Description: Attribute of a Virtual Interface
Structure field list including key, data, relationships and ABAP select examples
VEPATTR 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 "Attribute of a Virtual Interface" 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_VEPATTR TYPE VEPATTR.
The VEPATTR table consists of various fields, each holding specific information or linking keys about Attribute of a Virtual Interface data available in SAP. These include VEPNAME (Name of a Service Definition), VERSION (ABAP: Program Status (Active, Saved, Transported...)), SIESRNAME (Service Definition name for ESR), VEPNAMEEXT (External Name of a Service Definition (Uppercase/Lowercase)).. 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 VEPATTR 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 |
| VEPNAME | Name of a Service Definition | VEPNAME | CHAR | 30 | SHLP_ER_WEBSERVICE_NAME | ||||
| VERSION | ABAP: Program Status (Active, Saved, Transported...) | R3STATE | CHAR | 1 | R3STATE | ||||
| SIESRNAME | Service Definition name for ESR | VEPNAMEESR | CHAR | 255 | VEPNAMEESR | ||||
| VEPNAMEEXT | External Name of a Service Definition (Uppercase/Lowercase) | VEPNAMEEXT | CHAR | 30 | VEPNAMEEXT | ||||
| AUTHOR | Author | CNAM | CHAR | 12 | SYCHAR12 | ||||
| CREATEDON | Created on | RDIR_CDATE | DATS | 8 | SYDATS | ||||
| CHANGEDBY | Last changed by | UNAM | CHAR | 12 | SYCHAR12 | ||||
| CHANGEDON | Changed On | RDIR_UDATE | DATS | 8 | SYDATS | ||||
| DEFAULT_MAPPING | Name Mapping | WSMAPPING | CHAR | 1 | CHAR1 | ||||
| FROZEN | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| LOCKED | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| TEXT_ID | Key for Logical Object in the OTR | SOTR_CONC | CHAR | 32 | SYSUUID_C | ||||
| DOCU_ID | Key for Logical Object in the OTR | SOTR_CONC | CHAR | 32 | SYSUUID_C | ||||
| CTIME | WebServices: Creation Time | WS_CTIME | TIMS | 6 | UZEIT | ||||
| UTIME | WebServices: Change Time | WS_UTIME | TIMS | 6 | UZEIT | ||||
| WSINT_VERSION | Internal Version of Service | WSINT_VERSION | CHAR | 3 | WSINT_VERSION | ||||
| DEVCLASS | Package | DEVCLASS | CHAR | 30 | Assigned to domain | DEVCLASS | DVC | DEVCLASS | |
| ORIGLANGU | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| MODLANGU | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| TEXT | Short Description | VEPTEXT | CHAR | 255 | VEPTEXT | ||||
| REFTO | Reference to Development Object (End Point) | VEPREFTO | CHAR | 30 | CHAR30 | ||||
| VEPREFTYPE | Object Type of Reference Object (Function, BAPI, IDOC) | VEPREFTYPE | CHAR | 4 | Assigned to domain | VEPREFTYPE | |||
| NEED_OWN_DIALOG | Boolean Variable (X=True, -=False, Space=Unknown) | BOOLEAN | CHAR | 1 | BOOLEAN | ||||
| REFTOTEXT | Type of Original Object of a Service Definition | REFTOTEXT | CHAR | 60 | TEXT60 | ||||
| OBJTXT | Text (20 Characters) | TEXT20 | CHAR | 20 | TEXT20 | ||||
| NAMESPACE | SOAP Namespace of a Service Definition | VEPSOAPNAMESPACE | CHAR | 255 | VEPSOAPNAMESPACE |
| Key field | Non-key field |
How do I retrieve data from SAP structure VEPATTR using ABAP code?
As VEPATTR 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 VEPATTR as there is no data to select.How to access SAP table VEPATTR
Within an ECC or HANA version of SAP you can also view further information about VEPATTR 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