@UI.

headerinfo: {typenamePlural: 'Sales Orders}

qualifier
 '
@UI.lineItem: [{position: 10},{qualifier: 'ValueList', position:10}]

@search.searchable
..........................
 Expose a CDS View as object-page Floor Plan

@UI.headerInfo
 label: ' '
value: ' '

@UI.headerInfo + @UI.identification = @UI.badge

You can have either @UI.badge or @UI.header but not BOTH in a view

@UI.badge:
@UI.lineitem === @UI.Identification

has qualifier NO qualifier

Elements to be displayed in the page body of the object page floor plan
Grouping of Fields under one heading

Sections for forms

 I
Data Field like Annotations: @UI.lineitem @UI.identification

@UI.selectionField @UI.fieldGroup
 -ve number for position is allowed

position: -5

decimal -- quotes '1.1'

position: '1.1'

why it is used?

if the UI is displayed on a small screen, low priority fields are automatically hidden
Enriching a measure with business-relevant data
 change the order and check the output

@datapoint.criticality

@datapoint.trend
 @UI.datapoint
Trend-Criticality Calculation

.......................................

..............................

--------------------------
...........................
trendcalculation
@UI.datapoint
.trendCalculation
.criticalityCalculation
---------------------------------

----------------------
Person Responsible & ref. point:
@UI.datapoint:
referencePeriod:
responsibleName:
DataField Types can be mapped to @UI.dataPoint

@UI.lineItem: [ { type: #AS_DATAPOINT } ]

 @semantics == address data

....................................

.................................................
..........................
 @semantics.name
givenName, addlName, familyName

@semantics.contact.birthdate
BirthDate
navigate between screen, outside application, web sites
-------------------------------------
sepm_cds_sales_order sepm_cds_business_partner

You set the navigation path to Data Fields

data field with Navigation Path:

type: #WITH_NAVIGATION_PATH
url: '_association'
 type: #with_url

Set data element to URL in the table

action on semantic object

@consumption.semanticobject
@UI.lineitem:

type: #for_intent_based_navigation
semanticobjectAction: 'Show'
-------------------------
@consumption.semanicobject: ' '
element,
 type:#For_Action,
dataAction: 'BOPF:Copy' ,
label: 'copy'

type: #FOR_ACTION, dataAction: 'BOPF:Copy', label: 'Copy' }

ZOFT_BOPFchar:ACTION
type: #FOR_ACTION, dataAction: 'ZOFT_BOPF_999char:ACTION, label: 'Copy' }
@UI.identification: [{ position:30}]
@UI.multiLineText: true
Description,
 @UI.Identification[{ position: 40 } ]
@UI.masked
so.salesorder_id

@UI.hidden

all fields that are exposed by the OData service are available to the client

hide the fields if they are required in calculations, but you don't want to dispaly on UI
@UI. hidden vs @consumption.hidden

preventing the fields from being available to client

@consumption.hidden
use @consumption.hidden for system parameters

@environment variable
they are filled by runtime engine
 field is marked with an * asterik
@objectmodel.mandatory: true

---- if you don't enter value an error is raised

* GrossAmount