Creating a New Data Object

Prerequisites

You have created the software component version (SWCV) for which you want to create the data object.

Procedure

Log on to the SAP NetWeaver Application Server and start transaction SDOE_WB .
In the Data Orchestration Workbench, click with the secondary mouse button the software component version for which you want to create the data object and choose Create Create Data Object.
Under Data ObjectCategory , select the required data object category from the dropdown list.

Note

After you save the data object with a particular category, you cannot change the category.
Choose ADD .

On the Data ObjectOverview tab page, under Data ObjectDetails enter the following details:

Field name	Description	User action and values	Comment
SWCV Name	Displays the name of the software component version you selected in the Mobile Middleware Design browser	A read-only field.
Name	Indicates the name of the data object	Enter a name for the data object. The name must not contain any spaces or special characters.	Make sure the name you specify reflects the data-set represented by the data object, is unique within the software component version, and conforms to the naming conventions of your software development enterprise.
Description	Indicates a brief description of the data object.	Enter a description for the data object.
Status	Indicates the status of the data object. A data object can have the following statuses: NEW INACTIVE ACTIVE	A read-only field.	When you are creating a new data object, the status of the data object is NEW. After you save the data object. The status changes to inactive.
Version	Indicates the version of the data object	A read-only field.
Category	Indicates the category of the data object	A read-only field.
Automatic Key Mapping	Allows you to have the back-end keys of the individual data object nodes mapped automatically.	By default, this indicator is deselected.	This function automatically maps back-end keys in the parent nodes and child nodes of a data object, which have the same name and data type. More information: Automatic Key Mapping
Gateway Enabled	Allows you to use the data object to exchange data with multiple back-end systems.	Select the option.	If you release a data object with this option selected, you cannot deselect this option when you modify the data object later on. This means that later versions of the data object must remain gateway enabled.

Under Direction , select the required option to specify the behavior of the data object during runtime.

Field name	Description	Comment
Bi-Direction	Specifies that the data object supports download/upload of data from/to the back-end system	This is used for data that may be updated in the back end (and sent to the mobile device) and in the mobile device (and then sent back to the back end).
Download Only	Specifies that the data object supports only download of data from the back-end system	This is used for data that is only to be updated in the back end, not in the mobile device.
Upload Only	Specifies that the data object supports only upload of data to the back-end system	You cannot create a distribution model for an upload-only data object.
Keep Inst Locally	Defines that in the case of an upload-only data object, the data object instance is to be kept locally.

Under Conflict Detection Scheme , select any one of the following options to resolve the conflict. Conflicts can occur when a single data object is modified by two different users and both upload the modified data object to the Data Orchestration Engine (DOE). In this case, to resolve the conflict, the DOE uses the option you specify.

Field name	Description	Comment
Last One Wins	A data object instance can be modified by multiple mobile application users. If this option is selected, when all the modified instances are submitted simultaneously to the DOE, the DOE updates the database with modified data object instance that is received last.	By default, this option is selected.
First One Wins Object Level	If this option is selected, when all the modified data object instances are submitted simultaneously to the DOE, the DOE updates the database with modified data object instance that is received first. As a result, the DOE rejects the modified data object instances submitted by other application users.
First One Wins Row Level	Within a data object instance, multiple application users may update the same record or different records. Consider the scenario where you select this option and multiple application users update the same record and simultaneously submit the modified data object instances to the DOE. In this case, the DOE updates the database with the changes to the record in the modified data object instance that is received first. As a result, the DOE rejects the other data object instances that update the same record.

Under Backend Access Time stamp set one of the following indicators:

Field Name	Description	Comment
Before Backend Access	Indicates that a back-end access time stamp is to be set before back-end access.	Set this indicator if you want to have a time stamp field generated in the CDS table. At runtime, this field is filled with a time stamp which indicates the beginning of a back-end access process.
After Backend Access	Indicates that the back-end access time stamp is to be set after back-end access.	Set this indicator if you want to have a time stamp field generated in the CDS table. At runtime, this field is filled with a time stamp which indicates the end of a back-end access process.

Choose Save .
In the Package field, enter the name of the transportable package and choose Save .

Note

To save the data object locally, choose Local Object . In this case, the data object is part of the $TMP package and is not transported. If you want to transport the data object at a later point in time, you can assign the locally saved data object to a transportable package.

More information: Processing Data Objects
Enter the transport request and choose Enter .

Note

To create transport request, choose Create request .