Rearranging the Product Hierarchy nodes

[former_member203111]

Dear Experts,

I have been posting this issue on various blogs including SAP community Network but not able to get any solid solution and hoping to have any answer this time, here is my issue.

We have Two location s(US and Canada) and both locations are using same product hiererachy for their reporting need but now Canada has different requirement as far as hierarchy structure and its nodes are concerned and the way the reports are being presented to them.

Our hierarchy is built on 0material, please note that 0material contains attribute values that are associated with the material number and these values are loaded from ECC.

Our Sales and CRM reporting BEx queries do not use standard SAP hierarchy to display a material's product hierarchy, INSTEAD the Sales and CRM reporting BEx queries use a flattened material product hierarchy that is stored as attribute in the master table 0material.

Some of the attributes (for example. 0PRODH1) are loaded from the Material master table in ECC.  Some of the attributes are loaded from the table ZMAT_CLAS which is loaded from the Material Classification table in ECC.  The Material Table in ECC is tied to the Material Classification table in ECC by material number, and both are maintained by MasterFiles.

The product hierarchy is stored at the material level for reorg purposes.  For example, if a sub-category moves to a different category, the material master table in BW is updated (daily) for every material containing that sub-category.

As far as solution for Canada specific hierarchy, I am thinking to make a copy of existing hierarchy  into BW which is built on 0material and rearrange the nodes in copied hierarchy for Canada specific and then create a Hierarchy variable on the front end for Canadian users.

Can anyone please let me know the following:

1. What impact will it create on existing US hierarchy (if any).

2. What kind of maintainance and support is involved in the BW system once I copy the existing hierarchy for Canada.

3. Do I need to write any ABAP code such as Functional Module to automate the daily loading, if Yes, where do I write this code as I am not      ABAPer but need to get his help. (any Abap syntax or code help will be appreciated).

4. Is it possible to achieve this without writing ABAP code.

5. I want to create a technical design to present it to my team, what are the pros and cons of this apprach, please advise.

I will really apprecaite your reply, Thanks.

Regards

[former_member203111 · Accepted solution]

I have managed to come up with the solution for this problem which is to build a Flattened Hierarchy on attribute and use those navigational attributes in the reporting.

standard hierarchy will not give an option to suppress the higher level nodes therefore I will copy the existing hierarhy and realign the nodes according to my requirement.

There is some enhamcement required on the backend which means enahncing the extracator and adding the required fields and then remap those new fields with the newly created attributes on the 0material, run the load again and then use those attribute in the reporting.

Make sure to change the attribute to navigational attribute.

Hope it will give direction to someone who might have same kind of issue.

Closing this thread now.

Regards

[RamanKorrapati · Accepted solution]

Thanks  Imran for sharing the solution.

[former_member203111]

Admin: plz delete this post / discussion, I have an answer in another post in my activity, Thanks

[RamanKorrapati]

No issues, if you found answer, please provide here and close thread by choosing your own reply as correct answer. For future reference it would be helpful.