STR_DMS_BAPI_DOC_FILES2 SAP (eSOA DMS enhancement of bapi do files2 with binary obj) Structure details
Description: eSOA DMS enhancement of bapi do files2 with binary obj
Related tables to STR_DMS_BAPI_DOC_FILES2
Access table STR_DMS_BAPI_DOC_FILES2
Structure field list including key, data, relationships and ABAP select examples
STR_DMS_BAPI_DOC_FILES2 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 "eSOA DMS enhancement of bapi do files2 with binary obj" 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_STR_DMS_BAPI_DOC_FILES2 TYPE STR_DMS_BAPI_DOC_FILES2.
The STR_DMS_BAPI_DOC_FILES2 table consists of various fields, each holding specific information or linking keys about eSOA DMS enhancement of bapi do files2 with binary obj data available in SAP. These include DELETEVALUE (Deletion Indicator), DOCUMENTTYPE (Document Type), DOCUMENTNUMBER (Document number), DOCUMENTPART (Document Part).. 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 (Deep)
SAP STR_DMS_BAPI_DOC_FILES2 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 |
DELETEVALUE | Deletion Indicator | LKENZ | CHAR | 1 | XFELD | ||||
DOCUMENTTYPE | Document Type | DOKAR | CHAR | 3 | TDWA | DOKAR | CV2 | ||
DOCUMENTNUMBER | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
DOCUMENTPART | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
DOCUMENTVERSION | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
ORIGINALTYPE | Application number | DMS_APPNR | CHAR | 5 | CHAR5 | ||||
SOURCEDATACARRIER | Name of Data Carrier | DTTRG | CHAR | 10 | Assigned to domain | DTTRG | CV5 | ||
STORAGECATEGORY | Storage category for original files | CV_STORAGE_CAT | CHAR | 10 | CHAR10 | ||||
WSAPPLICATION | Application | DAPPL | CHAR | 3 | TDWP | DAPPL | |||
DOCPATH | Path for original file | DMS_PATH | CHAR | 255 | TEXT255 | ||||
DOCFILE | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
STATUSINTERN | Document Status | DOKST | CHAR | 2 | Assigned to domain | DOKST | |||
STATUSEXTERN | Status of a document (language-dependent) | STABK | CHAR | 2 | CHAR2 | ||||
STATUSLOG | Document management log field | PROTF | CHAR | 20 | PROTF | ||||
APPLICATION_ID | Logical document | SDOK_LOID | CHAR | 32 | SDOK_DOCID | ||||
FILE_ID | Physical document | SDOK_PHID | CHAR | 32 | SDOK_DOCID | ||||
DESCRIPTION | Short description of the original | CV_FILE_DESCRIPTION | CHAR | 40 | TEXT40 | ||||
LANGUAGE | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
CHECKEDIN | Document is cheked In | DMS_BAPI_CHECKEDIN | CHAR | 1 | XFELD | ||||
ACTIVE_VERSION | Active version of the original | CV_FILE_ACT_VERSION | 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 STR_DMS_BAPI_DOC_FILES2 using ABAP code?
As STR_DMS_BAPI_DOC_FILES2 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 STR_DMS_BAPI_DOC_FILES2 as there is no data to select.How to access SAP table STR_DMS_BAPI_DOC_FILES2
Within an ECC or HANA version of SAP you can also view further information about STR_DMS_BAPI_DOC_FILES2 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