siebel

Hey Guys, One thing we all think about is how to design a simple solution to a complicated requirement and so today lets see how to create a Narrative report for a 1:M relation. As you may know Narrative Report can be used only on one record. But, using a combination of reports, we can do the a LOT more! All we need to do is create 2 reports linked to each other and add them to a Dashboard. let me show you how. Step 1: Create a Opportunity Parent Report Using Opportunities Subject Area (Reporting  or Real-Time) Add the fields you would like to use on the Opportunity Information Section of the Quote report. In Step 2: Create Layout , Add a Narrative View and use the this code Opportunity Parent Narrative View Code . Make sure you use the @"Number" symbol in the right places, or the values would display against the wrong columns. You'll notice that the values are not correct in this preview, don't worry. since this report is not being filtered from the Prompt yet, the

Hey Everybody, Hope you all are doing Great! It's been a long time since my last post, apologies for that! Anyway, I have decided to make up for that time and give you some great stuff! Recently, I had a LOT of people asking for a way to Automatically generate EIM Mappings. I have written a post previously called Generate EIM mapping using SQL Script . However I made some new changes that will give you more information than before. So here are the updated versions for Oracle and MS SQL Output Preview Document Links : Do what the document tells you are you're good! Automate Siebel EIM Mapping using SQL_MSSQL Automate Siebel EIM Mapping using SQL_Oracle Watch out for more interesting Stuff! Cheers! Ryan

Sometimes Simplicity just does not precede complexity, but follows it. Recently while configuring Thread Bar for some views, we faced a trivial issue. Value of the Thread Field defined was not coming in the Thread bar.  We have specified the correct Thread Applet, Thread Field and Thread Title properties for the related views but only Thread Title was being displayed when we drilldown from List view to Form View. Google resulted this issue being faced by other users without fix. Things got luckier for me when i found a similar article on support web which stated that this is the intended behavior of siebel when the underlying Business Objects of traversing views are same. However as workaround of this issue there are three options: Have different BO's for List View and Destination View. Remove thread bar and make use of IE back option. If it is business critical to have navigation path in thread bar then one can define Source Field and Destination Field in the drilldown from list V