I'm working on IDT for creating business layers based on SAP BW Multi-providers. The issue I'm facing right now is that whenever I modify the underlying Multi-provider, my business layer is not getting refreshed automatically with the changes.
Please let me know if I need to do any settings in IDT for the business layer to get refreshed automatically or do I need to create a fresh design right from creating the connections.
If we add or delete any info-objects in BW cube/multiprovider , the BO connection( .cnx) , created with Relational connection mode, is not getting refreshed with the changes automatically until we delete and create fresh one.
Is there any way to refresh the connection automatically with modified changes in BW ?
Can we create an auto-join in data foundation after adding a particular table ?
Yes You Can !!! There are 2 ways of getting this done !!!
#1. If you do know what table the change was made, highlight the table, and then click on the "Bulb" icon on top of the Data Foundation window and click on the "Refresh Structure". This should check for the particular table and refresh its str. This is the option I would recommend the most as you are dealing with the only table where you are expecting the change.
#2. There is also an option where you can refresh the Str of the entire Data Foundation(DF). With DF open, click on "Actions->Refresh Structure"..Now the whole schema within the DF will be refreshed. However, the good thing is, it shows you all the changes in a dialog window on tables changes, columns changed, etc !!!
Hope this helps...
Could anybody please let me know where can I find 'Refresh Business Layer' Wizard in IDT. Please let me know if I need to apply any patch to reflect the wizard in IDT. BTW we are working on Vanilla version of BO4.0 ( i,e BO 4.0 SP2).
Is there any alternative way of refreshing the Business Layer or will business layer refreshes automatically once data foundation layer is refreshed?
Hi Pavan ,
Henry is correct !.. for the time being till you apply patch , you can do the following steps: :
1. 'Refresh structure' of the Data foundation (.dfx) with quick fixed connection
2. Right click the on generated business layer from .dfx and click on "Insert candiate objects".
3. Select the appropriate changed objects to get converted in BO objects in respective classes in Busness layer (.blr) automatically.
Hope, it would help you
Another quick question with something similar to above. I am building the UNX universe on top of Multi Provider and I noticed that normal select statements on Dimensions would return "ZERO" records unless a measure is included in the query. Is there a workaround for this? I do not mind using a dummy null measure for simple queries. However, this is becoming cumber some when doing cascading prompts. IDT has a simple way of doing it but me without being able to generate LOVs without a dummy measure, its becoming difficult to implement cascading LOVs.
Now the 2nd question is, I am developing all in DEV. When I use LCM and promote it to my QA, I can go ahead and create a new connection pointing to my QA Backend. However, when I try to change the connection from Dev to QA in the IDT Datafoundation "Connections" tab, it allows me to change the connection. However, the objects in the Business Layer does not reflect the new Calalog Name of the QA connection and none of them would parse. For example, Lets say my Dev connection is named D31Conn and my QA connection is named Q31Conn. Their catalog names by defaulyt are D31Conn and Q31Conn. Now, after developing my universe in BOBJ Dev and promoting it to QA, I am creating a new connection in BOBJ QA called Q31 Conn. When I open the promoted universe and try to change the connection from D31conn to Q31conn, it does it successfully. However, in my business layer, all objects would not parse and woul fail because their SQL still points to the old Catalog D31Conn instead of Q31Conn. Am I missing something here? Any help is much appreciated !
Edited by: Ramki Krishnamoorthy on Mar 6, 2012 2:46 AM
Just a Quick Update, I forgot to mention that my deployment is BI4.0 SP2 Patch 12