/BEV3/CHDKOM2 SAP (Contract Document Communication Structure 2 (DRAD)) Structure details
Description: Contract Document Communication Structure 2 (DRAD)
Related tables to /BEV3/CHDKOM2
Access table /BEV3/CHDKOM2
Structure field list including key, data, relationships and ABAP select examples
/BEV3/CHDKOM2 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 "Contract Document Communication Structure 2 (DRAD)" 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_/BEV3/CHDKOM2 TYPE /BEV3/CHDKOM2.
The /BEV3/CHDKOM2 table consists of various fields, each holding specific information or linking keys about Contract Document Communication Structure 2 (DRAD) data available in SAP. These include VWDART (Contract Handling Document Type), YVWDNR (CHD Contract Number), MUSTER (Model Indicator), OBJNR (Key for Objects).. 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 /BEV3/CHDKOM2 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 |
| YVORGE | CH Organizational Unit | /BEV3/CHOE | NUMC | 4 | /BEV3/CHTBVORGE | /BEV3/CHDOVORGE | /BEV3/CHYOE | ||
| VWDART | Contract Handling Document Type | /BEV3/CHDTVWDART | NUMC | 4 | /BEV3/CHTVWDART | /BEV3/CHDOVWDART | /BEV3/CHT | ||
| YVWDNR | CHD Contract Number | /BEV3/CHDTWDNR | NUMC | 13 | /BEV3/CHDOWDNR | /BEV3/CHW | /BEV3/CHHNODESTH | ||
| MUSTER | Model Indicator | /BEV3/CHMUSTER | CHAR | 1 | /BEV3/CHTXT01 | /BEV3/CHMUSTER | |||
| OBJNR | Key for Objects | /BEV3/CHOBJNR | NUMC | 14 | /BEV3/CHTOBJ | /BEV3/CHOBJNR | /BEV3/CHO | /BEV3/CHOBJ | |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| DOKAR | Document Type | DOKAR | CHAR | 3 | TDWA | DOKAR | CV2 | ||
| DOKNR | Document number | DOKNR | CHAR | 25 | DRAW | ALPHA | DOKNR | CV1 | |
| DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
| DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
| DOKOB | Linked SAP Object | DOKOB | CHAR | 10 | TDWO | DOKOB | |||
| OBZAE | Counter key | OBZAE | NUMC | 4 | NUM4 | ||||
| OBJKY | Document management object key | OBJKY | CHAR | 50 | CHAR50 | ||||
| VRKSTAT | Link status of a document | VRKSTAT | CHAR | 1 | VRKSTAT | ||||
| VRKSTAT1 | Object link status for document | STAT_OBVK | CHAR | 2 | VRKSTAT1 | ||||
| VOBJ | Name of database table for object | TABELLE | CHAR | 30 | TCLO | OBJEKTTAB | OTA | ||
| VKEY | Document management object key | OBJKY | CHAR | 50 | CHAR50 | ||||
| VDIR | Direction of document link active | DRADDIR | CHAR | 1 | XFELD | ||||
| VIEWFLAG | Indicator: default document for view | CV_VIEW_FLAG | CHAR | 1 | XFELD | ||||
| DELFLAG | Deletion indicator: object link | DEL_DRAD_FLAG | CHAR | 1 | |||||
| LONGTEXT_ID | DMS: GUID for allocation of long texts | LONGTEXT_ID | CHAR | 32 | CHAR32 | ||||
| CAD_POS | CAD: Assignment document <-> material | CAD_POS | CHAR | 1 | |||||
| CM_FIXED | Document fixed | DMS_CM_FIXED | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure /BEV3/CHDKOM2 using ABAP code?
As /BEV3/CHDKOM2 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 /BEV3/CHDKOM2 as there is no data to select.How to access SAP table /BEV3/CHDKOM2
Within an ECC or HANA version of SAP you can also view further information about /BEV3/CHDKOM2 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