New in SAP NetWeaver BW 7.30
Reduce Costs Using Semantic Partitioned Objects

  • by Dirk Morgenroth, MSc, Senior Consultant for Business Intelligence, Atos, Vienna
  • June 13, 2012
Find out how Semantic Partitioned Objects (SPOs) can help you limit costs and increase data analysis performance. Also, receive an overview of how to generate SPOs through a step-by-step process using the SPO wizard.
Key Concept

The Semantic Partitioned Object (SPO) is available in the SAP NetWeaver BW 7.30 release. The SPO is a newly introduced InfoProvider type that comprises one to 99 structurally equal InfoProviders. Semantic partitioning is triggered by a property of the InfoProvider. Currently, standard InfoCubes as well as standard and write-optimized DataStore objects are supported. 

Logical partitioning can handle challenges of data volume increase as well as performance. However, one downside is that the logical partitioning scenario comes at a cost: That cost is hidden in the set-up, maintenance, and enhancements efforts of a traditional partitioned InfoCube or DataStore object (DSO) landscape. Those efforts can add up considerably to the overall solution costs when examined after the fact. This is where Semantic Partitioned Objects (SPOs) come into play.

SPOs greatly reduce set-up, maintenance, and enhancement costs by offering an efficient, wizard-driven, template-oriented process to generate a new InfoProvider type that comprises well-known data targets.

A typical example of a costly activity that SPOs can streamline is adaptations of structurally equal data models to partition data by years (e.g., cost center data). Every single adaptation of one data model needs to be repeated for the other structurally equal objects. This involves several repetitive and error-prone steps (e.g. altering the data models themselves, altering the data flows that lead into them).

An SPO can reduce some of these manual, repetitive tasks by introducing the idea of reference structures: You define a reference structure once and let the system take care of the generation and adaptation of structurally equal structures derived from the reference structure.

Dirk Morgenroth, MSc

Dirk Morgenroth, MSc, is a senior consultant for business intelligence at Atos, Vienna, formerly Siemens IT Solutions and Services. As a certified SAP application professional with six years of hands-on experience in SAP NetWeaver BW, he covers the complete SAP BI life cycle, and supports clients in defining their BI strategy and in designing, implementing and maintaining their individual data warehouse solutions.

If you have comments about this article or would like to submit an article idea, please contact the BI editor.

Dirk will be presenting at the upcoming SAPinsider HANA 2017 conference, June 14-16, 2017, in Amsterdam. For information on the event, click here.

See more by this author


10/23/2017 10:48:49 PM

In which Scenario we can use SPO?

How much data volume justify the use of SPO (Cube) and SPO (DSO)?

Please log in to post a comment.

To learn more about subscription access to premium content, click here.