With lots the data information, it is possible to filter on logical dependences in the information values. I’ll show you that by an example.
Transcription of video
So this case, I have City Bike. It’s a seven gear male bike, aluminum, et cetera. If I insert my specification on this bike, I can see all the different specification that makes up the long description. And if I look down in my bike type City Bike, I can see two different selections, even though I know I have more in there. And for my gear, I can see I have four different selections.
And these are logical dependents. So this means if I delete my gear on this bike, I want to rename it, yes. And I look down in my bike type now, I can see I have more logical choices, meaning that the choices before were depending on my seven gear bike.
So if I select the mountain bike, for instance, on this one, like this. And I select my gear afterwards, I just need to rename it, and when I select my gear now, I can only select between two other gears. So it’s possible to set up those logical dependencies.
This also applies to the search functionality. So if I go back into my item window, and I view my search functionality in here, and I’ve selected a template called Male, meaning I can set up here the information I want to use for searching. And again, if I drill down into my bike type, I can select everything in here.
And I select one of them. Now when I select my gear, I can see I have only four whereas, before I knew I had six different selections. I’ll just select my seven gear here, which means if I go back on my bike and select that, I can see I have only two choices now.
So it runs both ways, those selections. So you don’t have to select in a specific order, now I delete my bike again and I can see I have all my gears in here.
So the logical dependences is a way of limiting the selection on values, information values, depending on other selection. And this applies to all of master data functionality, both on items, customers, vendors, lot numbers, et cetera.