Use Caseįor this blog post, I have a standard aDSO with technical name : SALESADSO, which contains some sales data for 2019 & 2020. This can be achieved by the program : RSDG_ADSO_ACTIVATE as well as manual activation of the same. For pre-existing aDSOs prior to the introduction of this feature, a reactivation is needed in order to have this view generated. Note : All newly created aDSOs in BW/4HANA 2.0, will have this ‘8’ view generated by default. More details about this can be found in above mentioned SAP help portal link. The reference points are exposed with an additional column with naming convention as following : “ _NCUM_REFP“. There’s another interesting feature for aDSOs with non-cumulative key figures – the marker for non-cumulative keyfigures. The internal & external formats of amount type keyfigures. New controller technical flag : “ COLD_STORE_FLAG”.Ģ. Rather we’ll focus on two important facades of the same :ġ. More information regarding the features of this ‘8’ view can be found in SAP note : 2723506 or here : External SAP HANA SQL View, so I will not repeat all the features in this blog post. However, direct access to these tables is said to be supported in routines scripted in HANA being used in transformations (Reference note : 1682131). It is recommended that the view for external access to be used in mixed modelling scenarios or exposing data to 3rd party consumers, while on the contrary, the usages of the database tables directly are discouraged & not supported by SAP. Now with BW/4HANA 2.0, we have another view generated with name : /BIC/A8 : View for external Access for aDSO. We are all well familiar with the below generated tables & views of aDSOs : (depending on the type of particular aDSO they are relevant) The view is generated with naming convention as following : /BIC (namespace)/A8. In this blog post, I would focus on some of the key aspects of the generated view for external access or the external SAP HANA SQL View for aDSOs in BW/4HANA 2.0 by a use case scenario.
0 Comments
Leave a Reply. |