CMS_STR_COR_REQ_DATA SAP (Correspondence request data) Structure details
Dictionary Type: Structure
Description: Correspondence request data
Description: Correspondence request data
ABAP Code to SELECT data from CMS_STR_COR_REQ_DATA
Related tables to CMS_STR_COR_REQ_DATA
Access table CMS_STR_COR_REQ_DATA
Related tables to CMS_STR_COR_REQ_DATA
Access table CMS_STR_COR_REQ_DATA
Structure field list including key, data, relationships and ABAP select examples
CMS_STR_COR_REQ_DATA 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 "Correspondence request data" 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_CMS_STR_COR_REQ_DATA TYPE CMS_STR_COR_REQ_DATA.
The CMS_STR_COR_REQ_DATA table consists of various fields, each holding specific information or linking keys about Correspondence request data data available in SAP. These include OBJECT_IDCMS (Object Identification Number), FLG_ORIGINALCMS (Flag to indicate if the document is original or duplicate), SENDCONTROLCMS (Dispatch Control), COTYP (Correspondence Type).. 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 CMS_STR_COR_REQ_DATA 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 |
| .INCLU-CMS | 0 | ||||||||
| OBJECT_IDCMS | Object Identification Number | CMS_DTE_OBJECT_ID | RAW | 16 | SYSUUID | ||||
| FLG_ORIGINALCMS | Flag to indicate if the document is original or duplicate | CMS_DTE_FLG_ORIG | CHAR | 1 | CMS_FLG | ||||
| SENDCONTROLCMS | Dispatch Control | SENDCONTROL | CHAR | 4 | Assigned to domain | ESENDCONTROL | |||
| COTYP | Correspondence Type | COTYP_KK | CHAR | 4 | Assigned to domain | COTYP_KK | COTYP | COTYP_KK | |
| COKEY | Correspondence key | COKEY_KK | CHAR | 36 | COKEY_KK | ||||
| UNAME | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
| CDATE | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| CTIME | TIME Data Element for SYST | SYTIME | TIMS | 6 | SYTIME | ||||
| GPART | Correspondence Recipient | CREC_GP_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | ||
| ORG_GPART | Original Correspondence Recipient | CREC_ORG_GP_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | ||
| VKONT | Contract Account Number | CORR_VKONT_KK | CHAR | 12 | ALPHA | CORR_VKONT_KK | |||
| VTREF | Reference Specifications from Contract | CORR_VTREF_KK | CHAR | 20 | ALPHA | CORR_VTREF_KK | |||
| ADRNR | Address Number of Correspondence Recipient | CREC_AD_KK | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ||
| AGPART | Sending Business Partner | CSEN_GP_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | ||
| AADRNR | Address Number of Correspondence Sender | CSEN_AD_KK | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ||
| FORMKEY | Application form | FORMKEY | CHAR | 30 | Assigned to domain | FORMKEY | FOM | ||
| FORMKEY_RDI | Application form | FORMKEY | CHAR | 30 | Assigned to domain | FORMKEY | FOM | ||
| ENTID1 | Correspondence data | ENTID_KK | CHAR | 4 | Assigned to domain | ENTID_KK | |||
| DATA1 | Correspondence Data Field | CDATA_KK | CHAR | 32 | CDATA_KK | ||||
| ENTID2 | Correspondence data | ENTID_KK | CHAR | 4 | Assigned to domain | ENTID_KK | |||
| DATA2 | Correspondence Data Field | CDATA_KK | CHAR | 32 | CDATA_KK | ||||
| ENTID3 | Correspondence data | ENTID_KK | CHAR | 4 | Assigned to domain | ENTID_KK | |||
| DATA3 | Correspondence Data Field | CDATA_KK | CHAR | 32 | CDATA_KK | ||||
| ENTID4 | Correspondence data | ENTID_KK | CHAR | 4 | Assigned to domain | ENTID_KK | |||
| DATA4 | Correspondence Data Field | CDATA_KK | CHAR | 32 | CDATA_KK | ||||
| CSORT | Correspondence Sort Field | CSORT_KK | CHAR | 50 | CORR_TXT50 | ||||
| XCODT | Data Part Is Used | XCODT_KK | CHAR | 1 | XFELD | ||||
| XCODT_CLUST | Cluster Data Part is Used | XCODT_CLUST_KK | CHAR | 1 | XFELD | ||||
| LAUFD | Date ID for Creation Run | CORR_LAUFD_KK | DATS | 8 | DATUM | ||||
| LAUFI | Additional ID Characteristic for Creation Run | CORR_LAUFI_KK | CHAR | 6 | CORR_LAUFI_KK | ||||
| XTEST | Correspondence is Result of Test | XTEST_KK | CHAR | 1 | XFELD | ||||
| COPRI | Print Date | COPRI_KK | DATS | 8 | SYDATS | ||||
| COIDT | Date of Issue | COIDT_KK | DATS | 8 | SYDATS | ||||
| COITM | Issue Time to the Second | COITM_KK | TIMS | 6 | SYTIME | ||||
| SPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| SALWA | Transaction Currency | CORR_BLWAE_KK | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| SALBE | Amount in Local Currency with +/- Signs | CORR_BETRH_KK | CURR | 13(2) | WRTV7 | ||||
| SENDCONTROL | Dispatch Control | SENDCONTROL | CHAR | 4 | ESENDCONTROL | ESENDCONTROL | |||
| PERSNUMBER | Person number | AD_PERSNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_PERSNUM | CDT | ADDRESS |
| BUKRS | Company Code in Correspondence | CORR_BUKRS | CHAR | 4 | CORR_BUKRS | ||||
| CORR_ROLE | Correspondence Roles | CORR_ROLE_KK | CHAR | 4 | TFK070M | CORR_ROLE_KK | |||
| COPRI_LAUFD | Date ID for Print Run | COPRI_LAUFD_KK | DATS | 8 | DATUM | ||||
| COPRI_LAUFI | ID Characteristic for Run | COPRI_LAUFID_KK | CHAR | 6 | COPRI_LAUFID_KK | ||||
| XTRIAL | Correspondence Request is Test | XTRIAL_KK | CHAR | 1 | XFELD | ||||
| XREPRINT | Recreate Correspondence | XREPRINT_KK | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure CMS_STR_COR_REQ_DATA using ABAP code?
As CMS_STR_COR_REQ_DATA 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 CMS_STR_COR_REQ_DATA as there is no data to select.How to access SAP table CMS_STR_COR_REQ_DATA
Within an ECC or HANA version of SAP you can also view further information about CMS_STR_COR_REQ_DATA 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