Show TOC

Workspace AdministrationLocate this document in the navigation structure

A workspace has to be created by an administrator before a business user can work in it.

The administrator defines settings such as lifetime, maximum disk space and the BW InfoProviders available in the workspace.

Procedure
  1. Call Workspace Administration from your user menu. You can use this to edit either one individual workspace (transaction RSWSP) or to edit several workspaces using a structure (transaction RSWSPW).

  2. Choose Display Impact Logs for InfoObjects to display a Workspace-neutral log, which lists the changes made to InfoObjects and their effects on local characteristics and CompositeProviders. More information: Changes to the Central InfoObject

  3. By choosing Display Workspace Action Logs, you can view all user actions and the administrator actions Create and Delete for this workspace.

Editing Individual Workspaces

  1. Select a workspace to edit or enter a name for a new workspace and choose Create.

Editing Multiple Workspaces

  1. The folder <ROOT> is initial. You can create your own folders for your workspaces below this. You can also upload a folder structure from a CSV file. More information: Managing the Folder Structure

  2. Choose a workspace to edit or create a new one by choosing Create Workspace in the context menu for your folder.

Tab: Settings

  1. You can make settings to define how the workspace is used:

    • General Settings:

      • You can set an expiry date. Once the expiry date is reached, the workspace is no longer available in Workspace Designer. Following consultation with the user, the administrator can extend the validity of the workspace or delete it, together with the objects it contains.

      • You can set a prefix for the providers in the workspace. All providers and transient queries in the workspace are then given this prefix. This prefix cannot be changed once an object hast been created with it.

      • You can enter the name of two contacts who can be called upon if problems arise with the workspaces.

    • Settings for Central Providers:

      You can assign a main provider of type MultiProvider or central CompositeProvider to the workspace. This is then assigned as a central provider. You need to explicitly select the InfoProviders you need from the main provider on the Central Providers tab page.

      More information: The Assigned Main Provider

    • Settings for Local Providers: These settings apply for local providers, local characteristics and local hierarchies:

      • You can set the maximum memory space for your own data in the workspace and the maximum number of providers. One provider is created for each uploaded data source. The system also displays the used memory and the number of providers created. If you have not made any entries, there is no restriction. This may be displayed as zero, depending on the system.

      • If you select Data Backup, a backup will be made of the uploaded data on the BW database as well as in the BWA. More information: Activating Data Backups for Local Providers

    • Settings for Data/Provider/CompositeProvider/Workspace Queries:

      • Under certain circumstances, uploading local data can cause new master data attributes to be created when a query is created. The Local Master Data Allowed flag allows you decide whether or not this should happen. For local characteristics and providers, this means that you can also load characteristic values that do not exist in the master data tables of BW InfoObjects.

      • If you set the Non-Unique Join Columns Allowed flag, a multiplication of key figures can occur if join links are used when modeling a CompositeProvider. For information about key figure multiplication, see: Union / Inner Join / Left Outer Join

Tab Page: Central Providers

  1. You can drag indexed BW InfoProviders from the object repository on the left to the right. (BWA-indexed as secondary persistence; SAP HANA as primary persistence) from the the left to the right.

    Note

    If you subsequently call a workspace with central providers that have already been assigned, the object tree is not displayed automatically. You have to choose Build InfoProvider Selection for this to happen.

  2. You can also select DataSources that can be used in BW Workspace Designer as the source for creating a local provider. To select DataSources, choose Display DataSource Selection. For DataSources of type File, the system checks whether the file is located on the application server. If not, it cannot be selected.

    Note

    Using DataSources in BW Workspaces is not recommended for mass data.

    The InfoProviders that you drag to the right are assigned to the workspace and can then be used in Workspace Designer for modeling CompositeProviders.

    The DataSources that you drag to the right serve as the source for uploads to a local provider that can be used for modeling.

  3. By double-clicking on an InfoProvider, you can display it.

  4. For InfoCubes from assigned MultiProviders, you can define whether they can be used for the workspace.

  5. You can also define whether certain key figures or characteristics can be used for the workspace.

Tab: Transfer Targets

  1. Here you can select the InfoProviders that are allowed for the transfer of data from local providers to central BW InfoProviders. By choosing Build InfoProvider Selection, you can view the InfoProvider tree on the left side of the screen. The supported target providers are DataStore objects (advanced) with the properties Activate Data, Activate Data and Write Change Log and Activate Data and All Characteristics are Key, Reporting on Union of Inbound and Active Table.

  2. Add the InfoProviders that you want to allow for data transfer by dragging them to the right side of the screen.
  3. Each InfoObject of the InfoProvider has two properties: writable and mandatory. The default setting for key fields of DataStore-objects is writable and mandatory.
  4. Provider Transfer Settings allows you to specify whether the data should be activated directly after transfer. You can also define filters here in order to restrict the data and to define whether the master data should be checked.
    Note Request-based deletion is only possible if the requests are still in the inbound table and therefore have not yet been activated. We threfore recommend not activating the data directly after transfer. This allows the business user check the data and to delete it again if necessary.

Tab Page: Local Providers

  1. If data has already been uploaded in Workspace Designer, you see a list of local providers created during the upload. The system displays the status for each local provider. OK, With Errors, Inactive or Analytic index does not exist. You can remove workspace assignments from the list for analytic indexes that no longer exist. By choosing Check you can run a more detailed analysis of the status.

    These local providers are edited in Workspace Designer.

    There is also a transaction that provides you with an overview of the local providers (analytic indexes) that you can use. More information: Managing Analytic Indexes

  2. You can also restore the analytic indexes if they are backed up in the BW system (if you are using a BWA). Choose Restore.

Note

If data backup is activated, your models and data that you have uploaded are also restored during a complete restore of BWA indexes belonging to a BW system. In BW Accelerator Monitor (transaction RSDDBIAMON), you can use the Rebuild BWA Indexes function.

Tab Page: Local CompositeProviders

  1. The system displays a list of the local CompositeProviders that have been created in Workspace Designer. The system displays the status for each CompositeProvider. OK, With Errors, Inactive or CompositeProvider does not exist.

  2. You can remove workspace assignments from the list for CompositeProviders that no longer exist.

Tab Page: Local Data

  1. The system displays a list of the local characteristics and local hierarchies that have been created in Workspace Designer. The system displays the status for each object. OK, With Errors, Inactive or does not exist. You see the memory consumption, number of records and further information.

  2. You can remove workspace assignments from the list for local characteristics and hierarchies that no longer exist.

Tab: Workspace Queries

  1. The system displays a list of the workspace queries that have been created in Workspace Designer.

Tab: Users

  1. The system displays a list of users who are authorized to work or run workspace-specific queries in the workspace in question. The authorizations are checked using the assigned roles/profiles in the user master record. The various authorizations (Workspace Designer/query) are displayed in the list using flags.

    Note

    Note however that the list can only contain users that you are authorized to display user master record maintenance for.

Finish Editing the Workspace

  1. Check the workspace. During the check, the system checks the active and revised version if one exists.

    Note

    There are two versions of the check if you have already activated the workspace (active version), made another change and only saved it for the time being (revised version).

  2. Save and activate the workspace. You can only use activated workspaces in Workspace Designer.

More information:

Tips for Editing Workspaces