SAP ABAP Data Element /IWFND/MED_MDL_ELMNT_EXT_NAME (External Name of the model entity)
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_ELMNT_EXT_NAME
Short Description External Name of the model entity  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type /IWFND/MED_MDL_ELMNT_EXT_NAME    
Data Type CHAR   Character String 
Length 40    
Decimal Places 0    
Output Length 40    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
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 Name 
Medium 15 Element Name 
Long 20 External Name 
Heading 40 External Element Name 
Supplementary Documentation - /IWFND/MED_MDL_ELMNT_EXT_NAME0100

Use

Name of the Property as represented in the external service, Service Document, and metadata document.

Dependencies

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

Example

External name is Telephone.

Technical name is TEL01.

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_ELMNT_EXT_NAME0200

Use

Name of relation as represented in the external service, Service Document, and metadata document.

Dependencies

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

Example

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

<Association Name="SalesOrder" sap:content-version="1">

<End Type="Z_FR_CUST.customer" Multiplicity="1" Role="FromRole_customer_zfr_salesorder" />

<End Type="Z_FR_CUST.zfr_salesorder" Multiplicity="*" Role="ToRole_zfr_salesorder_customer" />

<ReferentialConstraint>

<Principal Role="FromRole_customer_zfr_salesorder">

<PropertyRef Name="VALUE" />

</Principal>

<Dependent Role="ToRole_zfr_salesorder_customer">

<PropertyRef Name="CUSTOMERNUMBER" />

</Dependent>

</ReferentialConstraint>

</Association>

Supplementary Documentation - /IWFND/MED_MDL_ELMNT_EXT_NAME0300

Use

Name of operation as represented in the external service, Service Document, and metadata document.

Dependencies

Example

Supplementary Documentation - /IWFND/MED_MDL_ELMNT_EXT_NAME0400

Use

Name of Data Object as represented in the external service, Service Document, and metadata document.

Dependencies

Example

External name is Sales Order.

Technical name is Z123ABC.

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

<EntitySet Name="addressCollection" EntityType=".address" sap:content-version="" sap:creatable="true" sap:updatable="true" sap:deletable="" sap:searchable="" />

Note: Collection is automatically added to the name.

Supplementary Documentation - /IWFND/MED_MDL_ELMNT_EXT_NAME0700

Use

Enter the name of the input Property as represented in the external service, Service Document, and metadata document.

Dependencies

Example

External name is Telephone.

Technical name is TEL01.

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