Show TOC

Adding FieldsLocate this document in the navigation structure

You define the DataStore object by adding fields or InfoObjects.


The advantage of using fields is that you do not need to model any InfoObjects. This is recommended especially if you want to load data types that are not supported by InfoObjects.

Note the restrictions that apply when modeling with fields: Modeling with Fields Instead of InfoObjects


  1. Choose the Details tab.
  2. To add a field, choose Add Field. The field is added to your DataStore object. You can now define the field in the right area of the screen.
  3. Enter a description for the field.
  4. You can specify an InfoObject under Identify with:. This changes the field into an InfoObject. The properties of the InfoObject are applied. You can undo this by switching to Field under Identify with:.
  5. Enter the data type and data length. Certain types and lengths are not supported in the query. If you enter one of these, an error message appears. If they have a different format, they need to be assigned using an Open ODS view, in order to be displayed in the query.
  6. If you choose Use Navigation Attributes in Extraction, the navigation attributes of this InfoObject can be used in the transformation, if the DataStore object is the source of the transformation. In addition, you can use the navigation attributes as filter criteria in the DTP.
  7. You can use fields to organize your InfoObjects. There are no semantic restrictions here. To do this, choose Add Group. You can change the technical name of the group and enter a description. You can move fields from one group to another using drag and drop.
  8. You can define keys. More information: Defining Keys
  9. To delete fields, choose Delete.
  10. Under Maintain Properties, you can make for aggregation and master data check settings for all InfoObjects/fields that support this:

    You can select an aggregation type under Aggregation.

    Under Master Data Check, you can decide whether you want to check for referential integrity or whether you want to run the check when data is loaded or queries are executed and whether you want to save the SIDs. Saving SIDs is useful if you have a compound characteristic with high cardinality and mainly navigation attributes of this compound characteristic are used in the query. This means the join must be executed very frequently, which can have a negative impact on performance. An additional column is created in the table for the purpose of saving the SIDs for this InfoObject. This column is filled during activation.