EAUSVD SAP (Screen Fields: Move-out Proc for Contract) Structure details
Description: Screen Fields: Move-out Proc for Contract
Structure field list including key, data, relationships and ABAP select examples
EAUSVD 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 "Screen Fields: Move-out Proc for Contract" 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_EAUSVD TYPE EAUSVD.
The EAUSVD table consists of various fields, each holding specific information or linking keys about Screen Fields: Move-out Proc for Contract data available in SAP. These include MANDT (Client), AUSZBELEG (Consecutive number of move-out document), VERTRAG (Contract), VBEZ (Text for contract).. 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 EAUSVD 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 | |||
| AUSZBELEG | Consecutive number of move-out document | AUSZBELEG | CHAR | 12 | ALPHA | AUSZBELEG | EMO | EAUS | |
| VERTRAG | Contract | VERTRAG | CHAR | 10 | EVER | ALPHA | VERTRAG | VTG | EVER |
| VBEZ | Text for contract | E_VBEZ | CHAR | 35 | TEXT35 | ||||
| ANLAGE | Installation | ANLAGE | CHAR | 10 | EANL | ALPHA | ANLAGE | ANL | EANL |
| VSTELLE | Premise | VSTELLE | CHAR | 10 | EVBS | ALPHA | VSTELLE | VBS | EVBS |
| VBSADR | Premise address | VBSADR | CHAR | 80 | LINES | ||||
| OHNEEINZ | Move-out w/o move-in | OHNEEINZ | CHAR | 2 | EOHNEEINZ | OHNEEINZ | |||
| OHNEEINZT | Text for reason for move-out without move-in | OHNEEINZT | CHAR | 30 | TEXT30 | ||||
| MAHNV | Dunning Procedure | MAHNV_KK | CHAR | 2 | TFK047A | MAHNV_KK | FKK_MAHNV | ||
| MAHNVT | Dunning procedure text | TX007_KK | CHAR | 50 | TXT50 | ||||
| MANSP | Dunning Lock Reason | MANSP_KK | CHAR | 1 | TFK047S | MANSP_KK | |||
| MANSPT | Name of Dunning Lock Reason | TX008_KK | CHAR | 50 | TXT50 | ||||
| AUSZDAT | Move-Out Date | AUSZDAT | DATS | 8 | DATUM | ||||
| AUSZSTAT | Status of move-out processing | AUSZSTAT | CHAR | 2 | AUSZSTAT | ||||
| AUSZSTATT | Text for status of move-out processing | AUSZSTATT | CHAR | 60 | AS4TEXT | ||||
| WORKIT | Indicator: work items exist | WORKIT | CHAR | 1 | KENNZX | ||||
| AKLASSE | Billing class | AKLASSE | CHAR | 4 | EAKLASSE | AKLASSE | AKL | ||
| AKLASSET | Text for billing class | AKLASSETXT | CHAR | 30 | TEXT30 | ||||
| SPARTE | Division | SPARTE | CHAR | 2 | TSPA | SPART | SPA | ||
| SPARTET | Name | VTXTK | CHAR | 20 | TEXT20 | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| BUKRST | Name of Company Code or Company | BUTXT | CHAR | 25 | TEXT25 | ||||
| ANLART | Installation type | ANLART | CHAR | 4 | TE439 | ANLART | |||
| ANLARTT | Text for installation type | ANLARTTEXT | CHAR | 30 | TEXT30 | ||||
| VBSART | Type of premise | VBSART | CHAR | 8 | TE102 | VBSART | |||
| VBSARTT | Text for premise type | VBSARTTEXT | CHAR | 40 | TEXT40 | ||||
| KOFIZ | Account determination ID for IS-U contracts | E_KOFIZ | CHAR | 2 | TE097 | E_KOFIZ | KMM | ||
| KOFIZT | Text for account determination ID | KOFIZTEXT | CHAR | 50 | TEXT50 | ||||
| GEMFAKT | Invoice Contracts Jointly (Mandatory Contracts) | E_GEMFAKT | CHAR | 1 | E_GEMFAKT | ||||
| PYPLT | Payment plan type | E_PYPLT | CHAR | 4 | Assigned to domain | E_PYPLT | PYPT | ||
| PYPLTT | Text (30 Characters) | TEXT30 | CHAR | 30 | TEXT30 | ||||
| PYPLS | Starting month of payment plan | E_PYPLS | NUMC | 2 | MONTH | PYPS | |||
| BEZUG | Reference | BEZUG | CHAR | 1 | KENNZX | ||||
| EIGENVERBR | Plant or company consumption | EIGENVERBR | CHAR | 1 | EIGENVERBR | ||||
| MANABR | Bill contract manually | MANABR | CHAR | 1 | KENNZX | ||||
| PAUSCHAL | Device allocation is not possible | E_PAUSCHAL | CHAR | 1 | KENNZX | ||||
| EIGENT | Owner | E_GPARTNER | CHAR | 10 | BUT000 | ALPHA | BU_PARTNER | BPA | BUPA |
| NAMEEIGENT | Text for business partner | TEXT1GP_KK | CHAR | 132 | TEXT132 | ||||
| MANOUTSORT | Reason for manual outsorting in billing | MANOUTSORT | CHAR | 8 | TE127 | MANOUTSORT | |||
| MANOUTSRTT | Text for manual outsorting | MANOUTTEXT | CHAR | 30 | CHAR30 |
| Key field | Non-key field |
How do I retrieve data from SAP structure EAUSVD using ABAP code?
As EAUSVD 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 EAUSVD as there is no data to select.How to access SAP table EAUSVD
Within an ECC or HANA version of SAP you can also view further information about EAUSVD 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