DMS_ESO_KPRO_ORIGINAL_VERSION SAP (ZMUE_ESO_DMS_ORIGINAL_VERSION) Structure details
Description: ZMUE_ESO_DMS_ORIGINAL_VERSION
Related tables to DMS_ESO_KPRO_ORIGINAL_VERSION
Access table DMS_ESO_KPRO_ORIGINAL_VERSION
Structure field list including key, data, relationships and ABAP select examples
DMS_ESO_KPRO_ORIGINAL_VERSION 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 "ZMUE_ESO_DMS_ORIGINAL_VERSION" 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_DMS_ESO_KPRO_ORIGINAL_VERSION TYPE DMS_ESO_KPRO_ORIGINAL_VERSION.
The DMS_ESO_KPRO_ORIGINAL_VERSION table consists of various fields, each holding specific information or linking keys about ZMUE_ESO_DMS_ORIGINAL_VERSION data available in SAP. These include PHIO_ID (Physical document), LANGUAGE (Language Key), LO_CLASS (Class of logical document), LOIO_ID (Logical document).. 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 DMS_ESO_KPRO_ORIGINAL_VERSION 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 |
PH_CLASS | Physical document class | SDOK_PHCL | CHAR | 10 | Assigned to domain | SDOK_CLASS | |||
PHIO_ID | Physical document | SDOK_PHID | CHAR | 32 | SDOK_DOCID | ||||
LANGUAGE | Language Key | LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
LO_CLASS | Class of logical document | SDOK_LOCL | CHAR | 10 | Assigned to domain | SDOK_CLASS | |||
LOIO_ID | Logical document | SDOK_LOID | CHAR | 32 | SDOK_DOCID | ||||
CONTENT_DESC | Description content version | DMS_CONTENT_VERS_DESC | CHAR | 50 | TEXT50 | ||||
MIME_TYPE | HTML content type | W3CONTTYPE | CHAR | 128 | W3_CONTTYP | ||||
FILE_SIZE | File size (in bytes) | SDOK_FSIZE | NUMC | 12 | SDOK_FSIZE | ||||
FILE_NAME | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
FILE_TYPE | Type of data transfer | SDOK_TRFMD | CHAR | 1 | SDOK_TRFMD | ||||
ACTIVE_VERSION | Document Management Flag | CVFLAG | CHAR | 1 | CHAR1 | ||||
STORAGE_CAT | Category for physical documents | SDOK_STCAT | CHAR | 10 | Assigned to domain | SDOK_STCAT | |||
DRAW_DTTRG | Name of Data Carrier | DTTRG | CHAR | 10 | Assigned to domain | DTTRG | CV5 | ||
STATUS | Document Status | DOKST | CHAR | 2 | Assigned to domain | DOKST | |||
STATUS_NR | Counter key DRAP | STZAE | NUMC | 4 | NUM4 | ||||
CHECKED_OUT | Document Management Flag | CVFLAG | CHAR | 1 | CHAR1 | ||||
CHECKOUT_USER | Name of person responsible | DWNAM | CHAR | 12 | DWNAM | ||||
CREATE_USER | Created by | SDOK_CRUSR | CHAR | 12 | USERNAME | ||||
CREATE_TIMESTAMP | Create Timestamp | DMS_ESO_CREATE_TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
LAST_CHANGE_USER | Last changed by | SDOK_CHUSR | CHAR | 12 | USERNAME | ||||
LAST_CHANGE_TIMESTAMP | Change Timestamp | DMS_ESO_CHANGE_TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
URL | URL of KPRO document | ESH_E_KPRO_URL | STRG | 0 | ESH_D_KPRO_URL |
Key field | Non-key field |
How do I retrieve data from SAP structure DMS_ESO_KPRO_ORIGINAL_VERSION using ABAP code?
As DMS_ESO_KPRO_ORIGINAL_VERSION 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 DMS_ESO_KPRO_ORIGINAL_VERSION as there is no data to select.How to access SAP table DMS_ESO_KPRO_ORIGINAL_VERSION
Within an ECC or HANA version of SAP you can also view further information about DMS_ESO_KPRO_ORIGINAL_VERSION 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