GeeKs Blogging @ dotCOM » Fundamentals

Siebel – Admin Mode Flag

Madhvi Arora — Sun, 02 May 2010 07:51:19 +0000

In my last project,we had a requirement of Admin Views, so the admin users if required can change the data from frontend and not going to backend and running update queries.

Admin Views are those views in which all the records are visible to the person who has access to this view irrespective of the position of the person.

Admin views can be created by setting “Admin Mode flag” on the view to “Y”.

Following affects take palce on setting the Admin Mode Flag:
1.Visibility rules are disabled.
2.The user properties in the BC are ignored.
This means that the user properties such as “Field Read Only Field”, “BC Read Only field” get disable for the view on which this flag is set to true.
3.If the view is in Admin mode, then the following restrictions for the business components used by the applets of the view are ignored: no insert, no merge, and no update. However, if these restrictions are set at the applet level rather than the business component level, or if a field has a Read Only value of TRUE, the Admin mode does not affect them.

Vanilla examles of Admin View are: Account Administration View and the Opportunity Administration view.

But due to disabling of these user properties, we faced some practical problems. I will discuss these in my next post. Stay tuned !

Related posts:

Siebel Admin Mode Flag – II – Issue Log In the last post I described about Admin Mode Flag....

Siebel Admin – Gateway Name Server – An overview We discussed about the basic Siebel Server Architecture in our...

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

Siebel – Fetch Active view properties – II We discussed about fetching the values from the active view...

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

CRUD

Nitin Jain — Wed, 28 Oct 2009 08:27:58 +0000

No, I am not referring to the Billiards game here. While browsing the Internet, I keep coming across a plethora of new technical terms everyday.

One such term I came across recently is ‘CRUD’. If you already know what it is, this post is not for you!!

For those who don’t, CRUD is a general terminology for Create, Read, Update and Delete.

These are some of the typical operations that one performs on a set of data in a Database or any other Persistent Storage.
Creation refers to creation of new records in the Database, typically the Database Insert Operation.
Read is the reading of the records from the Database. Typically the view operations.
Update would be the usual updation of some particular data in some existing records.
Delete would mean the data is no longer available in the Database. Better be careful here!!

Question: How is this relevant to Siebel or CRM which is the current theme on GeeksBlogging@dotCOM?

Answer: Lots!
We work with CRM systems all the time. Now, that means creation of huge chunks of data. If this is an indication, Siebel CRM system houses 4500 tables in its Database! Just imagine the kind of data that would be there in the system. I recall coming across the 50-100 GB Database sizes quite frequently.

With so much of data flowing around, all the operations on every record are equally important. A small goof-up could easily mess up thousands of records, just to start with, in a very small span of time.

[Update] I also came across an interesting differentiation from Graham. Let’s talk about VBCs and EBCs in Siebel. Following is the text from Graham himself:
“.. As long as the data is only being used to read then an EBC on a view will be a good solution, it has a “short” path to the database and so will give a good level of performance. However, updating or creating records through this route will not be supported by Oracle.

If a full CRUD solution is needed then you’ll be forced into the VBC route, as you then have the control (within script or any other technology you use to implement the background logic) in order to implemented your business rules and logic so that the database integrity is maintained.

This technical solution needs backed up by a careful functional analysis though. Why do the two BCs need combined? How will updates be handled? What are the relationships? Often exploring these sort of questions uncovers that a carefuyl structuring of the view and the applets within it are all that are really needed to solve the business requirement; remember that by creating an EBC or VBC to meet the requirement you are implying an ongoing maintenance cost for the life of the implementation, an operational cost that the business will not necessarily have considered when they wrote the requirement!
.. ”

Following alternative definitions for CRUD are available on Wikipedia:
ABCD: add, browse, change, delete
ACID: add, change, inquire, delete — though this can be confused with the transactional use of the acronym ACID.
BREAD: browse, read, edit, add, delete
VADE(R): view, add, delete, edit (and restore, for systems supporting transaction processing)
QDIM: query, delete, insert, modify
SAID: show, alter, insert, delete
VEDAS: view, edit, delete, add, search
SCUD: select, create, update, delete

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

Siebel – Looping multiple records – Query and Process In my last post, I discussed as to how we...

Siebel – Looping Multiple Records – III Looping through multiple records is a requirement we come across...

Siebel – Automating Merge Records by script – II I call this Part II, as I have already introduced...

Siebel – Merge Records Functionality How many times have we realized that there are multiple...

Siebel – Symbolic Strings

Nitin Jain — Wed, 12 Aug 2009 05:13:06 +0000

Consider this a brief introductory tutorial on Symbolic Strings in Siebel. Symbolic Strings are from amongst the most commonly used entities in Siebel, especially in Siebel Multi lingual deployments.

They can greatly reduce the job of initializing, deploying, tracking, modifying all the plethora of error/warning messages that you may generally come across in a typical Siebel CRM application.

The Symbolic Strings centralize all the English and non-english language messages at one place in Siebel, where you to manage. You always have the option of doing this independently at all the individual places in Applets, Business Components and the like, but, it is really not recommended.

Symbolic Strings are defined and managed from within Siebel Tools. This Siebel feature was introduced for the first time with Siebel 7.7 (there was a big bunch of innovations that came with this Siebel version for the first time), and has persisted since. So, it could be one serious consideration if you are looking to upgrade from an older Siebel version.

But be careful. Some of the data is not converted to Symbolic Strings automatically during upgrade. This includes, Seed Data, Error Messages, LOVs, lots of non translable attributes, etc. These continue to use the Local based string values.

Migrating to Symbolic Strings in case of upgrade, using the Siebel Conversion and Consolidation process, though could be useful in many ways, is a different topic in itself.

Some of the typical scenarios where Symbolic Strings may be applicable are:
1) Displaying the same string at a number of places in Applets
Assume you have multiple Applets based on the same BC (Sales, Manager, Admin, External) exposing some of the common fields. Why to declare them repeatedly each time (though Siebel still allows you to do that!)? You can just go in to create a Symbolic String. Refer this Symbolic String in the value. Use of the String Override function should be reduced as much as possible!

2) Displaying the same string differently in multiple languages in the application
Either define the different caption for different languages by using the locale option corresponding to the control, else, better still, go in for Symbolic Strings!

Some of the typical advantages of using Siebel Symbolic Strings in your application are:
1) Avoiding redundancy and duplicacy, of course!
2) A centralized place for declaring and updating these user messages.
3) In the process, reducing maintenance, and enhancing value.
4) Reduced development time cycle (the obvious buzzword, TAT!!), and costs.

Do note that some of the other kinds of strings, like LOVs, PDQs, etc. are not covered as a part of the Symbolic Strings functionality. These are defined and used differently in Siebel system.

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

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

Siebel – Upgrade Process – Part II This is a continuation from the post, Siebel – Upgrade...

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

Siebel – EAI Queue Okay, what are you thinking about? Is it Middlewares in...

Siebel – Vanilla Functionality

Nitin Jain — Tue, 11 Aug 2009 05:40:02 +0000

What is Siebel Vanilla functionality?

Somebody recently asked me this question. Though trivial, it could be quite foxing for somebody new to the Siebel Development community. It is a part of the normal Siebel jargon.

In plain and simple words, anything Out-of-the-box (OOB) functionality is called Siebel Vanilla. Let me explain.

Siebel is more like a Development Tool than a Development Platform (just face it, it’s the truth!). From amongst the basic strengths of Siebel CRM are:
1) Beautiful Interface, at the same time, easy to use.
2) Strong adherence to global Best Practices in the Functional Processes implemented.
3) Large amount of OOB functionalities, which generally suffice for most of the Business Processes in each vertical.

Let’s take, for example, a Telco. If we use Siebel eCommunications vertical for it, what do you guess will be the Business Entities for the run-of-the mill Business Processes. They could be:
Products
Building Price Lists
Building Catalogues
Campaigns
Opportunity Management
Order Management, etc.

All the above are handled by the Siebel OOB Processes. Thus, are part of Siebel Vanilla.

My guess would be that the term ‘vanilla’ takes its name from the ice-cream flavours, vanilla, strawberry, Manhattan Mania, Tutty-fruity and the like.

If you like it plain and simple, it’s vanilla. If you customize it, or add a flavour from your own business to it, it’s a different flavour, more like strawberry, Kesar Pista, Manhattan Mania or the Tutty-fruity. Most of the times, Siebel Consultants would like to roll out an application as close to vanilla as possible.

However, in practice, that is rarely the case!

Related posts:
Siebel – Merge Records Functionality How many times have we realized that there are multiple...

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

Siebel – Automating Merge Records by script – II I call this Part II, as I have already introduced...

Siebel – Enable Detailed Logging – Local Very often we come across scenarios wherein the process is...

Siebel Configuration – A day in life Consider this article as a simple overview of Siebel Configuration....

Siebel Configuration – A day in life

Nitin Jain — Fri, 07 Aug 2009 03:14:29 +0000

Consider this article as a simple overview of Siebel Configuration. We will cover how a typical day in the life of a Siebel Configurator is most likely to be like.

Siebel is a Tool in itself. It is a Customer Relationship Management system, which Oracle has kept as close to the global standards as it could, and it has done a good job at that, I must say. In most cases, it is similar to any customized CRM software you may come across, just that most of the views, and Data Organization that you would yearn for, would be available Out of the Box when you install Siebel CRM.

However, just like no two people in the world are the same, no two organizations in the world are the same. The Business Requirements vary with every Corporate Group in the world. Though Oracle’s Siebel CRM is as close to the global standards as possible, yet there is ample room where you feel it is either too heavy for your needs, or too light. I have come across both ends of the extreme in my career, and so can safely say that both of these exist.

Along with different requirements come the difference in approach, what the Orders screen should look like, and which all fields must be required when creating an Opportunity in the system, for example. It could also be as complex as changing the functional process in Siebel itself. For eg. Siebel supports the concept of both Leads and Opportunities, while many Business Practices in the world don’t have both of them together. When you begin to modify an existing Asset, Siebel by itself creates a Quote first. Many businesses prefer going to the Order in the cycle altogether.

Here comes Siebel Configuration. It refers to modifying Siebel Out of the Box, or the Vanilla features as they are popularly called, and to customize them as per the Business Requirement. Joins, Links, MVGs, Business Components, Workflows, Scripts, User Properties and many more are popular terms associated with the Siebel Domain. The modifications to the Siebel Applications are done more in Siebel Tools than in a Siebel Web Client.

Major Pain Areas:
1) Quite Common skill in Siebel Community.

Advantages of being a Siebel Configuration Expert:
1) The level of expertise you can gain is immense. There are too many things that Siebel provides OOB for which we may customize. Good Siebel Configurators really help improve Siebel Performance which actually define success of Siebel CRM Implementations.
2) All Siebel projects need this skill, and in quite a large numbers. So, you can rest assured, recession or no recession, you will never be out of job.
3) Exposes most of Siebel OOB functionality, such that you get accustomed to the global standards in any process, be it Order Management, or Campaign Handling.
4) Generally, no late working hours. At least not as much in modules like Server Admin, or Siebel EIM.
5) Siebel always pays well.
6) Extremely high team involvement. Everybody would be buddies with you.

This is the most popular Siebel domain, and skills are in need in any Siebel project. This could be a nice thing to settle down in the later years of your life.

Related posts:
Siebel EIM Career – A day in Life Consider this article as a simple overview of Siebel EIM....

Siebel – Why Upgrade? – Part II This is a continuation of the post, “Siebel – Why...

Siebel – Popup Update Only Hi all, I was working with Siebel Multi Valued Links...

Siebel – Vanilla Functionality What is Siebel Vanilla functionality? Somebody recently asked me this...

Siebel – An Introduction to different modules In the Customer Relationship Management (CRM) space, Siebel CRM is...

Siebel EIM Career – A day in Life

Nitin Jain — Tue, 04 Aug 2009 09:21:41 +0000

Consider this article as a simple overview of Siebel EIM. We will cover how a typical day in the life of a Siebel EIM Developer is like.

Usage of Siebel EIM is guaranteed as soon as a Siebel project is to be implemented, in most cases. The only exceptions that I can think of are the Siebel Upgrade projects in some cases, or in case the client never had any information organizing of Contacts and Leads for this line of business before (Rare, and highly unlikely!!).

EIM, or the Enterprise Integration Manager, is the primary Siebel Server Component which is used to transfer data from another system into Siebel CRM Database.

The baseline is, when a client decides to be prudent enough to set up a Siebel CRM System, he must already be using some mode or mechanism. Most generally, this is in the form of Excel sheets for Small and Medium sized businesses before they get organized. On a slightly advanced level, they may be using some of the other CRM system like Sage Systems’ ACT!, Sugar CRM, vTiger, maybe even SAP, SFDC or CRM OnDemand!!

In any case, the data which was organized differently in the original CRM System needs to be migrated to the new Siebel CRM System. There would be data about Accounts, Contacts, Leads, Opportunities, Products, their Prices and many more. Siebel Database is highly Normalised (though Denormalized examples are not uncommon) with nearly 4,500 different tables in Siebel Database. The data from legacy database needs to be migrated into Siebel Database, and the data must conform to the Siebel Data Model of Normalization, and also, the restrictions of User Keys, Required columns, etc. which may not have been the case originally.

This would need a pragmatic approach from the EIM Architect to extract data and intelligently map it into the Siebel Database, something with needs for high skills, and hard work.

The basic process in its simplest representation involves extracting data from legacy systems in a TXT or CSV file, importing it into the Siebel EIM_ tables (also referred to as Staging, performed using tools like SQL Loader), and finally running the Siebel EIM process to import the data into Siebel Base Tables (S_ tables). The entire gamut of Foreign Keys resolution, Duplicate Data, User Keys, Required Columns and the like come into the picture at this stage.

EIM, through its elaborate architecture allows us to Import, Update, or Delete data in a Siebel Database.

Major Pain Areas:
1) Long Working hours in initial Designing phase. This is a pain when you see colleagues from other modules laughing it off when the project has barely begun. Also, at the time of final migration in Production, it may involve sleepless nights as the Production environment may be brought down for a very limited time only.
2) High amount of documentation needed in the mapping initially. You can also expect multiple rounds of reviews and corrections.
3) Most of the work is related to creating CTL and IFB files in Text files. You may feel it getting monotonous at times.
4) Mostly related to Databases. So, it is more of a personal inclination and choice.

Advantages of being a Siebel EIM Expert:
1) Well paying. Simple concept of supply and Demand. Siebel EIM professionals are usually in high demand, and can expect excellent renumerations.
2) Excellent architectural skills. Any Siebel EIM expert will be extremely well versed with Siebel Data Model, and thus, the Siebel Architecture.
3) Excellent Database handling skills. Extensive use of DB. Make sure you like working with RDBMS, SQLs and the like before jumping into it.
4) Interesting work. This is more of a personal choice I would say. Even then, with the requirements varying from project to project, EIM Architects are generally at the top of their life. Not to mention the frequent client Interactions.
5) Excellent Networking Opportunity. You would need to involve almost everybody in the team such that the data migrated confirms to the requirements of all individual modules.
6) I have noticed very few changes in Siebel EIM process as such moving from 7.7, 7.8, 8.0 and finally to 8.1 as yet. Changes in Data Model must be very clearly understood though. For the ones looking for stability in life, and complaining about ever changing softwares in the market, this could just the thing!

All in all, a very challenging domain, very interesting, and highly paying to work in.

Related posts:
Siebel Configuration – A day in life Consider this article as a simple overview of Siebel Configuration....

Siebel – Adding License Keys to Sample I am glad to be associated with Geeks Blogging @...

Siebel 7.x – Party Model Changes After introduction of party model, the table structure (as far...

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

Siebel – Merge Records Functionality How many times have we realized that there are multiple...

Siebel – Merge Records – Checklist

Nitin Jain — Fri, 24 Jul 2009 05:42:10 +0000

I call this Part III, and concluding part of a series of my posts on the Merge Records functionality in Siebel CRM. You may want to take a look at the previous 2 parts below:
Siebel – Merge Records functionality
Siebel – Automating Merging Records by script – II

Though this looks like a very interesting and useful utility from the face of it, it can be dangerous too.

If you decide to go ahead with this functionality for 2 records, I doubt if there is a way you can recover both the records once again. This is the most dangerous aspect that I see with the automation concept we discussed in Part II of the Merge Records series of posts.

I also came across a few more issues with the Merge Records functionality. I am penning them down here.

Bookshelf says, when the two records are merged, only the top level, or at most top 2 level records are merged. This is particularly important concept if we consider the case of merging the Account records, for example. We could have contacts and their activities associated with these two Account Records. As per the Bookshelf, only the Account and Contact records should have merged. However, from the face of it, it seems, the Activities records also merge practically.

When we merge two records, Duplicate records are created on the MVG based fields. For eg. merging Person A record with Person B record, would create two records under the Language MVG even if both the original contacts had the same value for Language. The only suggested solution is to remove the duplicate records through scripts (Baad solution proposed, I must say!).

Single value fields are not updated after the Merge Records process. Merge Record process updates the child records by means of Links and Joins based on the Foreign Key fields. Siebel recommends the use of “Data Quality” Siebel OOB functionality. It is available under the head, Administration – Data Quality.

Position records are not merged when mergin Contact records. How could Siebel miss out on such important stuff.

And many more….

The more I explored about it, the more interested I got in the complete MergeRecord functionality. Try running a simple search on Metalink with the Search String, “Merge Records”. I am sure you would become interested, too.

Related posts:
Siebel – Merge Records Functionality How many times have we realized that there are multiple...

Siebel – Automating Merge Records by script – II I call this Part II, as I have already introduced...

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

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

Siebel – SIA BC Utility Service – Loop multiple records This is a vanilla business service which provides an extensive...

Siebel – Fetch Active view properties – III

Nitin Jain — Fri, 24 Jul 2009 02:59:53 +0000

I will discuss a practical example, and the corresponding Inputs as a usage example for the “FINS Data Transfer Utilities”. If you have not already done so, I would suggest going through the previous posts for a better understanding:
Siebel – Fetch Active view properties
Siebel – Fetch Active view properties – II

I will share a practical usage example for the above vanilla BS here.
Launch your Siebel Client. Navigate to the screen,
Administration – Business Services -> Scripts
Press ‘New’. I chose the name, “04 Nitin Test” for my Test BS.

Write a small piece of code in the method, “Service_PreInvokeMethod”, and the language as eScript.

Sample code is as follows:

function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{

var Input_ps = TheApplication().NewPropertySet();
var Output_ps = TheApplication().NewPropertySet();

var bs_FINS = TheApplication().GetService(“FINS Data Transfer Utilities”);
bs_FINS.InvokeMethod(“GetActiveViewProp”, Input_ps, Output_ps);

TheApplication().RaiseErrorText(Output_ps.GetProperty(“”) );

return (CancelOperation);
}

You can replace the with the desired parameter one by one, to see the corresponding output. As a sample, I got the following outputs in my Siebel setup:

Output Argument Value

BusinessObject Business Service

IsAdminMode N

Screen

ThreadApplet Business Service Test List Applet

View Business Service Test View

ViewModeCode 4

There are two strange observations in the table above.
1) The Output Argument, “Screen” returns NULL. Now, I am obviously within a screen, which has a name. Why is it NULL?

2) It has returned the ViewMode “4″.

A simple Lookup in Siebel Tools F1 help lists the following ViewModes of a view:
SalesRepView (0)
ManagerView (1)
PersonalView (2)
AllView (3)
OrganizationView (5)
GroupView (7)
CatalogView (8)
SubOrganizationView (9)

Notice carefully, 4 is not in the list!

Related posts:
Siebel – Fetch Active view properties Hi, Working on a typical requirement recently, I came across...

Siebel – Fetch Active view properties – II We discussed about fetching the values from the active view...

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

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

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

Siebel – Fetch Active view properties

Nitin Jain — Wed, 22 Jul 2009 08:10:39 +0000

Hi,

Working on a typical requirement recently, I came across a need to fetch the properties from the user’s active view. This was an attempt to recognize the user, and the details about the Siebel view/screen he was in.

On research we can see that there are a number of Application level methods which we have at our disposal.

We see that we can get the active Business Object name using the format:
TheApplication().ActiveBusObject();

Also, the active view name may be fetched using:
TheApplication().ActiveViewName();

The Login Id of the user logged in may be fetched using:
TheApplication().LoginId();

The Name of Logged in user (the one that is typed into the Login box) may be fetched using:
TheApplication().LoginName();

The Position ID may be fetched using:
TheApplication().PositionId();

The position name of the user logged in may be fetched using:
TheApplication().PositionName();

.. and maybe some more, in case I missed out on any.

However, this is very limited information (though may be sufficient for some requirements). More so, if we notice, the information is mostly User oriented rather than being Siebel session oriented.

We will explore further if there is a way to get more detailed information of the current view. Even simple topics turn into series of posts. There is so much to explore and share in Siebel..!!

Related posts:
Siebel – Fetch Active view properties – II We discussed about fetching the values from the active view...

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

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

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

Siebel – Popup Update Only Hi all, I was working with Siebel Multi Valued Links...

Siebel – Automating Merge Records by script – II

Nitin Jain — Wed, 22 Jul 2009 06:02:08 +0000

I call this Part II, as I have already introduced the Merge Records Siebel functionality, and discussed its usage in his post. One of the interesting discussions we had was how such a data could possibly be inserted into the Siebel system, since Siebel has so many mechanisms to prevent Data Corruption. We had also zeroed in on EIM and EAI as the basic culprits which could possibly insert inconsistent data into the Siebel Database.

When such a thing happens on sucha large scale, or when we know the exact pattern whereby we can detect these duplicate records in the system, we may look at options to automate the process of Merging Records. How nice would it be if we could just somehow put it all up in a workflow or script which would achieve the above objective.

Exploring further on the topic, I came to realize that there is an undocumented BC method which we may fire to achieve the objective above. Try looking at the script below:

var Target_Id = “Dummy-001″;
var Source_Id = “Dummy-002″;
var bo_Contact = TheApplication().GetBusObject(“Contact”);
var bc_Contact = bo_Contact.GetBusComp(“Contact”);

bc_Contact.InvokeMethod(“SetAdminMode”, “TRUE”);
bc_Contact.SetViewMode(All);
bc_Contact.ClearToQuery();
bc_Contact.SetSearchSpec(“Id”, Source_Id + ” OR ” + Target_Id );
bc_Contact.ExecuteQuery(ForwardBackward);

if (bc_Contact.FirstRecord())
{
while (bc_Contact.GetFieldValue(“Id”) != Target_Id)
{
bc_Contact.NextRecord()
}
bc_Contact.InvokeMethod(“MergeRecords”, Source_Id);
}

If you notice carefully, we have invoked the method, “MergeRecords” on the Contact BC. The Contact BC has the class, “CSSBCContactSIS” which definitely, thus, supports this method. My guess would be that this method would be supported for all the BCs, where the vanilla Edit -> Merge Records functionality is enabled for the corresponding views. I haven’t actually gone further than this.

If somebody has had any other experience with Merge Records, please do share!

Related posts:
Siebel – Merge Records – Checklist I call this Part III, and concluding part of a...

Siebel – Merge Records Functionality How many times have we realized that there are multiple...

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

Siebel – EAI Siebel Adapter – Looping Multiple Records This is a follow-up post on the post, Siebel –...

Siebel – Looping Multiple Records – III Looping through multiple records is a requirement we come across...

Siebel – Merge Records Functionality

Nitin Jain — Tue, 21 Jul 2009 13:40:21 +0000

How many times have we realized that there are multiple records exisiting in our database with nearly the same values? The next though with a bolt of lightning is, how the hell were two records with similar data entered into the system, with all the fundamentals of Primary Keys and User Keys.

Well, the answer could be that though none of the User Keys were violated, data was common in the other fields except the User Key fields. For example, we may end up having two Contact records in our system, which we realize actually point to the same CONTACT. So much so for blasphemously expensive CRM Systems!

Before you actually pounce onto the Sales Rep, hey, the contact himself could have given two different mobile numbers to two different Sales Reps, couldn’t he? And, we can’t obviously forget the scenarios where loads and loads of low quality data is imported via our famous EIM / EAI processes into our poor Siebel system, which then has to bear the brunt of everything. Continuous Business scenario changes themselves mandating some of the changes in our Data Organization is another issue.

In any case, the problem is evident. Let’s try to work at solutions.
Siebel provides an OOB vanilla functionality called “Merge Records…” to handle such scenarios. Following is the process you can use:
1) Select the two records in the appropriate Siebel view, for eg. You may use CTRL to select 2 records.

Remember here that the record you select 2nd will become the target record. This will be the record that remains after the Merge Process. The record selected first will vanish. This may look up the corresponding record Row Ids to verify it on your own.

2) From the Application menu, choose, Edit -> Merge Records.

Do note that the Merge Records functionality is not available for all the views. The menu item Merge Records will be greyed out for the views where the functionality is not supported.

3) Click OK in the confirmation applet that appears.

The Merge process will now be performed, and the record selected first in the process will vanish. Also, you will notice that the data from the original record now appears in the left-over record. In other words, the data from first record has been MERGED into the second record! Also, the associated entities such as corresponding Opportunities, Activities, etc. will also be merged into the new record. This is the part which is most interesting.

I understand if some of you feel this is something very trivial. Personally, I found it very interesting. Will post a couple of more posts on this topic soon.

Related posts:
Siebel – Merge Records – Checklist I call this Part III, and concluding part of a...

Siebel – Automating Merge Records by script – II I call this Part II, as I have already introduced...

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

Siebel – Vanilla Functionality What is Siebel Vanilla functionality? Somebody recently asked me this...

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

Siebel – An Introduction to different modules

Nitin Jain — Fri, 10 Jul 2009 02:42:23 +0000

In the Customer Relationship Management (CRM) space, Siebel CRM is the undisputed Market Leader, at least that is the impression I have! And not only just so. Dig a little deep into Siebel CRM and you would realize how wide and vast Siebel CRM is, in terms of both the number of functionalities it covers, and the amount of detail in each one of these functionalities that it covers. I am more and more convinced that it is not just one software, but, and entire CRM suite stack built for the purpose.

It is not like Siebel is the only CRM software in the market today, just that it is the one most popular. Originally conceived, and spearheaded by Tom Siebel, the revolutionary (if I may call him), it has now been bought out by ORACLE, the behemoth who owns such a big part of our infrastructure today (no offences intended!).

Some of the others that come to my mind straight away are:

Oracle CRM (from ORACLE Corp’s own stable)
SAP CRM
ACT! by SAGE Systems
.. are all On Premise solutions ..

Salesforce.COM
Oracle CRM OnDemand
Sugar Express
.. are all On Demand / Hosted solutions ..

Sugar CRM Professional / Enterprise
Compiere
vTiger
.. fall in the Open Source Solutions space ..

I doubt if Sugar has a competition in the Open Source solutions space, which has caught the fancy of so many CTOs off late.

Despite so many options and heated competition in the space, Siebel has maintained its position and the space.
Some of the most popularly used areas are the ones that we can broadly outline in line with Siebel CRM. These are the areas that the Contractors and other Siebel CRM Professionals would generally popularize themselves as. These are:
Siebel Configuration Expert
Siebel Server Administration Expert
Siebel Enterprise Applications Integration (EAI) Expert
Siebel Enterprise Integration Manager (EIM) Expert
Siebel Reports Expert

Over and above, we have some specialized areas and corresponding Expert Professionals with experience in them, who complement and/or form a part of above areas. These are really specialized modules, which makes finding true talent quite difficult at times of sourcing. These are something like
Siebel eConfigurator Expert
Siebel ePricer Expert
Siebel Advisor Expert
Siebel Web Services expert
Siebel UCM Expert
Siebel ICM Expert, etc.

CRM being a concept in itself, be prepared to meet lots of functional experts in the area as well. From my point of view, I see expertise in this area as the most neglected part at the time of sourcing, however, personally I believe this is the most important part. A sound fundamental is important to the long term success and viability of any process. A sound Architecture must come before a flawless Implementation for the ultimate success of a Project. Functional Expertise is most popular in the Business Analysis areas of
Siebel Order Management
Siebel Sales
Siebel eCommunications (Telecom)
Siebel ePharma
Siebel Public Sector, and many more..

I can understand if it is beginning to get complicated and jumbled up for the first timers. Seasoned professionals would be comfortable with the hidden meanings of the terms, “etc” and “many more” above. As I always say, it’s not about right or wrong, it is my perspectives, and I am free to write about them!

Related posts:
Siebel Server Architecture – an Introduction You may call this an introductory tutorial. Siebel as we...

Siebel Configuration – A day in life Consider this article as a simple overview of Siebel Configuration....

Siebel EIM Career – A day in Life Consider this article as a simple overview of Siebel EIM....

A meeting with Siebel EAI Hi, Here I am, with my promise of introducing the...

Siebel – EAI Series on GeeksBlogging@dotCOM Siebel EAI, aka Enterprise Application Integration is generally the most...

Output Argument	Value
BusinessObject	Business Service
IsAdminMode	N
Screen
ThreadApplet	Business Service Test List Applet
View	Business Service Test View
ViewModeCode	4