sap first guidance - bw on hana...

SAP First Guidance

SAP NetWeaver BW 7.4 SP8 or higher

SAP HANA™

Applicable Releases:

SAP BW 7.4 SP8, powered by HANA

and higher

This First Guidance document is part of a series of documents that should help to better understand the various concepts of SAP BW powered by SAP HANA. The documents are still “work in progress”, so these guides are not intended to be exhaustive so far, and might never be. The purpose of these documents is to deliver additional information besides SAP Help and blogs to get a better understanding of the concepts of SAP BW powered

by SAP HANA.

Version 1.0

February 2016

First Guidance... Using Advanced DataStore Objects in SAP BW powered by SAP HANA

© Copyright 2015 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP AG. The

information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9, iSeries,

pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,

OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power

Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,

MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and

Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other

countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open

Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,

and MultiWin are trademarks or registered trademarks of Citrix Systems,

Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks

of W3C®, World Wide Web Consortium, Massachusetts Institute of

Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and other

countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other

Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business

Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Sybase, Inc.

Sybase is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this

document may be reproduced, copied, or transmitted in any form or for

any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license

agreement or any other agreement with SAP. This document contains

only intended strategies, developments, and functionalities of the SAP®

product and is not intended to be binding upon SAP to any particular

course of business, product strategy, and/or development. Please note

that this document is subject to change and may be changed by SAP at

any time without notice.

SAP assumes no responsibility for errors or omissions in this document.

SAP does not warrant the accuracy or completeness of the information,

text, graphics, links, or other items contained within this material. This

document is provided without a warranty of any kind, either express or

implied, including but not limited to the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without

limitation direct, special, indirect, or consequential damages that may

result from the use of these materials. This limitation shall not apply in

cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not

affected. SAP has no control over the information that you may access

through the use of hot links contained in these materials and does not

endorse your use of third-party Web pages nor provide any warranty

whatsoever relating to third-party Web pages.

SAP “How-to” Guides are intended to simplify the product implement-

tation. While specific product features and procedures typically are

explained in a practical business context, it is not implied that those

features and procedures are the only approach in solving a specific

business problem using SAP NetWeaver. Should you wish to receive

additional information, clarification or support, please refer to SAP

Consulting.

Any software coding and/or code lines / strings (“Code”) included in this

documentation are only examples and are not intended to be used in a

productive system environment. The Code is only intended better explain

and visualize the syntax and phrasing rules of certain coding. SAP does

not warrant the correctness and completeness of the Code given herein,

and SAP shall not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change

in these components may cause unpredictable and severe malfunctions

and is therefore expressively prohibited, as is any decompilation of these

components.

Any Java™ Source Code delivered with this product is only to be used by

SAP’s Support Services and may not be modified or altered in any way.

Document History

Document Version Description

1.00 First official release of this guide

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA

March 2016 1

Table of Contents

1. Introduction ........................................................................................................................... 2

1.1 Services provided by the aDSO ....................................................................................... 2

2. Requirements ........................................................................................................................ 4

2.1 Back-End Requirements .................................................................................................. 4

2.2 Requirements for the modeling environment .............................................................. 4

2.3 Conversion of classic objects to the aDSO .................................................................... 4

3. Understanding the Modeling Properties ............................................................................... 5

3.1 Introduction ....................................................................................................................... 5

3.2 Data Example Overview ................................................................................................... 7

3.3 Data Example 1 .................................................................................................................. 8

3.3.1 Characteristics of Combination ......................................................................... 9

3.3.2 Data Load Results ............................................................................................... 9

3.3.3 Aggregation of Reporting View after load ....................................................... 10

3.4 Data Example 2 ................................................................................................................ 11

3.4.1 Characteristics of Combination ....................................................................... 12

3.4.2 Data Load Results ............................................................................................. 12


3.5 Data Example 3 ............................................................................................................... 14




3.6 Data Example 4 ............................................................................................................... 17




3.7 Data Example 5 .............................................................................................................. 20



3.7.3 Aggregation of Reporting View after load .......................................................22

3.8 Selecting the modeling properties using LSA++ templates ......................................23

3.9 Using the extended table property of the aDSO (for dynamic tiering) .................... 24

4. Bypassing the PSA tables with the aDSO and ODP Framework ......................................... 24

5. Consuming the aDSO .......................................................................................................... 26

5.1 Is a virtual layer still required? ...................................................................................... 26

5.2 Unsupported Data Types ............................................................................................... 27

5.3 Navigational Attributes ................................................................................................. 29

5.3.1 Navigational Attributes for Data Staging ....................................................... 30

5.3.2 Transitive Attributes ........................................................................................ 30

5.4 Export DataSource ......................................................................................................... 31


March 2016 2

1. Introduction

In recent years SAP’s approach to data warehousing has gone through a period of evolution. Moving

away from traditional techniques, SAP BW 7.4 powered by SAP HANA opens the door for new modeling

possibilities, enabling a leaner and more agile environment.

The advanced Data Store Object (aDSO) is a new object type introduced in SAP BW 7.4 SP8 powered by

SAP HANA, The aDSO simplifies data persistency consolidating the InfoCube, Data Store Object (write-

optimized, standard and direct update) and PSA tables of prior releases.

When implementing the aDSO, it is important to understand the configuration options available and the

scenarios in which they are designed to be used. It is the aim of this document to provide such

information as well as general guidance for the use of the aDSO.

Superseded objects are referred to in this document as ‘classic objects’ or individually prefixed with the

word ‘classic’ (e.g. classic InfoCube).

Whilst classic objects are supported and may still be required in certain scenarios (check Note 2070577),

there are advantages to adopting the aDSO. The aDSO;

- Represents a single object for data persistency, simplifying the modeling and support

environment

- Provides greater control over the structure and behaviour of the object (using properties to mimic

the behaviours of classic objects)

- Can be modelled using fields, InfoObjects or a combination of both

- Provides integration with other new tools in the modern DW, namely, the Composite Provider and

the Open ODS view

- Has advanced remodeling capabilities to reduce the impact and time to implement changes

- Has new request handling capabilities for optimizing high data volumes

- Will be SAP’s strategic object for data persistency in BW powered by SAP HANA moving forward

1.1 Services provided by the aDSO When deciding whether to use BW to persist data for reporting, it is important to understand the

requirement for storage and data management services. The aDSO inherits the Data Warehousing

services from the classic BW objects. These include:

- Options for request handling, rollback and reload on committed (and activated) data

- Controlled error handling

- Built in Delta handling capabilities

o For various types of delta records, ‘After, Before, Reverse’ (ABR), ‘Additive’ (ADD), ‘After

Image’ (AIM, AIMD) and like data sources and

o For movement of data within the DW

- Robust application lifecycle management framework

- Pre-delivered business content

- Fully integrated scheduling and monitoring capabilities

- Integrity checks (for master data)

- Advanced authorisation concept (including hierarchy level)

- Optimized access for reading and reporting

- Content specific storage options (such as non-cumulative key figures)


March 2016 3

- Business Planning capabilities

References

For more information about the aDSO, please take a look at the following resources:

aDSO Help Documentation

New Modeling Tools Video Series

2070577 - (advanced) DataStore Object - availability in BW7.4 SP08, SP09 and SP10

http://help.sap.com/saphelp_nw74/helpdata/en/25/3a8dd2746045ea9b84fedd8b966609/content.htm

http://scn.sap.com/docs/DOC-64470

http://service.sap.com/sap/support/notes/2070577


March 2016 4

2. Requirements

2.1 Back-End Requirements The aDSO object type is available from BW 7.4 SP8 powered by SAP HANA, however, SAP highly

recommends using the latest release and support package (check the PAM). For customers using BW 7.4

SP8 – SP11, note 2070577 should be reviewed to ensure all relevant and critical fixes have been applied.

Additional features have been included incrementally from SP8 – SP11, for a list of these features and

corresponding availability please review the attachment to note 2070577.

References

For more information about the aDSO back-end requirements, please take a look at the following

resources:

Product Availability Matrix

2070577 - (advanced) DataStore Object - availability in BW7.4 SP08, SP09 and SP10

2.2 Requirements for the modeling environment The BW modeling tools in Eclipse are used to model the aDSO object. The object cannot be created or

edited in the SAP GUI however it is visible to the RSA1 InfoProvider tree. For modellers, it is highly

recommended to use the latest version of the BW development plug-in for Eclipse. Detailed instructions

on how to install and or upgrade the Eclipse environment for BW modeling can be found on the BW Video

Series SDN page (see references).

References

For more information about the aDSO front-end requirements, please take a look at the following

resources:

New Modeling Tools Video Series

Download BW Modeling Tools

2.3 Conversion of classic objects to the aDSO A tool for converting the classic objects to the aDSO is planned from BW 7.5 SP2. For customers on a

prior release there is an option to convert objects manually. This process is described in the SCN blog in

the reference section below.

References

For more information about convesrion to the aDSO, please take a look at the following

resources:

Blog - Converting DataStore objects and InfoCubes into advanced DataStore objects:

2238220 - BW4HANA: Transfer Enhancements

https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/support/pam/pam.html?smpsrv=https%3a%2f%2fwebsmp207.sap-ag.de#ts=0

http://service.sap.com/sap/support/notes/2070577


https://tools.hana.ondemand.com/#bw


https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3232333832323026


March 2016 5

3. Understanding the Modeling Properties

3.1 Introduction The aDSO inherits the same physical table structure of the classic standard DSO. The object is made up

of three tables, which may or may not be used depending on the scenario.

In addition to the physical tables, two views are created, one for data extraction and the other for

reporting. The data extraction view is relevant only for initial and full loads.

The aDSO physical structure, views and behaviour can be controlled using the modeling properties

highlighted below. By selecting different property combinations, the aDSO can mimic the structure and

functionality of any classic object.

Active Data Table

@ <Field Key>

@ <Field Key>

RECORDMODE

<Field>

………

Change Log Table

@ REQUSN

@ DATAPAKID

@ RECORD

RECORDMODE

<Field Key>

<Field Key>

<Field>

………….

………

Inbound Data Table

@ REQUSN

@ DATAPAKID

@ RECORD

RECORDMODE

<Field Key>

<Field Key>

<Field>

………….

Table structure of the aDSO

Activation Process Activation Process


March 2016 6

–

Note

The extended table property alters the physical location of the data which does not cause the

aDSO to behave differently hence this property will not be included in the data examples below

(for more information on the extended table property refer to the relevant section below).

The Unique Data Records property should only be activated where the uniqueness of the records

is guaranteed by the source and is designed only to accelerate load performance. This property

bypasses BW’s built in referential check and does not impact the structure or behaviour of the

aDSO. Again, this will not be included in the data examples.

How records should be processed will depend on both the source of the data and the purpose of the

object. For example, records may be extracted from the source using an after image delta mechanism,

but it’s only after looking at the purpose of the object that a decision can be made about the structure and

behaviour. An aDSO used for reporting current data (typically within the propagation or reporting layer of

the LSA++) will have different properties to one used for storing historical data movements (typically

within the Open ODS or corporate memory layers of the LSA++). These requirements may be aligned with

layers in the LSA++ methodology, hence it may be helpful to use or review the LSA++ templates available

which populate these properties. For more information please see section 3.8 Selecting the modeling

properties using LSA++ templates

References

For more information about convesrion to the aDSO, please take a look at the following

resources:

Help – Templates for Modeling the Data Warehousing Layers

Help – aDSO modeling properties

http://help.sap.com/saphelp_nw74/helpdata/en/b7/6fca02fa804d569c386b9b437f85d6/content.htm

http://help.sap.com/saphelp_nw74/helpdata/en/19/61a9b62f054cc5a4f0d98485b82fa9/content.htm?frameset=/en/b7/6fca02fa804d569c386b9b437f85d6/frameset.htm&current_toc=/en/a0/efe8240b754ee4ac1acc1ff57fa87c/plain.htm&node_id=52


March 2016 7

3.2 Data Example Overview To illustrate the impact of the different modeling properties, the following section of the document will

use a simple data example. Data will be loaded into a set of aDSO’s with different combinations of the

modeling properties selected, the result in the underlying tables and views will be shown for each step.

There are five possible combinations of modeling properties which could be selected in the aDSO

maintenance screen, these are depicted below in Example 1 – 5.

Example 1

Example 2

Example 3

Example 4

Example 5

For each of these examples, two requests are loaded. The first request loads new records into the aDSO,

the second request loads a delta or ‘change’. If activation is possible, it occurs after each load. The key of

the data is not applicable for some combinations, in these cases the key is ignored in the aDSO definition.

New Data Request

DOCNUMBER (KEY) DOCITEM (KEY) AMOUNT STATUS

100 1 10 A

100 2 20 A

Delta Data Request

DOCNUMBER (KEY) DOCITEM (KEY) AMOUNT STATUS

100 1 20 A

100 2 20 B

Record with indicative key 100/1 demonstrates an update to a key figure

Record with indicative key 100/2 demonstrates an update to a characteristic

The contents of the tables and views will be shown in the different load states

1. After initial data load (new data request)

2. After activation of initial data load

3. After delta data Load (delta data request)

4. After Activation of delta data load


March 2016 8

3.3 Data Example 1

Definition

Note

This Property combination does not allow a user defined key

The figure below shows the table structure which is activated for this property combination.


March 2016 9

3.3.1 Characteristics of Combination

Similar to (classic object) PSA table, Write-Optimised DSO

Usage Data Acquisition Layer, Corporate Memory Layer

Key System Defined, Request ID/Record

Delta Processing (reporting accuracy) ‘Additive Delta’ (ADD), ‘After, Before and Reverse’ (ABR)

Outbound Delta Mechanism Inherited from the inbound data source

Reporting Availability Immediately after load

Validity of Extraction Delta Immediately after load

Rollback/Request Deletion All loaded data

3.3.2 Data Load Results

Object Table Object View

1. Data Load

Inbound table

Change Log table

N/A

Active table

N/A

Extraction View

Reporting View

Note: Data is available for reporting and extraction

immediately after loading

2. Activate Data Load - Data cannot be activated for this property combination

3. Delta Load

Inbound table

Change Log table

N/A

Active table

N/A

Extraction View

Reporting View

4. Activate Delta Load - Data cannot be activated for this property combination


March 2016 10

3.3.3 Aggregation of Reporting View after load

By Doc Number and Doc Item

By Status

Caution

When using this property combination for reporting be mindful that all requests are aggregated

which may produce incorrect results if only ‘after image’ delta records are received.


March 2016 11

3.4 Data Example 2 Definition



March 2016 12


Similar to (classic object) Not similar to any classic object

Usage Corporate Memory or Reporting (please be aware of

limitations regarding rollback)

Key User Defined

Delta Processing (reporting accuracy) ‘Additive Delta’ (ADD)*, ‘After, Before and reverse’ (ABR),

‘After Image’ (AIM, AIMD)

Outbound Delta Mechanism Inherited from the inbound data source

Reporting Availability Active data only

Validity of Extraction Delta Only before data activation, once data is activated delta

extraction is not possible

Rollback/Request Deletion Only before data activation, once data is activated

rollback is not possible

* Assuming Summation is selected on the Key Figures within the transformation definition



1. Data Load

Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View

Note: Extraction is available immediately after

loading. Reporting is not available until activation

2. Activate Data Load

Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View


March 2016 13

3. Delta Load

Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View

4. Activate Delta Load

Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View

Note: Full delta extraction is not available once the

object is activated. Be mindful of the data extraction

requirements when considering this option.

3.4.3 Aggregation of Reporting View after load By Doc Number and Doc Item

By Status


March 2016 14




March 2016 15


Similar to (classic object) Standard DSO

Usage Propagation Layer

Key User Defined



Outbound Delta Mechanism ‘After, Before and reverse’ (ABR)


Validity of Extraction Delta For as long as data exists in Change Log

Rollback/Request Deletion For as long as data exists in Change Log




1. Data Load

Inbound table

Change Log table

Active table

Extraction View

Reporting View

Note: Extraction and Reporting are not available

until the data load has been activated


Inbound table

Change Log table

Active table

Extraction View

Note, the extraction view is only used for full and

delta initialisation.

Reporting View


March 2016 16

3. Delta Load

Inbound table

Change Log table

Active table

Extraction View

Reporting View


Inbound table

Change Log table

Active table

Extraction View

Note, the extraction view is only used for full and

delta initialisation. Delta extraction uses the change

log table

Reporting View

3.5.3 Aggregation of Reporting View after load By Doc Number and Doc Item

By Status


March 2016 17




March 2016 18


Similar to (classic object) Not similar to any classic object

Usage Corporate Memory

Key User Defined



Outbound Delta Mechanism Inherited from the source data


Validity of Extraction Delta For as long as data exists in the inbound table, retained by

default

Rollback / Request Deletion For as long as data exists in the inbound table, retained by

default




1. Data Load

Inbound table

Change Log table

Active table

Extraction View

Reporting View


Inbound table

Change Log table

Active table

Extraction View

Reporting View


March 2016 19

3. Delta Load

Inbound table

Change Log table

Active table

Extraction View

Reporting View


Inbound table

Change Log table

Active table

Extraction View

Reporting View



By Status


March 2016 20


Note

This Property combination does not allow a user defined key



March 2016 21


Similar to (classic object) InfoCube

Usage Propagation / Reporting Layers

Key All Characteristics are key

Delta Processing (reporting accuracy) ‘Additive Delta’ (ADD), ‘After, Before and reverse’ (ABR)

Outbound Delta Mechanism Inherited from the source data

Reporting Availability Immediately after load

Validity of Extraction Delta Inactivated data only

Rollback Inactivated data only



1. Data Load

Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View


Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View

3. Delta Load

Inbound table Extraction View


March 2016 22

Change Log table

N/A

Active table

Reporting View


Inbound table

Change Log table

N/A

Active table

Extraction View

Reporting View



By Status


March 2016 23

3.8 Selecting the modeling properties using LSA++ templates The flow chart below may assist in the selection of the modeling properties.


March 2016 24

3.9 Using the extended table property of the aDSO (for dynamic tiering)

As of BW7.5 SP1, the option to assign the aDSO to extended storage (dynamic tiering) is available for all

aDSO types. The use of this option should be aligned to the overall data aging strategy of the customer;

detailing when and how data is aged. This may also include the use of BW NLS.

The differences between dynamic tiering and BW NLS are highlighted below

At the time of writing this document, extended storage is allocated at the table level (a table either

belongs to the extended storage or it doesn’t).

Note

Dynamic tiering and NLS may require additional licenses and hardware.

References

For more information about the aDSO extended property functionality, please take a look at the following resources: Note 205763 – Conversion of PSA and write-optimised DSOs in SAP-HANA extended tables

4. Bypassing the PSA tables with the aDSO and ODP Framework

The PSA table can be bypassed by using the aDSO and Operation Data Provisioning (ODP) framework

under the following circumstances

- Data is extracted from an ABAP-based SAP Source System

- The DataSource is ODP enabled AND,

- Data Extraction mechanism is set to ‘Directly from the source system’ on the DTP (to bypass the

PSA)

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3230353736333626


March 2016 25

The process is described as follows

References

For more information about the aDSO extended property functionality, please take a look at the following resources:

ODP Framework Help Documentation

http://help.sap.com/saphelp_nw74/helpdata/en/c6/afacb707764885a6fb62f511c24f34/content.htm?frameset=/en/c6/afacb707764885a6fb62f511c24f34/frameset.htm&current_toc=/en/a3/fe1140d72dc442e10000000a1550b0/plain.htm&node_id=119&show_children=true#jump119


March 2016 26

5. Consuming the aDSO

5.1 Is a virtual layer still required? Creating an abstraction between the data model and the end-user report is still fundamental to good data

warehouse design. In fact, this concept may have even more relevance, given the new data acquisition

options available (for example virtualisation through SDA).

For the aDSO, it is recommended to use the Composite Provider or Open ODS view within the

Virtualisation layer and not to report directly off the aDSO itself.

References


How to implement virtual integration of external data with SAP BW powered by SAP HANA

BW

Query

BW

Query

BW

Query

aDSO

Not Recommended

aDSO aDSO

Composite

Provider

aDSO

OODSV

Recommended Recommended where the aDSO

is generated from Open ODS

View

Generated

Dataflow

http://go.sap.com/docs/download/2016/02/1ccf360a-617c-0010-82c7-eda71af511fa.pdf

http://go.sap.com/docs/download/2016/02/1ccf360a-617c-0010-82c7-eda71af511fa.pdf


March 2016 27

5.2 Unsupported Data Types With the introduction of field-based modeling, some data types available in the aDSO are not visible for

reporting or consumption directly in BW. A full list of supported data types can be found in note 2185212.

For data types which are not supported for reporting, an Open ODS View can be used to convert the field

into a supported data type.

Example: Querying an unsupported data type

In the example below an aDSO is created with the field DESCRIPTION defined as a ‘Sting’ which is not a

supported data type of BW.

When the aDSO is queried directly, only supported data types are made available. (note in the example

below that DESCRIPTION is not available as a drill down)


March 2016 28

Also note that the field DESCRIPTION will not be available in the Composite Provider definition. This is

because the Composite Provider does not provide data type conversion.

To make the field accessible for reporting an Open ODS view must be used.

In this example, an Open ODS view is created using the aDSO as the source.

By using the Open ODS view, the application will automatically apply the conversion on the field

DESCRIPTION.

When the Open ODS view is queried, the field DESCRIPTION is available.


March 2016 29

5.3 Navigational Attributes Unlike classic objects, consumption options for the aDSO can only be defined in the virtualisation layer

objects (using the OpenODS View or the CompositeProvider). These include

- Creating semantic associations with data residing in BW (for example an Open ODS view or

InfoObject)

- Defining compounding characteristics for InfoObjects

- Assigning navigational attributes

Example: Activating a Navigational Attribute for Reporting

In the following example the navigational attributes associated with InfoObject 0D_NW_PRID are

activated.

In the Composite Provider definition, go to the output tab


March 2016 30

Right click the object which stores the navigational attributes (in this case 0D_NM_PRID) and select

navigational attributes

Select the navigational attributes to add and click OK

5.3.1 Navigational Attributes for Data Staging A less common use for the navigational attribute is for data staging; used within a transformation or as a

data filter within a DTP. As of BW7.5 SP1 there is an option for selecting a navigational attribute within the

aDSO, this feature is only relevant for data staging scenarios and has no impact on reporting.

5.3.2 Transitive Attributes A characteristic in an InfoProvider can have navigational attributes, which can be used to navigate within

queries. These navigational attributes can themselves also have navigational attributes, which are called

transitive attributes. In the diagram below characteristic 0COSTCENTER has attribute 0COMP_CODE.

0COMP_CODE has an attribute 0COMPANY. In this case 0COMPANY is considered a transitive attribute.

Traditionally there have been challenges in incorporating transitive attributes into a data model for

reporting.


March 2016 31

Whilst it is planned to include functionality specifically for modeling transitive attributes, transitive

attributes can be modelled today by using a left outer join between the individual InfoObjects within the

Composite Provider.

5.4 Export DataSource To transfer data from the aDSO to another BW system, an ODP DataSource must be used. To set up the

ODP DataSource, the process described in the SAP help documentation should be followed (see

reference section).

Prior to BW7.5 SP1, only full extraction was available for this scenario.

References


Help Documentation: Exchanging Data between BW Systems Using the ODP Source System

http://help.sap.com/saphelp_nw74/helpdata/en/ef/3341bc65c747fba1509fdfb250b452/content.htm?frameset=/en/4a/12e84976df1b42e10000000a42189c/frameset.htm&current_toc=/en/a3/fe1140d72dc442e10000000a1550b0/plain.htm&node_id=396

http://help.sap.com/saphelp_nw74/helpdata/en/ef/3341bc65c747fba1509fdfb250b452/content.htm?frameset=/en/4a/12e84976df1b42e10000000a42189c/frameset.htm&current_toc=/en/a3/fe1140d72dc442e10000000a1550b0/plain.htm&node_id=396

www.sap.com/contactsap

www.sdn.sap.com/irj/sdn/edw-ops

http://www.sap.com/contactsap

http://www.sdn.sap.com/irj/sdn/edw-ops

sap first guidance - bw on hana...

Documents