Skip to Content

Documenting Developments and Data Model in SAP BW on HANA

Hello Community!

I've got some question regarding the documentation of SAP BW Developments and their managment in a whole.

First of all I'll give you some Background information:

This is my first SAP BW (on HANA) Project and I asked myself how to document developments in such a way, that it might be useful and save time in following Projects. This is a "vanilla" System, so there is no prior work done yet.
Unfortunately I've never seen a best practise of how to document Software before. I only read loads of posts (articles, ...) saying that nobody likes this Kind of work. As a fresher (straigth from University) I'm not that opinion. It has a high priority for me.

As there are no formal rules how to document at work, I would like to ask you for your help and your experience according to the following questions:

A) How much priority has the documentation in SAP BW for you?
How do you handle it (technique/System in General)? (What is your advice for me?)

-> I'm thinking about a custom Wiki where I want to document the model as well as some Business logic ( e.g. KPI) Maybe this idea will be discarded according to Administration effort.

I've already found a post (in the old SCN) where someone gave the advice to document inside the BW Model with a hugh document on reporting layer referencing to the related objects - that might be a bit distracting in a later Phase.

C) What would you (maybe) do "better" looking at the past?

Thanks in Advance! Your participation will help me a lot!

Kind Regards!

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

0 Answers