DESTINATION_NAME in KSR_TA_HTTP_CL
Destination Name (DE: Destinationsname)
DESTINATION_NAME is a field in SAP table KSR_TA_HTTP_CL (KSR: Tenant Aggregate HTTP Client). It represents "Destination Name". Data element: KSR_V_DESTINATION_NAME. Available in 1 CDS view(s) as Destination_Name.
Business Meaning
| Description (EN) | Destination Name |
|---|---|
| Beschreibung (DE) | Destinationsname |
| Data Element | KSR_V_DESTINATION_NAME |
| Key Field | Yes |
CDS Views & Technical Names (1)
KSR_TA_HTTP_CL.DESTINATION_NAME is exposed in CDS views under the following technical name. Views reading the table directly are listed first; "via" marks views that pass the field on through intermediate views.
Destination_Name
(1 view)
| View | Access | VDM | Release | Description |
|---|---|---|---|---|
| KSR_I_TA_HTTP_CL_R | direct | KSR: Tenant Aggregated HTTP Client |
Other Tables with Field DESTINATION_NAME (5)
| Table | Data Element | Key | Description |
|---|---|---|---|
| KSR_TA_RFC_CL | KSR_V_DESTINATION_NAME | KEY | KSR: Tenant Aggregate RFC Client |
| KSR_TS_HTTP_CL | KSR_V_DESTINATION_NAME | KSR: Tenant Specific HTTP Client Subrecords | |
| KSR_TS_HTTP_CLDS | KSR_V_DESTINATION_NAME | KSR: Tenant Specific HTTP Client Destination Subrecords | |
| KSR_TS_HTTP_SRVD | KSR_V_DESTINATION_NAME | KSR: Tenant Specific HTTP Server Destination Subrecords | |
| KSR_TS_RFC_CL | KSR_V_DESTINATION_NAME | KSR: Tenant Specific HTTP Client Subrecords |
Learn More
- Understanding Data Lineage in SAP S/4HANA
- SAP Tables vs CDS Views — Key Differences
- Understanding the SAP S/4HANA Data Model
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA