Tree Data Structure in Article Master Data
Not planned
It would be great, if there is a possibility to build a tree structure in Article Master Data like the folders in the Windows Explorer.
Companies with many articles could visualize it. For Example, if they have spare parts for cars and they search for all spare parts which are connected to a Porsche 3L Camshaft, then they could Select: Porsche, Engine, 3L, Cylinder Head and they will find all the needed Articles.
-
Official comment
Hello,
You can create Universal Fuctions type SQL, in those queries you can add data from other tables or UDF's. You can also add variables and in the query set them as optional.
Here is a video of a Feature Focus Session of this Universal Funciton.
Also, we will have a Webinar if a few weeks (date pending) where we will explain how to create this kind of searches to make easier to find Master Data.
-
Thank you for your request. The development team have now added it to our internal planning-system for evaluation. -
@Rasmus, It would be wonderful if this can be done by giving us access to the queries used, so we (in the field) can deploy our own queries against whatever manufacturing system is being used. For example Boyum writes the queries for SAP's BOM, and for Beas. We in the field could use those as example to write queries against other systems (i.e. BatchMaster, etc.) The B1UP tree logic would indicate required and optional fields that must be returned by the query.
-
Hi Yaremi,
thank you for your answer. This is a very good feature, which helps me to solve lots of problems, but I think it won’t solve the problem with the article master data.
It’s because the “Tree” is changing almost every minute. Example:
If you are a car mechanic or a plumber, you get articles databases from your suppliers. Sometimes more than one million different article numbers and you add more than one hundred articles and 10 folders per day.
So there are hundred folders, some of them with hundred subfolders in almost 10 layers. VW names the subfolders as “front-wheel-drive” and “rear-wheel-drive”. Porsche names it als “FWD” and “RWD”, Toyota as “FR” and “BK”.
If these Words are in a parent folder called “VW Type of drive” or “Toyota type of drive” you will find the right subfolder. With SQL it would be a little complicated, because most of the users can’t change a SQL statement.
Because of this problem most (of German) ERP Systems have got a Article Explorer Tree.
If you like, I can send you a video, but I can’t do this on a public site.
-
We need some more information here. Out of the box Item Master Data does not have any sort of hierarchy unless we are talking Bill of Materials.
@Michael: Are you talking about something to visualize BOM structures or are you talking about a tool to define the structure?
@Dave: I not really following your comment. What query are you talking about we expose (we currently have no Queries at all) and how is this related to the request?
-
@Rasmus, My thought is that your team would create the tree view object as part of B1UP, and then open it up so that we can write the query that feeds the tree view. Ideally the tree view object wouldn't know where the data it is using comes from, only that it received data that matches it's requirements.
This allows us to make this tree view object work with the BOM / Formula structure from any manufacturing system. I think the SQL Report is very close to this concept.
-
Hi Yaremi,
thank you for this great tip.
Now I have watched the complete video. I have integrated the SQL widget in the dashboard and combined it with the auto filter and Drag n Drop grouping.
That’s the ultimate article search machine.
-
@Dave: Thanks for the explanation. It is not something that is currently planned but we will keep it around should many ask for it.
-
This feature request has been evaluated and based on our current roadmap/number of votes we are sorry to say that this request is not planned for the product.
Please sign in to leave a comment.
Comments
9 comments