RCV_STR_DYN_REC_DET_HDS_SOURCE SAP (Source Structure for Dynamic Recipient Determination in HDS) Structure details
Description: Source Structure for Dynamic Recipient Determination in HDS
Related tables to RCV_STR_DYN_REC_DET_HDS_SOURCE
Access table RCV_STR_DYN_REC_DET_HDS_SOURCE
Structure field list including key, data, relationships and ABAP select examples
RCV_STR_DYN_REC_DET_HDS_SOURCE 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 "Source Structure for Dynamic Recipient Determination in HDS" 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_RCV_STR_DYN_REC_DET_HDS_SOURCE TYPE RCV_STR_DYN_REC_DET_HDS_SOURCE.
The RCV_STR_DYN_REC_DET_HDS_SOURCE table consists of various fields, each holding specific information or linking keys about Source Structure for Dynamic Recipient Determination in HDS data available in SAP. These include GPART (Correspondence Recipient), GPART_GUID (Correspondence Recipient (GUID)), ORG_GPART (Original Correspondence Recipient), ORG_GPART_GUID (Original Correspondence Recipient (GUID)).. 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 RCV_STR_DYN_REC_DET_HDS_SOURCE 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 |
COTYP | Correspondence Type | COTYP_KK | CHAR | 4 | Assigned to domain | COTYP_KK | COTYP | COTYP_KK | |
GPART | Correspondence Recipient | CREC_GP_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | ||
GPART_GUID | Correspondence Recipient (GUID) | CREC_GP_GUID_KK | CHAR | 32 | SYSUUID_C | ||||
ORG_GPART | Original Correspondence Recipient | CREC_ORG_GP_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | ||
ORG_GPART_GUID | Original Correspondence Recipient (GUID) | CREC_ORG_GP_GUID_KK | CHAR | 32 | SYSUUID_C | ||||
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 | |||
DATA1 | Correspondence Data Field 1 | RCV_DTE_CORR_DATA1 | CHAR | 32 | CDATA_KK | ||||
DATA2 | Correspondence Data Field 2 | RCV_DTE_CORR_DATA2 | CHAR | 32 | CDATA_KK | ||||
DATA3 | Correspondence Data Field 3 | RCV_DTE_CORR_DATA3 | CHAR | 32 | CDATA_KK | ||||
DATA4 | Correspondence Data Field 4 | RCV_DTE_CORR_DATA4 | CHAR | 32 | CDATA_KK | ||||
CSORT | Correspondence Sort Field | CSORT_KK | CHAR | 50 | CORR_TXT50 | ||||
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 | ||||
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 | ||||
BUKRS | Company Code in Correspondence | CORR_BUKRS | CHAR | 4 | CORR_BUKRS | ||||
CORR_ROLE | Correspondence Roles | CORR_ROLE_KK | CHAR | 4 | Assigned to domain | CORR_ROLE_KK | |||
XTRIAL | Correspondence Request is Test | XTRIAL_KK | CHAR | 1 | XFELD | ||||
SUBAP | Subapplication Indicator in Correspondence | CORR_SUBAP_KK | CHAR | 1 | CORR_SUBAP_KK |
Key field | Non-key field |
How do I retrieve data from SAP structure RCV_STR_DYN_REC_DET_HDS_SOURCE using ABAP code?
As RCV_STR_DYN_REC_DET_HDS_SOURCE 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 RCV_STR_DYN_REC_DET_HDS_SOURCE as there is no data to select.How to access SAP table RCV_STR_DYN_REC_DET_HDS_SOURCE
Within an ECC or HANA version of SAP you can also view further information about RCV_STR_DYN_REC_DET_HDS_SOURCE 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