need some real time examples where we use hierarchy,taxonomy and qualifier

[Former Member]

Hi Guys,

I have some doubts regarding lookup table. where exactly we use hierarchy,taxonomy and qualifier tables in real time cases. can anybody make clear with some examples.

Regards

Ravikumar

[Former Member · Accepted solution]

Hi Ravi,

You can use Qualified table, when you have some scenario laike based on your one field, other field values will change.Like, With change in region, Price and storage temprature of medicines can change.

You can use hierarchy when you want to have your searches easier. Like if you have Vehicles, Two wheelers, four wheelers, Cars, Bikes etc. Then it is easier to search for the products if they are maintained in proper hierarchies. Vehicles -> Four wheelers -> Maruti ->Swift. User can easily reach to a record (Swift) and come to know details.

You can use taxonomy, when you have some attributes related to classes. Like Say you have, a class hierarchy for Cloths. Under clothes you will be having a child node each for T-shirts and Trousers. Now you want that if user selects T-shirt from the hierarchy, then its corresponding attributes (Size, Sleeves etc) should be displayed and if user selects Trouser then its corresponding attributes (Waist, Length etc) should be displayed. In that caseyou can use a taxonomy in which class hierarchy will consist of Cloths -> T-shirts, Trousers. and you will have attributes linked to their respective classes.

Hope this is clear to you.

Regards,

Dheeraj.

[Former Member]

Hi Ravi,

Qualified tables are used to show different variants in the relationships between main tables and subtables in a simple, highly efficient way. This makes sense because individual values in the qualified table depending on the relationship between the main table entry and the subtable entryu2014may be different for every main table entry. For example.

One Customer pays a price of 5 USD per item for quantities between 1 and 100 items. From 101 to 200 items, he pays only 3.50 USD.

Another customer pays 5.50 USD for 1 to 100 items and 4 USD from 101 to 200.

The product table stores all the product information, including these

quantity scales. But where should the pricing information be stored?

In MDM, it will be stored in a qualified table. The qualifier (here, the

price) is not just related to the record of the table in which it is stored, but also to the main table record to which it is connected.

This not only u201Csavesu201D a table, it keeps the product table manageable, because there continues to be only one record for every product, in which multiple prices can be stored for each customer.

Hierarchy tables display hierarchies in master data, such as product hierarchies, which are displayed in a tree menu. One example is an org chart, with branching between areas and departments.

Taxonomies are used to categorize or classify master data into coherent groups according to defined attributes, like product groups. For instance, a category u201Cbottlesu201D might automatically contain subcategories u201C1 liter bottles,u201D u201C1.5 liter bottles,u201D and so on, which can be used to form a uniform expression of the u201Cvolumeu201D attribute.

Regards

Richa

[Former Member]

Hello Saragadam,

Hierarchy table can be used to maintain hierarchy relationships.Say for example

a bank need to maintain their customer details but these customers may belong to

others customers .To maintain this relationship, we maintain hierarchy relationships.

Different customers can have different properties like some customer can have PAN

number and some customers might not have PAN number.To distinuigsh these

type of properties, we use attributes in MDM.Taxonomy is responsible to maintain

hierarchy relationships with attributes.

Qualifier table is special kind of lookup table.Any lookup table meant to eliminate

redudancy of data.The same way qualifier table acts.

Take one manufacturing company produces different products.These different

products contains different prices based on region and product.Here same

manufacturing company and same product has different prices based on regions.

To maintain this data makes redudancy.In order to eliminate redudancy we use

qualifier table.

In qulifier lookup table we have qualifier fields and non-qualifier fields.

The field values which are changed based on other fields called as qualifier fields.

In the above example, price values are changed baed on region and product.

So we make it price field as qualifier and region,product fields as nonqualifier in

qualifier lookup table.

Finally we link the maintable record to lookup records so that we don't have enter the

same data multiple times.

Thanks

Narendra