SAP ABAP Data Element /IWFND/MED_MDL_CORE_TYPES (Data Type)
Hierarchy
SAP_GWFND (Software Component) SAP Gateway Foundation
   OPU-FND-CS (Application Component) IWF Common Services
     /IWFND/MED_SVC_MULTI_LANGU (Package) GW Framework - Metadata - Service Def. - End User Translatio
Basic Data
Data Element /IWFND/MED_MDL_CORE_TYPES
Short Description Data Type  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type /IWFND/MED_MDL_CORE_TYPES    
Data Type CHAR   Character String 
Length 20    
Decimal Places 0    
Output Length 20    
Value Table /IWFND/I_MED_CTD    
Further Characteristics
Search Help: Name /IWFND/SH_MED_CORE_TYPES    
Search Help: Parameters CORE_TYPE   
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Data Type 
Medium 17 Core Data Type 
Long 20 Core Data Type 
Heading 17 Core Data Type 
Documentation

Definition

Specifies the Entity Data Model (EDM) type. The following are the data types:

  • Edm.Guid: A unique identifier value. You can map it to the predefined CHAR LENGTH 32. The internal representation does not contain any '-'.
  • Edm.Double: A floating point number with 15 digits precision. Can be mapped to the predefined FLOAT.
  • Edm.Single: A floating point number with seven digits precision. You can map it to the predefined FLOAT. The value range is between 1.18E-38 and 3.40E+38. The serialization always formats the value with 8 decimal places.
  • Edm.Int16: A signed 16-bit integer value. You can map it to the predefined INT2, INT, and also NUM. The value range is between -32768 and 32767. When it is mapped to NUM, leading ZEROs are removed in serialization and added in deserialization.
  • Edm.Int32: A signed 32-bit integer value. You can map it to the predefined INT, and also NUM. The value range is between -2147483647 to 2147483647. When it is mapped to NUM, leading ZEROs are removed in serialization and added in deserialization.
  • Edm.Int64: A signed 64-bit integer value. You can map it to the predefined PACKED LENGTH >= 8 DECIMALS 0, and also NUM. When it is mapped to NUM, leading ZEROs are removed in serialization and added in deserialization.
  • Edm.SByte: A signed 8-bit integer value. You can map it to the predefined INT2, INT, and NUM is also possible The value range is between -255 and 255. When it is mapped to NUM, leading ZEROs are removed in serialization and added in deserialization.
  • Edm.DateTime: Date and time with values. DateTime as Timestamp can be mapped to the predefined : TIME. It is ignored by deserialization. In serialization, it is 00:00:00. DateTime as Date can be mapped to the predefined : DATE. It is ignored by deserialization. In serialization, it is 00-00-00.
  • Edm.Binary: Fixed or variable length binary data. You can map it to the predefined XSTRING, and HEX.
  • Edm.String: Fixed or variable length character data. You can map it to the predefined STRING, CHAR, and NUM. No conversion is done for Strings.
  • Edm.Decimal: Numeric value with fixed precision and scale. You can map it to the predefined PACKED, DECFLOAT16, and DECFLOAT34.
  • Edm.DateTimeOf: Offset in minutes from GMT. You can map it to the predefined PACKED LENGTH 8 DECIMALS 0 (timestamp is without fractional seconds), and PACKED LENGTH 11 DECIMALS 7 (timestamp with fractional seconds). Deserialzation considers an offset like +03:30 and converts it into an UTC Timestamp. The internal representation must be an UTC Timestamp. Serialzation always uses Z as Offset.
  • Edm.Boolean: Represents the mathematical concepts of binary-valued logic. You can map it to the predefined CHAR LENGTH 1. The XML value 'true' and '1' is mapped to the ABAP value 'X'. The XML value 'false' and '0' is mapped to the ABAP value ' '.
  • Edm.Time: Time of day with values ranging from 0:00:00.x to 23.59.59
  • Edm.Byte: Unsigned 8-bit integer value. You can map it to the predefined INT1, INT, and NUM is also possible. The value range is between 0 and 255. When it is mapped to NUM, leading ZEROs are removed in serialization and added in deserialization.

Use

Dependencies

Example

Supplementary Documentation - /IWFND/MED_MDL_CORE_TYPES0100

Use

Specifies the type allowed from OData that is used at runtime.

Select a type from the value help.

Dependencies

The Property editor fields together control how the Property is represented in the metadata.

Example

Select Edm.String for fixed or variable length character data.

The following example shows how the Property editor fields are represented in the metadata, with this field underlined to highlight it:

<Property Name="telephone" Type="Edm.String" Nullable="false" MaxLength="30" sap:label="Telephone number" sap:creatable="true" sap:updatable="true" sap:filterable="true" sap:semantics="tel" />

Supplementary Documentation - /IWFND/MED_MDL_CORE_TYPES0700

Use

Specifies the type allowed from OData that is used at runtime.

Select a type from the value help.

Dependencies

Example

Select Edm.String for fixed or variable length character data.

History
Last changed by/on SAP  20131122 
SAP Release Created in 200