Creating Semantically Partitioned Object(SPO) in BW 7.3
SAP NetWeaver Business Warehouse 7.30 (BW7.30)
This paper provides details and step by step procedure for creating Semantically Partitioned Object (SPO) based on DSO.
Company: L&T Infotech Ltd
Created on: 02 November 2012
Vishnudas Narayana Mangalam is working as SAP-BI Consultant in L&T Infotech Ltd and has worked on BW Implementation/Support Projects.
Table of Contents
Reduced Manual Effort
Step by Step Procedure For Creating SPO based on DSO
A semantically partitioned object is an Info Provider that consists of several Info Cubes or Data Store objects with the same structure. The goal of semantic partitioned objects (SPOs) is to model a semantic partition once and then apply the model repeatedly in order to create and maintain highly scalable data containers while reducing development efforts.
· An SPO is based on either a DSO or an InfoCube.
· Each SPO is made of multiple data providers of the same type with identical structure.
· Each of the underlying data providers behaves like a “regular” DSO or Cube, with its own metadata tables, data tables, data flows and sources/targets, and are independent of each other.
· Each SPO will have a so called Master provider, which acts as a template based on which the part providers are built.
· While defining metadata for the SPO, the definition is being made implicitly to the master provider, which is then used as a template to create the part providers
· The part providers are read only, changes to them can be made only via the master provider
· When a SPO is created, a reference structure keeps track of the partitions. The structure is placed in the Multi Provider for querying.
· SPO Wizards create all Data Transfer Processes (DTP), transformations, filters for each data store and a process chain automatically.
· Applicable for DSO and Cubes
· Better performance with mass data
o Reduced Query Run time for large data volume
· Close data connection
o Better Error handling and partitioned data available for reporting and analysis
· Working with different time zones
o Separation can be done on time zones. Helpful when we have multiple source systems and single BW instance
Reduced Manual Effort
In earlier SAP NetWeaver BW releases, multiple manual steps are required to achieve semantic partitioning and scalable data containers. For example, if an administrator needs to create 20 partitions (broken down by geography, year, business unit, and so on), he or she has to run through every step manually, linking transformations and data transfer processes (DTPs) and creating process chains. And if the partitions need to be modified, then the administrator has to start over and apply each change manually.
With SAP NetWeaver BW 7.3, semantic partitioning has been significantly simplified with a wizard that automates the creation of SPOs and guides users through the process. An administrator can now use automated semantic partitioning to create InfoProviders that consist of multiple DataStore Objects or InfoCubes with the same structure. This leads to highly scalable data containers when data is loaded. An administrator can also load the objects in parallel, enabling better performance.
This automation drastically reduces the manual effort required to create, maintain, and change semantic partitions, and it enables fast implementation of enterprise data warehousing with SAP NetWeaver BW.
Step by Step Procedure For Creating SPO Based On DSO
Go to transaction RSA1.
From the required InfoArea right click and select the option “Create DataStore Object”.
Fill the required Technical details for DSO. Check Semantically Partitioned.
You can choose a template or add objects manually. SPO can be used as a template for creating another object.
To create a new template Select ObjectType as “Semantically Partitioned Object” and then click on Create.
To create based on existing template Select ObjectType as “Datastore Object” and then click on Create.
Step 3 :
Click Maintain object and in Object Maintenance screen Click on Save.
If any changes are required in maintenance of object, make the necessary changes and save.
Step 4 :
Click on Maintain Partitions.
First step is to choose the infoObject(s) on which the partition criteria is to be defined. This is based on the business logic.
Step 5 :
Select the required characteristics and transfer to selected characteristics list in Partitioning Criteria.
Step 6 :
Click on Continue.
Partition 01 is created by default as shown below. Specify the partition criteria.
For giving range uncheck the single value checkbox.
There is an option to add multiple partitions, either based on time or a fixed number of partitions.
The time-based partitioning option allows you to specify number of partitions based on available time characteristics
Add another set of partitions if multiple partitions are required. To avoid creation of partitions manually incase of fixed intervals, click multiple partitions
Step 9 :
In Partitions Maintenance screen give the necessary details as shown. This depends on interval and partitions we want to create.
Step 10 :
Partitions are automatically created based on the periods per partition. If required these can be edited.
Step 11 :
Once partitions are created Click on Start Activation.
Step 12 :
Once the activation is done logs are displayed as shown below.
Click on Create transformation.
Fill the necessary details in the transformation maintenance screen.
1 transformation is sufficient for all the partitions.
The field mappings are automatically generated.
Step 14 :
Activate the transformation.
Step 15 :
Create Data Transfer Process .
From DTP Templates section create a new template and save the entries.
Step 16 :
Select the template and all the datasources in various partitions. Click on Assign DTP’s to selection.
Click on Save
Select all the DTPs and click on Generate
1 by 1 all the DTPs will get generated automatically.
Click on Create Process Chain.
Click on Add to add the DTPs
The sequence of the DTPs can be changed and then save.
Click on Generate to activate the chain.
Save the start process if the start criteria is as desired.
Process chain is now created and activated.
Step 18 :
The complete data flow for the Semantically Partitioned Object (for DSO ) is as shown below.
Refresh the tree. The entire dataflow is created.