Show TOC

Editing the Fields in the Operational Data ProviderLocate this document in the navigation structure

Use

Under Details, the system displays the field list of the selected operational data provider (ODP). The proposal is generated from the model node and contains as fields all node attributes selected in the Model Node step which have a data type that is supported by ODPs.

Procedure

Set the ODP field list and the analyitic properties of the ODP fields:

  1. The definition of an InfoObject (with the name, the description and the availability of texts and attributes) is either derived locally from the ODP field or from an association.

    Depending on the role that an ODP field has during analysis and on how the field is used in its search and analysis model, you can influence how the definition of the InfoObject - and in particular the InfoObject Name and its description - are derived for an ODP field.

    • Representing key field:

      For representative key fields, the InfoObject is based on the ODP. No changes can be made in the derivation of the InfoOject definition.

    • Fields that are used in the foreign key relationship of an association and are not representative key fields:

      For other fields that are used in the foreign key relationship of an association, but are not the representative key field, the InfoObject is based on the target of the association. The target of the association is the reference characteristic for the ODP field. If you do not want to use the association for the derivation of the InfoObject name and description, you have the following options:

      • You can select the ODP field's Redefine column. The field's Attribute Name and Description columns are then input enabled. Enter an appropriate name and a description. If you follow this procedure, the InfoObject texts and attributes are based on the target of the association. The navigation attributes are not taken over from the associated ODP however.

      • You can use an associated ODP with ODP view Projection in order to derive the InfoObject definition for the ODP field. To do this, press Associated ODP and select a suitable ODP in the dialog box that appears. If you follow this procedure, the system selects the Associated ODP column for the ODP field. The system derives the InfoObject definition from the selected ODP and takes over the navigation attributes from this ODP. The navigation attributes are then displayed below the ODP field in the ODP field list.

    • Fields that are not used in the foreign key relationship of an association and are not representative key fields either:

      For fields that are not used in the foreign key relationship of an association and are not representative key fields either, the InfoObject definition is based on the local definition of the ODP field. The field's Attribute Name and Description columns are input enabled. You can change the name and description of the ODP field locally.

    For information about the InfoObject names and descriptions, see Deriving InfoObject Names for ODP Fields.

    Note

    For changes in the derivation of the InfoObject definition, note the following:

    • A typical scenario for changing descriptions is when using navigation attributes. Navigation attributes must clarify the context that they are used in by means of their description. They therefore need to have different descriptions to the display attributes.

    • If you change the derivation of InfoObject definitions, note how objects are compounded.

  2. In the Role column, the system proposes the InfoObject type (characteristic or key figure) for an ODP field. The proposal is based on the data type of the corresponding node attribute. Check the proposal (especially for fields with the data types DATS, TIMS or DEC) and modify them if necessary.

  3. In the Aggregation Mode column, the system proposes aggregation mode SUM for key figures.

  4. To make it possible to use navigation attributes, perform the following steps in accordance with the ODP's semantics:

    1. To format a field in an ODP for master data attributes as navigation attributes, select the Navigation Attribute column for the field in question.

      In the ODP with ODP view Data Extraction, set the upper limit of the navigation attributes for all of the node's ODPs.

      If you select the Navigation Attribute column in an ODP with ODP view Projection, this applies for just this ODP. Note that you can only use an ODP field of an ODP with ODP view Projection as a navigation attribute if it is already selected as a navigation attribute in the associated ODP with ODP view Data Extraction.

    2. For a transaction data ODP with an association to a master data ODP that provides navigation attributes, you can add the navigation attributes to the required field (characteristic):

      1. Select the field that you want to add the navigation attributes to and press Associated ODP.

      2. A popup appears. Select the required ODP here. If several ODPs correspond to various referencing characteristics, select the ODP that reflects the role of the field selected in your transaction data ODP.

  5. Check the entries in the columns for selectability of the fields.

  6. If your ODP contains fields that you only need for search purposes and do not want to use for Operational Data Provisioning, you can delete them from the ODP field list.

    If you are using the SAP HANA database or SAP BW Accelerator, fields that are deleted from the ODP are indexed but are not read for Operational Data Provisioning.

  7. Save the ODP.