VXVEPENDPOINT SAP (Delta for VEPENDPOINT) Structure details
Description: Delta for VEPENDPOINT
Related tables to VXVEPENDPOINT
Access table VXVEPENDPOINT
Structure field list including key, data, relationships and ABAP select examples
VXVEPENDPOINT 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 "Delta for VEPENDPOINT" 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_VXVEPENDPOINT TYPE VXVEPENDPOINT.
The VXVEPENDPOINT table consists of various fields, each holding specific information or linking keys about Delta for VEPENDPOINT data available in SAP. These include VRSFLAG (CHAR04 data element for SYST), RELID (Relation ID), VEPNAME (Name of a Service Definition), VERSION (ABAP: Program Status (Active, Saved, Transported...)).. 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 VXVEPENDPOINT 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 |
| VRSFLAG | CHAR04 data element for SYST | SYCHAR04 | CHAR | 4 | SYCHAR04 | ||||
| RELID | Relation ID | RELID | CHAR | 2 | RELID | ||||
| VEPNAME | Name of a Service Definition | VEPNAME | CHAR | 30 | SHLP_ER_WEBSERVICE_NAME | ||||
| VERSION | ABAP: Program Status (Active, Saved, Transported...) | R3STATE | CHAR | 1 | R3STATE | ||||
| SORTFIELD | Continuation ID | SRTF2 | INT4 | 10 | SYBIN4 | ||||
| ENDPOINTTYPE | Object Type of Reference Object (Function, BAPI, IDOC) | VEPREFTYPE | CHAR | 4 | Assigned to domain | VEPREFTYPE | |||
| DATA_VERSION | Version of Endpoint Data Unit | VIFENDPOINTDATAVERS | CHAR | 10 | CHAR10 | ||||
| DEF_START_PT | Starting Point for Service Def. (Inside-Out or Outside-In) | DEF_START_PT | CHAR | 1 | DEF_START_PT | ||||
| AUTO_GENERATED | Endpoint was generated automatically | AUTO_GENERATED | CHAR | 1 | BOOLEAN | ||||
| IS_SRVV | Endpoint was generated automatically | SEWS_IS_SRVV | CHAR | 1 | BOOLEAN | ||||
| ENDPOINTNAME | Reference to Development Object (End Point) | VEPREFTO | CHAR | 30 | CHAR30 | ||||
| CLUSTR | BIN2 data element for SYST | SYBIN2 | INT2 | 5 | SYBIN2 | ||||
| CLUSTD | EU cluster field 3500 for INDX-like tables | EU_LRAW | LRAW | 3500 | EU_LRAW |
| Key field | Non-key field |
How do I retrieve data from SAP structure VXVEPENDPOINT using ABAP code?
As VXVEPENDPOINT 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 VXVEPENDPOINT as there is no data to select.How to access SAP table VXVEPENDPOINT
Within an ECC or HANA version of SAP you can also view further information about VXVEPENDPOINT 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