In the native annotations of the SAP Fiori Elements application, we can see a number of the following attributes prefixed with Common and UI:

These Common, UI, or namespaces are defined at the beginning of the local annotation file (under the localService folder) :

<? The XML version = "1.0" encoding = "utf-8"? > <edmx: edmx Version="4.0" XMLNS :edmx="http://docs.oasis-open.org/odata/ns/edmx"> <edmx:Reference URI =".. /.. /catalogservice; v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_COMMON',Version='0001',SAP__Origin='LOCAL')/$value"> <edmx:Include Namespace="com.sap.vocabularies.Common.v1" Alias="Common"/> </edmx:Reference> <edmx:Reference Uri=".. /.. /catalogservice; v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_UI',Version='0001',SAP__Origin='LOCAL')/$value"> <edmx:Include Namespace="com.sap.vocabularies.UI.v1" Alias="UI"/> </edmx:Reference>
  • com.sap.vocabularies.Common.v1: Common terms for all SAP vocabularies

https://sap.github.io/odata-v…

  • com.sap.vocabularies.UI.v1:Terms for presenting data in user interfaces

https://sap.github.io/odata-v…

All the Odata Vocabulary annotations defined by SAP for Fiori Elements can be found at this link:

https://sap.github.io/odata-v…

There are two types of vocabulary based annotations:

  1. In-place: Part of the OData service metadata.
  2. Ex-place: In addition to the Metadata Document, the Annotation Provider Class (APC) is provided by an annotation-provided Class. The binding relationship between APC and ODATA service is maintained by the transaction code /IWBEP/REG_VOCAN.

These annotations are available using a query to the SAP Gateway catalog service, /sap/opu/odata/IWFND/CATALOGSERVICE; V = 2 /. The Entity Set: a longitudinal Annotations’.

For example:

More of Jerry’s original articles can be found on “Wang Zixi “: