Yesterday a reader of Siebel Unleashed asked an interesting question stating a requirement. I thought it would be interesting to share that requirement with all of you and know your thoughts on it.
Question:
I want to display records from 2 Siebel tables in a single applet. Is it a good idea to create a VBC and fetch records from both Siebel tables and display it in the UI? If yes, how can I achieve that? At least high level steps.
Answer:
Surprise……
I was about the post the answer (basically my thoughts not a solution) to the question but then I thought to do it a little differently. I wanted to hear your thoughts about this requirement first and then see if it matches the answer I was thinking.
I am pretty sure there are lots of smart people out there with lots of experience who can guide what is best possible way to do it. I will share my answer on Thursday.
So you have 2 days to post your thoughts and answers to this question.
Stay tuned
————————————————————–
Three people contributed and provided an answer. I must say that they covered all the options that I had in mind. Jimit came really close to what I had in mind. Here is what I was I was thinking.
The first question that came to my mind was:
Are these tables related?
If yes, then as Jimit correctly pointed, use join. If they are not related in anyway, then we are open for options of using EBC or VBC. As Graham has correctly pointed, that this technical solution needs backed up by a careful functional analysis.
Let’s weigh both options:
EBC: It is easy to implement and maintain in Siebel but we have to create a view at database level that performs union of tables as suggested by Viktor. So, you have maintenance problems if there is some change in table schema and also it will be readonly.
VBC: We assume that both the tables are in same schema as other Siebel tables so it is easy to create Business components on that table. So, VBC option is easy to maintain as through scripting we can instantiate both business components and do display them in whatever we want to or we can follow sINDhuja’s approach create IO based on those Business Components but it requires more effort to implement as compared to EBC.
This is where functional analysis comes into picture which will help us to decide us on approach we need to take.
I would like to thank Viktor, Jimit, Graham and Sindhuja for there contribution


(4 votes, average: 4.00 out of 5)