CVAPI_DOC_FILE_MASS SAP (DMS: Originals of a Document for mass) Structure details
Description: DMS: Originals of a Document for mass
Related tables to CVAPI_DOC_FILE_MASS
Access table CVAPI_DOC_FILE_MASS
Structure field list including key, data, relationships and ABAP select examples
CVAPI_DOC_FILE_MASS 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 "DMS: Originals of a Document for mass" 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_CVAPI_DOC_FILE_MASS TYPE CVAPI_DOC_FILE_MASS.
The CVAPI_DOC_FILE_MASS table consists of various fields, each holding specific information or linking keys about DMS: Originals of a Document for mass data available in SAP. These include DOCNUMBER (Document number), DOCPART (Document Part), DOCVERSION (Document Version), UPDATEFLAG (Checkbox).. 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 CVAPI_DOC_FILE_MASS 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 |
| DOCTYPE | Document Type | DOKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
| DOCNUMBER | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
| DOCPART | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
| DOCVERSION | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
| UPDATEFLAG | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| APPNR | Application number | DMS_APPNR | CHAR | 5 | CHAR5 | ||||
| DAPPL | Application | DAPPL | CHAR | 3 | Assigned to domain | DAPPL | |||
| LANGU | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| ACTIVE_VERSION | Active version of the original | CV_FILE_ACT_VERSION | CHAR | 1 | XFELD | ||||
| DTTRG | Name of Data Carrier | DTTRG | CHAR | 10 | Assigned to domain | DTTRG | CV5 | ||
| STORAGE_CAT | Storage category for original files | CV_STORAGE_CAT | CHAR | 10 | CHAR10 | ||||
| PATHNAME | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
| FILENAME | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
| DESCRIPTION | Short description of the original | CV_FILE_DESCRIPTION | CHAR | 40 | TEXT40 | ||||
| LO_OBJID | Logical document | SDOK_LOID | CHAR | 32 | SDOK_DOCID | ||||
| PH_OBJID | Physical document | SDOK_PHID | CHAR | 32 | SDOK_DOCID | ||||
| FILE_ID | DVS: GUID for allocation PHIO - file name | DMS_FILE_ID | CHAR | 32 | CHAR32 | ||||
| URL | URL | DMS_URL | CHAR | 4096 | CHAR4096 | ||||
| CHECKED_IN | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| CREATED_AT | Time of change (UTC) | SDOK_CHTST | NUMC | 14 | TSTLC | SDOK_TSTMP | |||
| CHANGED_AT | Time of change (UTC) | SDOK_CHTST | NUMC | 14 | TSTLC | SDOK_TSTMP | |||
| CREATED_BY | Name of person responsible | DWNAM | CHAR | 12 | DWNAM | ||||
| CHANGED_BY | Name of person responsible | DWNAM | CHAR | 12 | DWNAM | ||||
| CONTENT_DESCRIPTION | Description content version | DMS_CONTENT_VERS_DESC | CHAR | 50 | TEXT50 |
| Key field | Non-key field |
How do I retrieve data from SAP structure CVAPI_DOC_FILE_MASS using ABAP code?
As CVAPI_DOC_FILE_MASS 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 CVAPI_DOC_FILE_MASS as there is no data to select.How to access SAP table CVAPI_DOC_FILE_MASS
Within an ECC or HANA version of SAP you can also view further information about CVAPI_DOC_FILE_MASS 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