TCORS_ALERT_CORRES SAP (Correspondence required alert) Structure details
Description: Correspondence required alert
Related tables to TCORS_ALERT_CORRES
Access table TCORS_ALERT_CORRES
Structure field list including key, data, relationships and ABAP select examples
TCORS_ALERT_CORRES 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 required alert" 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_TCORS_ALERT_CORRES TYPE TCORS_ALERT_CORRES.
The TCORS_ALERT_CORRES table consists of various fields, each holding specific information or linking keys about Correspondence required alert data available in SAP. These include DEALNUMBER (Financial Transaction), SEC_ACC (Securities Account), CO_KEY (Semantic key for Corr), CO_UUID (Correspondence Object UUID).. 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 TCORS_ALERT_CORRES 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 |
COMPANY_CODE | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
DEALNUMBER | Financial Transaction | TB_RFHA | CHAR | 13 | Assigned to domain | ALPHA | T_RFHA | FAN | VTBA |
SEC_ACC | Securities Account | RLDEPO | CHAR | 10 | Assigned to domain | RLDEPO | DEP | ACC_CCD_CORE | |
CO_KEY | Semantic key for Corr | FTR_CO_KEY | CHAR | 16 | ALPHA | FTR_CO_KEY | TCORH_COKEY | ||
CO_UUID | Correspondence Object UUID | FTR_COID | RAW | 16 | |||||
BPGROUP | Business Partner Group ID | FTR_BPGRP | CHAR | 15 | Assigned to domain | FTR_BPGRP | |||
PROFILE | Correspondence Profile | FTR_PROFILE | CHAR | 15 | Assigned to domain | FTR_PROFILE | |||
RECIPIENT_TYPE | Recipient/Sender Type | FTR_RECIPIENT_TYPE | CHAR | 15 | Assigned to domain | FTR_RECIPIENT_TYPE | |||
RECIPIENT | Correspondence Recipient | FTR_RECIPIENT | CHAR | 10 | ALPHA | FTR_RECIPIENT | |||
FUNCTION | Correspondence Class | FTR_FUNCTION | CHAR | 15 | Assigned to domain | FTR_FUNCTION | |||
CHANNEL | Correspondence Channel | FTR_CHANNEL | CHAR | 15 | Assigned to domain | FTR_CHANNEL | |||
MESSAGE_FORMAT | Format | FTR_FORMAT | CHAR | 15 | Assigned to domain | FTR_FORMAT | |||
DIRECTION | Direction of correspondence | FTR_CODIR | CHAR | 1 | FTR_CODIR | ||||
CRUSER | Entered by | TB_CRUSER | CHAR | 12 | SYCHAR12 | ||||
DCRDAT | Entered On | TB_DCRDAT | DATS | 8 | DATUM | ||||
TCRTIM | Entry Time | TB_TCRTIM | TIMS | 6 | UZEIT | ||||
EXEC_DATE | Outgoing Correspondence Execution Date | FTR_EXEC_DATE | DATS | 8 | DATUM | ||||
EXEC_TIME | Outgoing Correspondence Execution Time | FTR_EXEC_TIME | TIMS | 6 | UZEIT | ||||
EXEC_USER | Outgoing Correspondence Executed by User | FTR_EXEC_USER | CHAR | 12 | Assigned to domain | FTR_USERNAME | USER_COMP | ||
DELV_DATE | Outgoing correspondence delivery date | FTR_DELV_DATE | DATS | 8 | DATUM | ||||
DELV_TIME | Outgoing correspondence delivery time | FTR_DELV_TIME | TIMS | 6 | UZEIT | ||||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 |
Key field | Non-key field |
How do I retrieve data from SAP structure TCORS_ALERT_CORRES using ABAP code?
As TCORS_ALERT_CORRES 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 TCORS_ALERT_CORRES as there is no data to select.How to access SAP table TCORS_ALERT_CORRES
Within an ECC or HANA version of SAP you can also view further information about TCORS_ALERT_CORRES 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