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
36
Embed
SAP First Guidance - BW on HANA 1a248.g.akamai.net/n/248/420835/73daf8bcebd0f3209494f2caa4f125517… · SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 11
3.4 Data Example 2 Definition
The figure below shows the table structure which is activated for this property combination.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 12
3.4.1 Characteristics of Combination
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
3.4.2 Data Load Results
Object Table Object View
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 14
3.5 Data Example 3 Definition
The figure below shows the table structure which is activated for this property combination.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 15
3.5.1 Characteristics of Combination
Similar to (classic object) Standard DSO
Usage Propagation Layer
Key User Defined
Delta Processing (reporting accuracy) ‘Additive Delta’ (ADD)*, ‘After, Before and reverse’ (ABR),
‘After Image’ (AIM, AIMD)
Outbound Delta Mechanism ‘After, Before and reverse’ (ABR)
Reporting Availability Active data only
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
* Assuming Summation is selected on the Key Figures within the transformation definition
3.5.2 Data Load Results
Object Table Object View
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
2. Activate Data Load
Inbound table
Change Log table
Active table
Extraction View
Note, the extraction view is only used for full and
delta initialisation.
Reporting View
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 16
3. Delta Load
Inbound table
Change Log table
Active table
Extraction View
Reporting View
4. Activate Delta Load
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 17
3.6 Data Example 4 Definition
The figure below shows the table structure which is activated for this property combination.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 18
3.6.1 Characteristics of Combination
Similar to (classic object) Not similar to any classic object
Usage Corporate Memory
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 source data
Reporting Availability Active data only
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
* Assuming Summation is selected on the Key Figures within the transformation definition
3.6.2 Data Load Results
Object Table Object View
1. Data Load
Inbound table
Change Log table
Active table
Extraction View
Reporting View
2. Activate Data Load
Inbound table
Change Log table
Active table
Extraction View
Reporting View
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 19
3. Delta Load
Inbound table
Change Log table
Active table
Extraction View
Reporting View
3. Activate Delta Load
Inbound table
Change Log table
Active table
Extraction View
Reporting View
3.6.3 Aggregation of Reporting View after load
By Doc Number and Doc Item
By Status
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 20
3.7 Data Example 5 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.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 21
3.7.1 Characteristics of Combination
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
3.7.2 Data Load Results
Object Table Object View
1. Data Load
Inbound table
Change Log table
N/A
Active table
Extraction View
Reporting View
2. Activate Data Load
Inbound table
Change Log table
N/A
Active table
Extraction View
Reporting View
3. Delta Load
Inbound table Extraction View
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
March 2016 22
Change Log table
N/A
Active table
Reporting View
3. Activate Delta Load
Inbound table
Change Log table
N/A
Active table
Extraction View
Reporting View
3.7.3 Aggregation of Reporting View after load
By Doc Number and Doc Item
By Status
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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)
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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.
SAP First Guidance - New Installation/Import– SAP NetWeaver BW powered by SAP HANA
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
For more information about the aDSO extended property functionality, please take a look at the following resources:
Help Documentation: Exchanging Data between BW Systems Using the ODP Source System