Skip to Content
Author's profile photo Sibo Zhang

Understand aDSO

In this blog, I’ll talk about several technical perspectives of aDSO.

First of all, if you don’t have a BMT(BW Modeling Tool)  and still want to quickly find out the technical detail of your aDSO, you can refer to table RSOADSO. Here you can find all basic information including settings and types of a certain aDSO.

There are 7 types of aDSOs in total. The classic ones can be mapped to the 7 types so we don’t count them separately. They are:

Enterprise data warehouse architecture

  • Data acquisition layer(Including corporate memory)
  • Corporate memory – compression capabilities
  • Corporate memory – reporting capabilities
  • Data warehouse layer – delta calculation
  • Data warehouse layer – data mart

Planning

  • Planning on Cube-like
  • Planning on Direct Update

The type is defined by 6 different attributes. You can find the 6 attributes in table RSOADSO as 6 corresponding fields.

Attributes

Field Name Description
ACTIVATE_DATA Active Data
WRITE_CHANGELOG Write Chang Log
CUBEDELTAONLY All Chars are key
NO_AQ_DELETION Keep Inbound Data, Reporting on Union of Inbound and Active Table
PLANNING_MODE Planning Mode
DIRECT_UPDATE Direct Update

 

aDSO Types

In BMT, you can find out the aDSO types easily like below

How can you determine it in SAPGUI? You can use one of the below method:

1 via the XML

For example, below is a delta calculation type aDSO. Because the activateData and writeChangelog are marked as true.

2 via the table entry in RSOADSO. See below:

You can refer to below table for the mapping of table fields and the type of aDSO.

Tables

When you create an aDSO, there will be 5 DDIC tables generated by the system. This is regardless of the aDSO type. Their naming conversion is /BIC/A<tech_name>*

Not all tables are being used by the aDSO, this is determined by the type.

Below table is a mapping between aDSO type and the tables being used.

Hope you find this blog useful. I’ll keep updating it.

 

Assigned tags

      9 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Lilu Zhang
      Lilu Zhang

      Good post!

      Author's profile photo Former Member
      Former Member

      Very useful sharing!!! Thanks

      Author's profile photo Andras Margitics
      Andras Margitics

      Great content Sibo, thank you!

      One note, there is another option to check the aDSO model type.

      Tcode: RSA1 -> Manage -> Top menu: General -> Show Settings

       

       

      Best regards, Andras

       

      Author's profile photo Sibo Zhang
      Sibo Zhang
      Blog Post Author

      Thank you Andras!

      Author's profile photo Eleonore Gossart
      Eleonore Gossart

      Good reading, thank you Sibo!!

      Author's profile photo Marco Braun
      Marco Braun

      Dear Mr Zhang,

      may it’s a silly question does it is possible to use aDSOs only with Hana DB or can i create and store aDSOs in different Databases like ASE from Sybase.

      I ask because i check the table “RSOOBJXREF” and find some objects with type ADSO and version “D”. I have a test system 7.52 on ASE. A Search over google for aDSOs return only results about Hana.

      For a short answer i would be very thankful

      best regards

      Marco

      Author's profile photo Mark Hall
      Mark Hall

      Very helpful, thanks!

      Author's profile photo D D
      D D

      Dear Mr Zhang,

       

      Thanks for your blog.

      Using ADSO I still have one open point, in which business scenario, would I must use a ADSO type Cube rather than an ADSO type DSO ?

      Do we still need cube in our dataflow, as on SAP on HANA creating reports on DSO will no more have performance issue ?

      Maybe you owuld know ?

       

      Regards

      DD

      Author's profile photo Narayanan Sanhameswaran
      Narayanan Sanhameswaran

      Thangs Mr. Zhang.

      I attached a planning mode- direct update ADSO to a Composite Provider and checked the Navigational Attribute and attached to an Aggregate level and created a query.  When I execute the query it is input-ready with the characteristic  and its related navigational attribute.  But when I don't include the characteristics and only include the navigational attribute the Key figure looses its input-ready mode.  What do I do to make this query input-ready if I plan using the navigational attribute.

      Pl. help