What’s New in the SAP BW/4HANA Content Add-On 1.0 SP16 & 2.0 SP06
You might have been wondering what we have been up to in the recent months.
We have been eagerly working on getting the latest Support Package for the BW/4HANA Content ready.
BW/4 Content(B) SP16 for BW/4HANA 1.0
BW/4 Content(B) SP06 for BW/4HANA 2.0
Let’s have a closer look what’s in
- A new data flow for SAP S/4HANA Service
- SAP S/4HANA Finance Universal Journal foundation
- SAP S/4HANA specific InfoObjects
SAP S/4HANA Service
A whole new Dataflow for the SAP S/4HANA Service area as depicted here.
The data flow brings SAP S/4HANA Service contracts data into your SAP BW/4HANA extending the existing data flows for SAP S/4HANA Service.
Possible scenarios are
- analyzing expiring service contracts
- top selling product by service contracts
- service order net amounts
- completion rates
- open service orders
- service confirmation net amounts, numbers
- unplanned service orders
You can also check out the blog by our colleagues from SAP S/4HANA service.
SAP S/4HANA Finance – Universal Journal
You say ACDOCA, and we finally say YEAH!
Data Flow S/4 FI: GL Account Line Item (/IMO/DF_FI401) provides all fields/InfoObjects that you know from your SAP S/4HANA source system to SAP BW/4HANA.
You can use the DSO delivered in this data flow as foundation to get you going faster during project implementations for customized financial reporting scenarios.
Some basic calcuations have already been done in the transformation into the DSO, e.g. determination of clearead items as well as statistical orders, wbs elements
etc.. Debit, Credit, Turnover key figures are not part of the show. But they can easily be configured either in a transformation into a further staging DSO or on top of a Composite Provider, using SQL expressions or restricted/calculated key figures, whichever suits you best.
One small detail you might notice is the extended key figure length fitting nicely to the extended data types of SAP S/4HANA Finance:
Admittedly it is (still) not possible to achieve this by standard means in SAP BW/4HANA, hence we also resorted to note 460652.
SAP S/4HANA New InfoObjects
You will see some new InfoObjects that you haven’t seen so far starting out with 0S4…, like 0S4PRODUCT based on the CDS view structures.
Building SAP S/4HANA content we have focused on integrated master data as well and hence have decided to create a dedicated set of characteristics fitting particularly to the APIs (CDS views in this case) provided by SAP S/4HANA.
And yes this includes some of the big/central ones, like material, plant, customer, you name it.
Here is a short list covering the major ones.
You will find more in your system, also many new ones referencing the ones listed in the table above, e.g. 0S4BPSOLDTO, 0S4BPSHIPTO, and 0S4BPBILLTO referencing to 0S4BPARTNER. The extensive list of InfoObjects shipped with the BW/4HANA Content can be found attached to note 2395613.
Wherever possible theses new InfoObjects are or will be integrated into the SAP S/4HANA specific data models in SAP BW/4HANA. We are aware that this change might be troublesome for some of you with a multi-source system landscape including older ERP versions like SAP ECC.
Be reminded of the flexible modeling capabilities in the Composite Provider (i.e. association with InfoObject…) which will help here to hold on to the classic InfoObject and its master data.
One short comment on Product (0S4PRODUCT). If you are wondering how to deal with cross analytics including SAP SRM and others, we have decided to create a separate characteristic for this called Cross-application Product (0CA_PROD). You can add it to your Composite Providers which will enable you linking SAP S/4HANA product number to e.g. SRM product number and its attributes. Just select the relevant attributes of 0BBP_PROD as transitive attributes in characteristic 0CA_PROD.
As always, after importing the new support package in your SAP BW/4HANA system, you will have to have the newly available shadow versions of the source system dependent objects generated for your source system. Otherwise you will be missing out on the DataSource and Transformation into the InfoSource (I guess you wouldn’t be particularly happy to map about 300 fields coming from ACDOCA manually 😉 )
There are two ways to do so:
- SAP GUI: go to transaction RSA1 -> Source Systems. Right click on the particular source system (ODP_CDS) and choose option Activate.
- BW Modeling Tools: In your BW Project open the respective source system by double clicking it in the DataSource tree (ODP_CDS). Press the “Content Update” Icon (two yellow arrows).
Please check note 2433354 for further details.
Find the new as well as all existing SAP BW/4HANA Content data flows and more details in the updated presentation here
Thanks for the update. Considering the business functions level of S/4HANA, what's the percentage share of new CDS based content in the whole package?
Hi Erdem Pekcan,
please check the link provided in the last paragraph of the blog to the detailed content presentation (slides (8/9).
Thank you Simon.
hi Simon Kranig
can you share some more background which led to the decision to add the 0S4*-InfoObjects and not e.g. to provide just InfoSources and transformations to the classical central ones?
I would understand your blog, that the customers should use the 0S4-InfoObjects as soon as possible.
The initial effort for a customer when mapping the classical InfoObjects to 0S4-InfoObjects or vice versa in the HCPRs only might be low, but I see there some challenges in this approach. Therefore I would actually opt to exchange the old objects already in the Integrated-DWH-Layer plus HCPRs - but as far as I understand this needs to be done by the customers, correct?
Thanks and best regards
let me try to answer your question. Main reason behind this decision is the possibly different structures of the classical DataSources and the SAP S/4HANA CDS View based DataSources. The 0S4* InfoObjects reflect the structures as provided by the respective CDS view for extraction of this master data.
We have created this set for being able to focus on providing a consistent SAP S/4HANA based BW/4HANA data model based on the SAP S/4HANA point of view (exposed via CDS extraction views).
The HCPR InfoObject mapping feature was just one example. In the end this really depends on the customer specific situation.
Are we talking about a greenfield SAP S/4HANA system, someone moving from SAP ECC to SAP S/4HANA or a multi source system landscape consisting of SAP ECC AND SAP S/4HANA systems.