Show TOC

Procedure documentationDeveloping Data Types Locate this document in the navigation structure

 

You use data types to describe the data structures for the following cases:

  • To describe the structure of a message type that can be referenced from one or more service interfaces in the ES Repository. By using the service interface, you can use the referenced data structure for the following scenarios:

    • To define the data of a message that is exchanged in either Web service communication (point-to-point) or in Integration Server communication. The data type definition determines how the valid payload of a message will look.

    • To use the data of a (adaptive) Web service model in SAP NetWeaver Developer Studio for UI development. The Web service model is based on a Web service definition in the ABAP backend, which you can in turn create on the basis of ES Repository service interfaces in the backend.

There are different classifications of data types in the ES Repository:

  • Core data types and aggregated data types

    The specification XML Naming and Design Rules by the United Nations for Trade Facilitation and Electronic Business (UN/CEFACT XML NDR) describes how syntax-free components, which have been developed according to ISO 15000-5 Core Components Technical Specification (CCTS) are represented systematically in XML schema and XML instances. Core data types and aggregated data types are defined according to these standards. In addition to the language elements of XML schema, the data type editor also has attributes for the definition of the data types that comply with CCTS. These can be evaluated when the data type is used elsewhere. This, together with the governance process for data types simplifies the development of cross-company processes and the development of user interfaces, for example.

  • Freely-Modeled Data Type

    Freestyle data types support XML schema only.

Message types in the ES Repository can reference freestyle data types, core data types, and aggregated data types.

Prerequisites

The following sections contain general information about developing data types:

  • Data Types in the Enterprise Services Repository

    This section describes the underlying concepts behind data type development, irrespective of how they are classified.

  • XSD Editor (Freely-Modeled Data Types)

    Describes the XSD editor for freely-modeled data types, and the underlying concepts of XML schema. Although you use different editors to develop data types based on CCTS, the underlying concepts are still also relevant for developing core data types and aggregated data types.

Procedure

  1. Decide whether you want to develop data types that comply with CCTS, or whether you want to model freely-modeled data types. SAP recommends that you develop data types that comply with CCTS in the case of new developments. You can also reference core data types or aggregated data types from freely-modeled data types.

    Note Note

    When you create a data type, you must decide whether you want to create a freestyle data type, core data type, or aggregated data type. Data may be lost when you switch between the different classifications.

    End of the note.
  2. It is possible - albeit with restrictions - to import as a template data types developed in XML schema using an external tool. The exact restrictions depend on the classification of the data type. More information: Importing XSD as a Template.

  3. Develop your data types either according to CCTS, or model them freely:

  4. Customers or partners can enhance data types. More information: Enhancing Data Types