Show TOC

Remodeling a DataStore ObjectLocate this document in the navigation structure

Prerequisites

  • You have created a DataStore Object (DSO) and loaded data into it.

  • The change log must be empty.

  • For an SAP HANA-Optimized DataStore Object, if the change log data is not deleted, filling methods are supported but scheduling is not allowed. You need to delete the change log data to schedule the remodeling rule.

  • All DataStore object types are supported.

  • The DataStore object must not have an archive or near-line storage that contains data. If this is the case, you first have to reload the data from the archive or the near-line storage into the DataStore object. After remodeling, the data can be loaded back into the archive or near-line storage.

  • There must not be any inactive data in the DataStore object.

Procedure


  1. You access Data Store object remodeling in the Data Warehousing Workbench under Administration. You can also access it from the InfoProvider context menu in the InfoProvider tree by choosing Start of the navigation path Additional Functions  Next navigation step Remodeling End of the navigation path.

  2. Create a remodeling rule. Specify a name and description for the remodeling rule, select a DataStore object, as required, and choose Create.

  3. Choose Add Operation to List. You can select one of the following options from the dialog box:

    • Add characteristic/key figure

    • Delete characteristic/key figure

    • Replace characteristic/key figure

  4. For the Add Characteristic and Replace Characteristic options, specify how you want to fill the new characteristic with data:

    • Constant: The system fills the new characteristic with a constant.

    • Attribute: The system fills the new characteristic with the values of an attribute of another characteristic.

    • 1:1 mapping for characteristic: The system fills the new characteristic with the values of another characteristic. You replace one characteristic with another, thereby adopting the value of the original characteristic.

    • Customer exit: The system fills the new characteristic using a customer exit. More information: Customer Exits in Remodeling.

    For key figures, no filling method is used.

  5. Choose Transfer

  6. Repeat steps 3 and 4 until you have collected all changes. In the bottom half of the screen, you can make changes to the operations at any time. To do this, select the corresponding step in the upper half of the screen.

    You can delete an operation at any time using Remove Operation from the list.

  7. Save your entries.

  8. Choose Check. The system checks whether the operations are correctly defined and whether the relevant InfoObjects are available in the InfoProvider.

    The system also checks the compatibility of the filling method.

    Example

    • If the filling method is 1:1 mapping, the system reads one single value from the old InfoObject and checks if this is a valid value for the new InfoObject without filling or changing master data.

    • If the filling method is Customer exit, the system passes one row of the source table to the customer exit and executes it to check if the output is received and compatible with the new InfoObject.

  9. You can display a list of the objects affected by remodeling using Impact Analysis. These objects are deactivated during remodeling. You can make a note of the objects that you need to reactivate later.

  10. By choosing Schedule, you can either start remodeling immediately or schedule it for later. You can specify whether to execute the process in parallel by setting the Execute Steps in Parallel flag. Do not set this flag if your system does not have sufficient capacity.

  11. You can check the process in the monitor. More information: Monitor and Error Handling.

Results

You can now use the remodeled, active DataStore object.