Editing Data Object Properties
The Data Object (DO) entities are abstractions of real business objects. DO structures (or "metadata") are defined in the Data Orchestration engine (DOE) but can be edited in the SAP NetWeaver Developer Studio (NWDS). The NWDS contains a Data Object editor that you can use to view data objects you have imported from the DOE and edit some of their properties. You can open all data objects and all nodes of a data object in the data object editor.
To view or change data objects in NWDS, you first have to import them from the DOE. More information: Creating Data Objects
Features
To open a data object or node in the editor, double-click it in the Service Explorer.
Data Objects
For a data object, the editor has two tabs:
Overview : This tab displays basic read-only information about the data object.
Nodes : On this tab, you can define which nodes are shown to the developer. To show a node, mark the checkbox for that node in the table. You can also specify whether synchronization conflicts and errors should be resolved automatically or if you want to create your own handlers. Finally, you can see which lifecycle operations (create, read, update, delete) are possible for nodes.
Data Object Nodes
For data object nodes, the editor contains the following tabs:
Overview : This tab shows basic read-only information about the node.
Attributes :
This tab shows a list of all attributes for the node. In the "Show" column, you can choose whether to show or hide individual attributes. This governs if the respective getter/setter methods are generated for accessing the data object attribute. The sync key attributes cannot be hidden.
|
Table item |
Description |
|
Show |
Decides if a node will be available in the DO by showing or hiding it at a Java API level. |
|
Name |
The name, which appears in the NWDS and can be edited. You may want to change the name of a data object attribute in NWDS. By default, the name is a case-sensitive copy of the DOE-side attribute name, but can be arbitrarily changed, for example to increase readability of your code. |
|
Data Type |
An attribute is automatically defined during import of the data object from the DOE. Since DOE uses ABAP types while NWDS and the mobile client use Java types, a type conversion is happening automatically and the corresponding Java types are created in the Data Dictionary. You can inspect the Data Dictionary type by right-clicking the data type and choosing "Open dictionary type". |
|
Default Value |
The value set by default for an attribute when a Data object instance is created. |
|
Type Validation |
Whether values are checked for consistency with the relevant type in the data dictionary. Since this check has a performance impact, ideally this check should be carried out on the User Interface level. |
|
Value Help |
Defines a data source from which to derive a range of allowed values. The original "Name" column displays the name of the data object in the DOE and cannot be changed. |
|
Original Name |
This is the original name of the node attribute as defined in the DOE. |
Relations : This tab provides a read-only overview of relations for the node. They are inferred from the node associations modeled in the DOE. More information: Defining an Association Between Data Objects
Ind exes : On this tab, you can create and view database indexes for attributes or combinations of attributes. If you expect that certain attributes or combinations of attributes will be used frequently in queries, it is recommended that you create an index for them to improve data access performance.