GeeKs Blogging @ dotCOM » Prachi Sharma

Metalink3 to My Oracle Support – Change Log

Prachi Sharma — Mon, 17 Aug 2009 02:36:56 +0000

There are a number of significant changes, or enhancements coming as a part of upgrade from Metalink3 to My Oracle Support. Metalink3 has been the lifeline for official Oracle support up till now for users of Siebel CRM, Peoplesoft, JD Edwards and Hyperion.

Some of the Major changes promised by Oracle as a part of this change are:
1) The new My Oracle Support Interface requires a Flash Player
Oracle says the new UI will need Adobe Flash Player version 9.0.115 or later. If you don’t have a flash player installed on your computer, better do it now from the Adobe Flash Player download site.

Our guess is that it could mean that the new interface runs even slower. Users are already complaining about Oracle Metalink3 speed vis-a-vis Siebel Supportweb. We understand that Oracle may be trying to put forth a more modern picture by going in for a more elaborate UI, but, is that really what you asked for?

2) Home Page replaced by Dashboard Page
Dashboards will display high level information of certain type, like Service Requests or Knowledge Articles. Users will be able to drill down to get more detailed information.
Customization of the Dashboard will be possible. This means the users will be able to drag and drop the information they feel is most relevant to them.

3) Login URL is set for a change
https://metalink3.oracle.com will be redirected to https://support.oracle.com. I like this. I hate getting the third grade treatment by the name ‘metalink3′ being a Siebel CRM user. Thanks, Oracle.

4) Multi Language Support
The new Oracle Support UI will be available in 4 languages based on the initial Browser selection – English, Japanese, Korean and Chinese. I am surprised. What about the more popular languages like French, German, Spanish and Portugese?

In any case, I guess English is going to be by far the most popular, going simply by the percentage of English users using the site.

5) Booksmarks replaced by Favourites
Oracle says, the Bookmarks as we know in Metalink3 will now be migrated to Favourites in My Oracle Support. Favourites, they say, allows users to flag additional items such as Bugs, Systems, Targets and Projects.

It is only a hands-on on the new system which will throw up the true pictures, the strengths and the weaknesses though.

Related posts:

Metalink3 to My Oracle Support – Train yourself Metalink3 is the Oracle support portal. It is used by...

My Oracle Support Non Flash Version We all need Professional support one time or the other,...

Siebel – Symbolic Strings – Change default ‘X_’ This is a smaill tip I was working on, which...

Changes to the Oracle Homepage? Just browsing through the Internet, particularly the Oracle Homepage, http://www.oracle.com,...

Oracle Fusion Middleware 11g released Hi, We had shared the most happening news of the...

Metalink3 to My Oracle Support – Train yourself

Prachi Sharma — Sat, 15 Aug 2009 12:23:59 +0000

Metalink3 is the Oracle support portal. It is used by licensed users of Siebel, Peoplesoft, JD Edwards and Hyperion for official Oracle support activities.

Yeah, I can hear somebody swooning out there trying to remember the good old days of Siebel Supportweb! Lightning fast query results, very relevant and we remember when we could find solutions to problems on almost everything. Metalink, though has also caught up, I guess everybody is fond of old memories.

In any case, Metalink as we know, is to retire soon. Metalink3 is being replaced by ‘y Oracle Support’ortal by Oracle. In order to help the users get better accustomed to it, there are some online courses being run, so that we the users don’t complain as much as we did in the Supportweb to Metalink transition. Well, Oracle always claimed that the not-so-good user experience was always because of insufficient training of the users on the new system, and not a flaw of the Oracle Metalink at all. Well, we will leave that part of the debate open for our readers here.

The upgradation as Oracle says, is planned for the weekend of August 28-30, 2009. Customer Training on the same is scheduled to start on Monday, August 17, 2009, and is expected to continue up till September 04, 2009. It is a live web based training which is scheduled to run twice daily. There will be a follow-up open question and answer session immediately after each presentation.

To register, Oracle has provided the link, Oracle Metalink3 Training. Let’s go through the training give Oracle a chance and see if the My Oracle Support is really better than Metalink3.

As always, waiting for your invaluable comments!!

[Update] Chris Warticki from Oracle is providing support on this. Chris is twittering @cwarticki. He has also started a twibe to help us guys out. Thanks, Chris!

Related posts:
Metalink3 to My Oracle Support – Change Log There are a number of significant changes, or enhancements coming...

My Oracle Support Non Flash Version We all need Professional support one time or the other,...

Oracle Siebel Certification needs hands on training – II Most of Oracle Certifications need a mandatory hands on training....

Oracle finalizes new Training Partner Hello, We reported last week that Oracle has decided to...

Oracle Fusion Middleware 11g released Hi, We had shared the most happening news of the...

Siebel – Popup Update Only

Prachi Sharma — Thu, 25 Jun 2009 03:28:04 +0000

Hi all,

I was working with Siebel Multi Valued Links (MVLs) for some of the configuration requirements in our project. Siebel Configuration is a vast world in itself. I always feel I am learning something new everyday!

We generally use MVLs to fetch data through typical “Links” that we configure in Siebel BCs. We once across an interesting requirement which I am sharing with all of you.

Requirement: To suppress the opening of the MVG Pop up Applet for a particular Multi Valued Field (MVF).

This could be a requirement in a typical scenario where Siebel OOB offers a Multi Valued relationship, but, we have a requirement where it can possibly have a maximum of one record in the relationship. For eg. Requirements say we can have a maximum of one Address per Account, though Siebel OOB solution offers multiple Addresses per Account. There is no need for the user to be opening the MVG Applet and selecting values from it in this case.

While working to try and find solutions to this problem, we noticed that corresponding to the MVL, there is a property by the name of “Popup Update Only”.

To reach this, navigate to,
Siebel Tools Object Explorer -> Business Component -> Multi Value Link

Query for the Link that you would want to modify. Navigate towards the right in the Records window to locate the Property, “Popup Update Only”. Set this to FALSE. This would be set to TRUE in case we need to pop up the MVG Pop Up window to enter values.

Setting this to FALSE, MVG (Multi Value Group) field values can be edited directly from the Parent Applet.

Do let us know in case this helps you some day.

Related posts:
Siebel – Looping multiple records – Update records Hi, We often come across a requirement where we need...

Siebel 8 Certification Update All of us want to be certified Siebel experts, don’t...

Siebel – Make MVG Field required Siebel supports the concept of Multi Valued Fields, or the...

Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – Make a field Required, conditionally There was a requirement in our project to make Account...

Siebel – Make MVG Field required

Prachi Sharma — Mon, 22 Jun 2009 05:02:08 +0000

Siebel supports the concept of Multi Valued Fields, or the MVF. These generally relate to fields such as Addresses, or Contacts which may possibly be more than one for a particular Account record. You would generally notice an Inter table which would further store the details.

One of the major problems that pops up is to make these fields Required. This does not work if set at Field level or using the Required User Property for these Multi Value fields.
This can really frustrate the developer.

We can implement this by using the script below. I have tried to set this on a field called, “Dummy Field” for demo:

function BusComp_PreWriteRecord ()
{
var DummyField = this.ActivateField(“Dummy Field”);
DummyField = this.GetFieldValue(“Dummy Field”);

if ((DummyField == “”)||(DummyField == null))
TheApplication().RaiseErrorText(“DummyField is a required field.”);

return (ContinueOperation);
}

Replace Dummy Field name above with your field name, and it should work beautifully.

Related posts:
Siebel – Make MVG Field required – II Hi friends, This is a follow-up post of the post...

Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – Make a field Required, conditionally There was a requirement in our project to make Account...

Query on the Long Column or Field A typical problem in any EAI project. Others too!! One...

Siebel – ActivateField() split wide open In Siebel, we generally tend to use the fields on...

Siebel – Different MiniButton types

Prachi Sharma — Sat, 20 Jun 2009 08:05:31 +0000

You must have come across the so many different types of minibuttons that you can place on your applets. Have you ever gotten confused as to which minibutton to choose for which particular applet?

It’s so nice to be back! Hello to everybody.

I was working on a configuration requirement recently when I needed to add a minibutton on an applet. I noticed that I had many different minibuttons available, and it seemed that all of them perform the same task. I consulted my senior who asked me to just use MinibuttonEdit kind of button. I digged a little deep into it, and, I am sharing here my findings with everybody.

You would find the following different types of minibutton options in Siebel:
MiniButton
MiniButtonEdit
MiniButtonEditNew
MiniButtonNew
MiniButtonQuery

Believe me all of them have different uses. Actually, their visibility on applets is controlled by the selection we make. You can refer the table below for easy understanding:

New Edit Query

MiniButton Y Y Y

MiniButtonEdit N Y N

MiniButtonEditNew Y Y N

MiniButtonNew Y N N

MiniButtonQuery N Y Y

The above selections will ensure that the selected button appears only in the Applet Mode that we want.

Related posts:
Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

Siebel – Admin Mode Flag In my last project,we had a requirement of Admin Views,...

Siebel – changing Textbox height

Prachi Sharma — Mon, 18 May 2009 04:58:16 +0000

There are a number of HTML controls available in Siebel. One such control is the Textbox, or the Textarea. This is generally displayed as a big box on the screen having a height spanning multiple rows.

There was a requirement from my client to modify the number of rows being displayes on the Textbox. He wanted this textarea on the Applet to be 6 rows tall, such that most of the text is directly visible to the Customer Support guy using this view. I will discuss the solution that we implemented to this problem here.

Navigate to the Applet in Siebel Tools, where you need to show this textbox of height equal to 6 rows.
In the Object Explorer, select Controls.
Navigate to the Control which has the Textbox / Textarea.
In the corresponding columns, you will find a property called, “HTML Height”. Set this value as 100.
Compile into the Siebel SRF, and restart Siebel Web Client. You should now see the Textbox with a large height as desired.

Siebel seems to take this value in terms of pixels on the screen. 100 seemed to be reasonable in our case.

Similarly, if you want to change the width of the Textbox, there is another property corresponding to the Textarea control called, “HTML Width”. You can change the width of this textarea to as much as your requirements.

We tried doing this on the Form Applet and it worked.

Related posts:
Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

Siebel – Remove About SRF Window In my previous post, I had discussed as to how...

Siebel – DefaultFocus – User Property

Prachi Sharma — Sun, 17 May 2009 04:59:26 +0000

In Siebel Application, whenever you navigate to a screen, the default focus of the cursor is set to the first editable field. You may have a requirement to instead set the default focus to a more commonly used field. So, whenever you navigate to that screen, the curson focus will be on the client required field first up, and the user will have to navigate to reach some other field in the applet.

This can be done easily by using a Siebel vanilla Applet level User Property called, DefaultFocus.

In order to use this, simply navigate to the ‘Applets’ object manager in Siebel Tools. Navigate to ‘Applet User Prop’ under the ‘Applets’ Object Manager.

Do a NewRecord and set the following values:
Name : DefaultFocus
Value :

Here, is the name of the column where you want to set the Default focus.

Compile your changes into the Siebel SRF and run. You will now see that the default focus whenever you navigate to the screen, has been set on the required column in the Applet.

This will run for both Form and List Applets. But, somehow this does not run in High Interactivity mode! This works in Standard Interactivity mode only. I hope this article helps somebody someday.

Related posts:
Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Automatic User Logout Logging out a user automatically, when the user does not...

Siebel – Forcing User Logoff Hi all, Somebody recently asked me if there is a...

Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – millisecond dates on Applet

Prachi Sharma — Sat, 16 May 2009 05:00:34 +0000

I had discussed in my previous posts about invoking a BS in a calculated field for complex calculated calculations, and, about finding out dates accurate to milliseconds. You can read about them from the links below:

Invoking a BS in a calculated field
finding out dates accurate to milliseconds

Today, I will discuss as to how we can show dates on Applets with upto millisecond accuracy. This could be of immense importance in EAI projects as one example, wherein we need to calculate the time spent on each step. Performance debugging could be really enhanced by using this method.

I will extend the concepts introduced previously. We will take the Problem statement to be, “Showing the ‘Created’ time of the Applet, accurate to the closest millisecond”.

For this we would need to create a new custom column of type string in the corresponding table and the Business Component. Whenever a new record is entered in this table, we will populate this new column as well. I will call it “Created_ms”.

I extended the script which I had used in my previous examples like this -

function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{

if (MethodName == “md_getMS_Created”)
{
var d_test01 = new Date();
var d_test03 = d_test01.getMilliseconds();
var d_test02 = d_test01.toString() + ” : ” + d_test03 ;

Outputs.SetProperty ( “out_get_ms_created”, d_test02 );

return (CancelOperation);
}

return (CancelOperation);
}

I have used the methodname, “md_getMS_Created” in this case.
Instead of outputting the value, we can use this script within some other code where we are creating new records. Now, when we expose this column on an Applet, the user will be able to see the time accurate to milliseconds.

I hope this helps somebody some day.

Related posts:
Siebel – getMilliseconds() usage Siebel by default displays all dates in the system accurate...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – InvokeServiceMethod() on Calculated Fields InvokeServiceMethod() is used to invoke Business Services and take values...

Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...

Siebel – getMilliseconds() usage

Prachi Sharma — Fri, 15 May 2009 04:50:33 +0000

Siebel by default displays all dates in the system accurate to the seconds place. However, at times, especially in EAI based projects or performance intensive projects, it is often a requirement to calculate accuracy down to the last millisecond.

Siebel provides a ready made function called getMilliseconds() for this functionality.

I wrote a simple script in Siebel Local Client to demostrate this functionality. The contents of the script, “Dummy Get_MS Test” is:

function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{

if (MethodName == “md_getMS”)
{
var d_test01 = new Date();
TheApplication().RaiseErrorText( d_test01.getMilliseconds() );

return (CancelOperation);
}
return (CancelOperation);
}

This returned me the value 895 in my tests. To be precise, I received the following output:
—————————
Siebel
—————————
895(SBL-EXL-00151)
—————————
OK
—————————

This cannot be hours, minutes or seconds. It has to be milliseconds.

Hence proven!

Related posts:
Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...

Siebel – InvokeServiceMethod() on Calculated Fields InvokeServiceMethod() is used to invoke Business Services and take values...

Siebel – Fetch Active view properties – III I will discuss a practical example, and the corresponding Inputs...

Siebel – EAI Queue – Usage I had introduced the concept of Siebel EAI Queues in...

Siebel – Symbolic Strings – Usage Symbolic Strings appear directly in Siebel Tools’ Object Explorer, an...

Siebel – InvokeServiceMethod() on Calculated Fields

Prachi Sharma — Sun, 10 May 2009 02:45:56 +0000

InvokeServiceMethod() is used to invoke Business Services and take values from it in case of Calculated Fields.

I actually wanted to post on something else, but, I guess this has to be a precursor to it.

All of us know of Calculated Fields in Siebel Business Components. I am sure they must have solved some very big problems for you at times, as they have for me. However, not all of us know that we can actually invoke Business Service scripts from within the Calculated Fields, rather than just calling some in built functions or playing around with the other fields in the BC. This functionality enhances the already huge functionality of the Calculated Fields in Siebel.

For demonstration, I will first create a new Dummy Business Service, and then invoke it from BC.

Create a new Business Service in Siebel Tools by the name, “Dummy InvokeServiceMethod Test BS”.
Define a method in this BS, “md_SumVals()”. Following is a sample code snippet:

function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{
if(MethodName == “md_SumVals”)
{
var num1 = Inputs.GetProperty(“Num1″);
var num2 = Inputs.GetProperty(“Num2″);
var Out_Sum = num1 + “,” + num2;
Outputs.SetProperty(“Out_Sum”, Out_Sum);
return(CancelOperation);
}

return (CancelOperation);
}

Client side BS also works in this case.
This BS is now ready to return the Sum of the two input values in the Output Property, “Out_Sum”.

Now, add a new field, “SumVals” in the BC where this value needs to be exposed. Tick mark the “Calculated” property to TRUE for this field. In the column for Calculated Value, enter the expression:

InvokeServiceMethod(“Dummy InvokeServiceMethod Test BS”,”md_SumVals”,”num1=3, num2=4″, “Out_Sum”)

The general syntax for invoking this method is:
InvokeServiceMethod (“[ServiceName]“, “[MethodName]“, “[InputProp1=val1, InputProp2=val2]“, “[OutputProp]“)

This will now return the sum of the two input numbers. This example can be expanded in a variety of ways for complex Siebel operations.

I would like to emphasize for one and all to minimize scripting since Scripts are not recommended as part of Siebel Best practices. It is very rare that you would run out of all the other options and have to use InvokeServiceMethod on a Calculated Field. The requirement has to be really really complex in this case, I guess!

Related posts:
Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...

Siebel – ActivateField() split wide open In Siebel, we generally tend to use the fields on...

Siebel – Make MVG Field required Siebel supports the concept of Multi Valued Fields, or the...

Siebel – Make MVG Field required – II Hi friends, This is a follow-up post of the post...

Siebel – getMilliseconds() usage Siebel by default displays all dates in the system accurate...

Siebel – Number of rows displayed in List Applet

Prachi Sharma — Fri, 08 May 2009 18:16:53 +0000

Siebel Web Client by default shows only the first 7 rows. I guess all of us would have observed that. Today, I will share a Siebel tip as to how we can control increasing or descreasing this default number.

There are two kinds of settings in Siebel to control this:
1) Control the number of default rows being shown. And,
2) The maximum number of rows being shown in one go on the screen. This is when we press the Show More button on the Applet.

Controlling the default number of rows
There is a parameter called “NumberOfListRows” in the “SWE” section of the .cfg file. If you change this value, to say 10, you would see 10 rows by default in the List Applets by default. This is when this setting is not being overridden by some other property in Siebel.

If you want to set the default value of the number of rows to be displayed in only one Applet, you can set the property, “HTML Number of Rows” for that particular applet. This appears as a column in Siebel Tools along with the name of the Applet. Press multiple number of times to reach this particular property in Siebel Tools.

The value will default to 10 in case this property is not set at the indivisual Applet and the CFG file level.

Controlling the Maximum Number of Rows
In the SWE section of the CFG file, you can set the parameter, “NumberOfMaxListRows”. This will control the number of rows to be displayed on the List Applet once the Show More button is pressed and the applet expands.

This value defaults to 20 if not set in the CFG.

These tips are true for 7.x versions of Siebel. I remember one of my friends telling me that there is another option in Siebel 8.0. If somebody knows about that, please add to this post.

Related posts:
Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel Assets List view – Performance issue / Cannot display records Assets Screen Load is a major problem in Siebel, and...

Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...

Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...

Siebel – Custom Applet Title

Prachi Sharma — Wed, 06 May 2009 02:53:18 +0000

There is an Applet title on the top of the Applets. This is normally something simple and static. For eg. Serial Number, Line Items, etc. I will discuss how we can make it dynamic. We will make it dynamic so that it displays something based on the record that is currently selected in the Applet.

I came across this recently when I was trying to practice with the solution suggested by Madhvi in her post on Showing red asterisk on conditionally required fields on this blog.

The Applet title is generally static and constant for an applet. In this article I will show a simple requirement and solution where we change the Title of the Applet on the basis of Account of the record selected. I will take the example of the “Order Entry – Order Form Applet (Sales)” which is the first applet on the Sales Orders screen.

1) Navigate to Siebel Web Client with Order Management functionality available.

2) Navigate to the Sales Order screen using Page Tabs on top or the Sitemap. You should be able to verify the first applet name by going to Help -> About View…

3) Login into corresponding Siebel Tools. Query on the Applets for the applet, “Order Entry – Order Form Applet (Sales)”.

4) Goto the “Controls” section corresponding to the Applet Object Manager. Here, you should see a control by the name of “AppletTitle”.

5) In this record, change the value in the column “Field” to “Account”.

6) Compile and Go. The Applet should now display the name of the Account in the selected record.

This is a dynamic approach because the Title in the Applet will now change from, “Sales Order” to the Account name of the selected record. This will work.

Trying to make it look a little good, we can create a calculated field as below, and use it in the Applet Title above.
‘Sales Order : ‘ + [Account]

This will make it look a little better by showing both the Applet Name and the Account Name. This can be done for any field not just the Account field.

Thanks Madhvi. While trying out your solution, I learnt something new as well.

Related posts:
Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...

Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Oracle’s recession strategy

Prachi Sharma — Tue, 05 May 2009 10:25:19 +0000

Recession is in, and it is now official. US had accepted early this year that recession had creeped in six months ago, something all of us already knew. After the pricing changes introduced by some of the Software bigwigs including Microsoft, it seems Oracle is now ready to play the game.

As per the latest reports, Oracle has complely waived off its Extended support pricing through 2010 and 2011. This has been done for some of the major Oracle product lines including Siebel CRM. This was announce by the Oracle President Charles Phillips at the recent COLLABORATE conference.

You can read the complete news article on yahoo news here.

Seems like the Oracle kind of strategy to tide over the recession.

Related posts:
Changes to the Oracle Homepage? Just browsing through the Internet, particularly the Oracle Homepage, http://www.oracle.com,...

Inside Oracle Fusion Apps : CRM perspective Okay, now this is bigg news. We all know about...

Oracle Buys Virtual Iron Oracle Corp. (R) is at it again! The latest news...

Oracle Fusion Applications price list Is Oracle Fusion Apps now generally available ? Well, with...

Oracle Fusion Middleware 11g released Hi, We had shared the most happening news of the...

Siebel – Unable to check out objects

Prachi Sharma — Sat, 25 Apr 2009 15:34:29 +0000

I will discuss the following most prominent ways to enable or disable object level check-outs in Siebel here:
1) EnableObjectCOCI parameter
2) Allow Object Locking

I will explain these terms here.

Siebel brings about lot of new features in every new release. One of the very useful improvements in Siebel 7.8 was “object level check-out” in Siebel Tools. For those who started working directly on Siebel 7.8 and above, uptill Siebel 7.7.x, Siebel had the concept of Projects. A project in Siebel was a logical grouping of various objects – Workflows, Business Services, BCs, Applets, etc. We had custom projects for EAI, Configuration, Pricing, B2B, etc. And, we could only check out or check in projects! This was really time consuming.

I remember waiting for days in some cases, for someone to check in the project, because I wanted to work on some other object that she was not working on, but was in the same Siebel project. With object level locking, an individual can work on individual objects (an Applet, BC, or Business Service, etc.), and some other member can simulaneously check-out some other object whether or not in the same project. This greatly increases productivity, speed, and quality.

However, I had a lot of friends coming upto me, that even though they had Siebel 7.8 or above installed, at times their object level check-out was not enabled for some objects. Either it was not enabled at all, or for some particular objects.

There are two parameters in Siebel which control the Object level check out in Siebel

1) EnableObjectCOCI parameter
This parameter is present in the ‘[Siebel]‘ section (generally present on top) of the tools.cfg file. Your tools.cfg file would be located in the folder, “/Tools/BIN/ENU”.
This parameter must be set to TRUE to enable the object level check out.

1) Allow Object Locking
This is a new column in Siebel Tools against Projects in Siebel Tools. For most projects, this flag is ticked TRUE by default. But, I have noticed that for Upgrade related projects, it is set to FALSE. In case you created custom project in Siebel Tools, this flag must be set to TRUE.

Though this has helped increase speed, it has still not solved the problem. I still have to wait for long period sometimes for my friends to check-in the commonly used objects like ‘Quote Item’ BC and the like. I am wondering about one thing now. What is the real use of having projects now? If I can check out objects, why do we still have projects? I can’t think of any place where we cannot do with objects, and projects are still required. After all, projects are only a logical grouping of some objects. Right?

Though checking out objects is trivial at times, and taken for granted, I have also had a few of my friends discussing about checking out Workflows in Siebel. I have also heard people claim that is one thing still not possible without checking out the entire project. I will try to cover this problem in future posts.

Related posts:
Siebel Tools hangs when checking out objects Hi, Now this is strange. I had been running into...

Siebel – Unable to launch Local Client Hi all, I was making a fresh install of Siebel...

Siebel – Unable to login to mobile client After long time I am writing a blog… This time...

Siebel – Symbolic Strings – Usage Symbolic Strings appear directly in Siebel Tools’ Object Explorer, an...

Siebel – Run Case Insensitive queries This is a nice tip I ran across. All the...

Siebel – Adding License Keys to Sample

Prachi Sharma — Mon, 20 Apr 2009 02:46:30 +0000

I am glad to be associated with Geeks Blogging @ dotCOM. This is my first post here.

This is a very generic problem that we all come across. Adding License Keys in Siebel Sample Database. This is at times a little difficult and workarounds have to be used.

There are a number of ways that you can enter License Keys in Siebel:
1) When you are installing Siebel, and try to log in for the first time, it asks for valid License Keys. You can enter multiple license keys at this step.
2) Log into Siebel Web Application. Navigate to Sitemap -> Administration – Application -> License Keys.
3) Log into Siebel Tools. Navigate to Help -> Technical Support -> License Keys

However, you will notice that only the first option works in case of Sample Database. The route through Siebel Client and Siebel tools are greyed out. The first option has the drawbacks in case, the license keys entered are not lifelong, and we may need to enter new license keys after some time. Also, we may need to add additional functionality in Siebel using new license keys.

The solution is to login into Siebel Tools. Once logged in, press ‘Shift’. Keep it presses while navigating to Help -> Technical Support. Now, if you notice the ‘License Keys’ button is active. Press License Keys, a new dialogue box will open. Here, you can add new, delete or edit existing license keys. This will solve the problem.

Related posts:
Siebel – License keys don’t work / are invalid So, here I am again. After the fabulous solution to...

Siebel – Autosave Opportunity data – Sample Code This is a follow up post on my previous post,...

Siebel – Scrolling between records – UP and DOWN Generally in Siebel Client, we very often have the need...

Siebel – Unable to launch Local Client Hi all, I was making a fresh install of Siebel...

Siebel – Remove About SRF Window In my previous post, I had discussed as to how...

	New	Edit	Query
MiniButton	Y	Y	Y
MiniButtonEdit	N	Y	N
MiniButtonEditNew	Y	Y	N
MiniButtonNew	Y	N	N
MiniButtonQuery	N	Y	Y