Conceptual question on Products and Customer Hierarchies

Question

I am wondering why it was first necessary to create Business Partner Hierarchies and Product Category Hierarchies in a different framework than Org Management.
I understand Org Management, but I donu2019t see the need to recreate, for example, your customeru2019s hierarchy in BP hierarchy builder if you can do all in Org Management.
The only current advantage I see is the fact that you can link conditions to Product Groups, and to different nodes in the BP hierarchy.
But why was this not originally done as an enhancement to Org Management?

Answer 1

By same I meant exactly the same. And that snippet-
providing Child extends Parent - won't compileI know the snippet won't compile.
Ah, I see. Child is less general than parent,
therefore the one on the left is NOT more general,
therefore it's incorrect. Makes sense.
Inheritance is so screwy. Polymorphism is much easier
to understand when a class implements an interface
than when it extends another class, in my opinion.
I wish there was a way to state the declaration in a
sentence type structure, as I find those easy to
understand.
Maybe in the case of
Parent p = new Child();one could say
something like, "a new specialization of Parent is
Child, p."How about "A parent, specifically a child, called p". (throws ClumsyClassnameException)
How about the old examples?
class Animal {}
class Dog extends Animal {}
Animal rover = new Dog();"I need an animal, called Rover. Specifically, I need a Dog"