C_TransportationCondition
Manage Conditions
C_TransportationCondition is a Consumption CDS View that provides data about "Manage Conditions" in SAP S/4HANA. It reads from 1 data source (R_TransportationConditionTP) and exposes 9 fields with key field TransportationConditionUUID. It is exposed through 1 OData service (UI_TRANSPORTATIONCONDITION). It is used in 1 Fiori application: Manage Conditions. Part of development package CVIEW_TM_COND_MNG.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_TransportationConditionTP | R_TransportationConditionTP | projection |
Annotations (8)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Manage Conditions | view | |
| AccessControl.authorizationCheck | #MANDATORY | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.usageType.dataClass | #ORGANIZATIONAL | view | |
| VDM.viewType | #CONSUMPTION | view | |
| Metadata.allowExtensions | true | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_TRANSPORTATIONCONDITION | UI_TRANSPORTATIONCONDITION | V2 | C1 | NOT_RELEASED |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5768 | Manage Conditions | Transactional | With this app, you can maintain conditions for an application area within TM. The conditions are consumed within the applications(application logic) for decision making or arriving at an outcome. |
Manage Conditions
Business Role: Master Data Specialist - Transportation Management
With this app, you can define conditions.
Key Features: Define conditions to automate confirmation and posting of freight costs Use the combination of carrier or service provider, procuring company code, and purchasing organization to set the conditions. When a freight document matches a condition, the system automatically confirms and posts the freight costs. Define conditions to determine freight unit building rules Use the combination of the following attributes to set the conditions: Source location Destination location Shipping condition Transportation group Material freight group When you save a sales order or purchase order, the system determines a logistics integration profile. If a condition for determining freight unit building rules is assigned to this profile, the system automatically creates freight units based on the freight unit building rule returned by this condition. Define conditions to determine the unit of measure for normalized quantities and additional normalized quantities Use the combination of the following attributes to set the conditions: Source country/region Destination country/region Source region Destination region If a relevant business document matches one or several of these attributes, the system determines the unit of measure for normalized quantities and additional normalized quantities based on the values that you have specified in the data access definition of your condition. Note that in the freight orders, the corresponding fields are called Pallet Spaces and Loading Meters.
Fields (9)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | TransportationConditionUUID | TransportationConditionUUID | ||
| TransportationCondition | TransportationCondition | |||
| TransportationConditionDesc | TransportationConditionDesc | |||
| TransportationConditionType | TransportationConditionType | |||
| TranspConditionTypeTextlocalized | ||||
| CreatedByUser | CreatedByUser | User Name | ||
| CreationDateTime | CreationDateTime | Timestamp | ||
| LastChangedByUser | LastChangedByUser | User Name | ||
| ChangedDateTime | ChangedDateTime | Time Stamp |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view C_TransportationCondition.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
CREATE VIEW C_TransportationCondition AS
SELECT
TransportationConditionUUID,
TransportationCondition,
TransportationConditionDesc,
TransportationConditionType,
_TranspConditionType._TranspConditionTypeText.TranspConditionTypeText : localized AS TranspConditionTypeTextlocalized,
CreatedByUser,
CreationDateTime,
LastChangedByUser,
ChangedDateTime
FROM R_TransportationConditionTP
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- 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
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA