API_DRAD SAP (Document-Object Link) Structure details
Description: Document-Object Link
Structure field list including key, data, relationships and ABAP select examples
API_DRAD 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 "Document-Object Link" 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_API_DRAD TYPE API_DRAD.
The API_DRAD table consists of various fields, each holding specific information or linking keys about Document-Object Link data available in SAP. These include AENNR (Change Number), MANDT (Client), DOKAR (Document Type), DOKNR (Document number).. 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: Not classified
SAP API_DRAD 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 |
| PVGUID | Internal Number of the PVS Variant | PVS_PVGUID | RAW | 16 | SYSUUID | ||||
| AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| DOKAR | Document Type | DOKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
| DOKNR | Document number | DOKNR | CHAR | 25 | Assigned to domain | 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 | Assigned to domain | 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 | Assigned to domain | 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 | ||||
| UPDKZ | Update indicator | UPDKZ_D | CHAR | 1 | UPDKZ |
| Key field | Non-key field |
How do I retrieve data from SAP structure API_DRAD using ABAP code?
As API_DRAD 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 API_DRAD as there is no data to select.How to access SAP table API_DRAD
Within an ECC or HANA version of SAP you can also view further information about API_DRAD 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