Hi Marvin,
It might be that the mapping of DataSource fields to InfoObjects in the Transformation is not OK. I advice to check all rules and share screenshots if you are in doubt.
In my opinion the hierarchy framework is quite rigid although greatly enhanced in BW 7.3. You can use 7.0 data staging technology with Transformations and DTPs. In the Transformation there are some new hierarchy rule types and on top of that, you can even write routines. However, in some cases the Business Content (BCT) Characteristics are hard-coded by SAP.
Most of the mapping is done automatically. If you have a look at your PSA data, then you will normally see what you have to do and whether or not to write a tiny routine (e.g. to map to another InfoObject).
There are basically 2 cases to determine the Hierarchy Characteristics:
- FIELDNAME is available in hierarchy structure (e.g. G/L account number);
- Only IOBJNM is available in hierarchy structure (e.g. Material Hierarchy).
In the first case, you can use the transformation rule type Derive Hierarchy Characteristic. In the second case, you can use the transformation rule type Hierarchy Split for NODENAME and a simple ABAP coding for the InfoObject. You have to program any replacement of BCT InfoObjects (e.g. 0MATERIAL by RMATERIAL). You can check the PSA data of segment Hierarchy Nodes to determine all BCT InfoObjects to be replaced.
More information can be found in the following blog The new SAP NetWeaver BW 7.30 hierarchy framework. Also you can refer to SAP Help:
- SAP Help - Creating a transformation for a hierarchy;
- SAP Help - Examples of a hierarchy transformation.
Best regards,
Sander