GeeKs Blogging @ dotCOM » Himanshu Bajpai

Login Failed in Dedicated Web Client : MVF Issue

Himanshu Bajpai — Tue, 30 Aug 2011 21:18:49 +0000

Recently I have met with the Problem in form of defect. The Problem was related to Record Visibility in Activity.

There were activities created for SR as a result of Email Response and properly visible in Activity List Applet under SR. We have Pick Applet in SR Applet for fetching all Email related activities. But strangely same activities were not visible in the Pick Applet.

On investigation, we found that the Applet was based on a different BC i.e. Action Special.
Seeing Different BC It is understood there is a problem of Record Visibility.
And since BC Record visibility is controlled by BusComp View Mode, there were bound to be some issues.
We compared Action and Action Special BCs BusComp View Mode.

Following was the screenshot of BC -Action Special (click to enlarge)

Siebel BC Action-special screenshot

Following was the screenshot of BC-Action (click to enlarge)

Siebel BC-Action screenshot

Above Snapshot shows the difference clearly !!

As a Solution –
1) We made Action Special similar to Action BC and added Visibilty MVF as Organization and Visibility MVL as Organization.
2) Compiled SRF.
3) Login in dedicated Client.
Shock!!!!!!!!!!!!!!
It was throwing error of Wrong User Id and Password while few minutes back it was working fine.
Login again- Shock again-error again.

3rd Time Login (3 is my lucky number ), but error again but this time my luck was better. So error changed to something different and is indicated below (click to enlarge) -

Siebel Error - BC MVF Configuration issue

Since Organization MVL was not present in Action Special, I was not able login into the dedicated client.
Actually I did the View Mode Change by Compare Object utility on Action and Action Special BC. This smartness and laziness created the whole issue because compare object put the MVL and MVF even though MVL/MVF was not present in BC.

If you change the Visibility MVL/MVF Manually then you would not allowed by Siebel to pick MVL/MVF that is not present in BC.

But it is really good for me. Since I have learnt a lesson and that is generic.

Conclusion-If the Reference of MVL or MVF is not present in BC then you would not able to login Siebel Dedicated Client and you can expect to get the below error.
—————————
User ID or password that you entered is incorrect.
Please check the spelling and try again.
—————————

Thanks for reading. Stay tuned for more articles !!

Related posts:

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

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

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

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

BI – Actuate Reports in PDF format in Siebel Hi all, Siebel is well integrated with Actuate Reports, used...

Siebel EIM – Nomenclature of Custom Column

Himanshu Bajpai — Sun, 07 Jun 2009 10:40:45 +0000

Previous post regarding new custom columns mapping in EIM table seems very useful for Siebel developers. Especially, the ones that are planning a new move to this territory of Siebel. Brijesh has written it beautifully which you can read from the link below:
SIEBEL EIM – CUSTOM COLUMN MAPPING

I have also applied the same tips given in SIEBEL EIM – CUSTOM COLUMN MAPPING. In one of our implementations, we have number of custom columns in S_ORDER table and have the requirement to update two of the existing custom fields X_TEST_DUMMY_COLS_VALUE and X_TEST_VAL.

I have used EIM Table Mapping wizard and applied the changes on EIM_ORDER table for validating upon the two custom column I have found two new EIM column respectively named-
ORDTESTDUMMYCOLSVA and
ORD_X_TEST_VAL.

It is quite strange for me because why Siebel has also used discrimination like human being!

Then we have analyzed the Siebel mechanism and it is given below – Siebel will allow only 18 characters for EIM column Name. If it exceeds the length then first Siebel erase the “_” from right. If still it is not fit within 18 character then it will be truncated from right. It prefixes EIM columns as ORD or AST to the EIM_ORDER, EIM_ASSET. So guys now if u designs a custom column then make its length short to recognize respective EIM column easily with some standard name.

Related posts:
Siebel EIM – Custom column mapping It’s a very basic concept explaining how we can generate...

Siebel EIM – Custom table mapping This article is similar to my previous article (Siebel EIM...

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

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

Siebel – Case Insensitivity (CIAI) Wizard CIAI stands for Case Insensitive and Accent Insensitive in Siebel....

Siebel – ActivateField() split wide open

Himanshu Bajpai — Fri, 01 May 2009 04:16:56 +0000

In Siebel, we generally tend to use the fields on the BC level in a number of ways, one of them being their use in Siebel scripts. The most common functions for operating on BC fields are GetFieldValue() and SetFieldValue() used for getting a value, or setting a value of the corresponding field in the BC. However, Siebel requires using ActivateField() before operating on any field of the BC.

Fields that are not active at runtime should not be used in script. Runtime errors, flawed logic and lost data may be the result of such a practice.

Following are the fields that are active by default.
• System fields (Id, Created, Created By, Updated, Updated By)
• Fields with their Link Spec property (on the business component object) set to TRUE
• Fields with their Force Active property (on the business component object) set to TRUE
• Fields included in the definition of an applet on the active view, even if the field’s Show In List property (for List Applets in Siebel 7.x) or its Visible property (for Form Applets in Siebel 7.x) is set to FALSE (on the applet object).

Note that a list column must be bound to a web template to actually be included in the SQL. Simply defining the column in the applet’s definition will not make a field active as of 7.5.2.200.
• Fields activated with BusComp.ActivateField(“”) are active for the lifetime of the BusComp object variable or until deactivated explicitly by the DeactivateFields method.
• Fields that are used as part of a calculated field calculation when the calculated field is retrieved for use on the active applet.

If any of the above circumstances is not true then the field will not be retrieved in the SQL statement for the business component. This means that no value is available to GetFieldValue and subsequent updates with WriteRecord will not have a database column to update since it was not included in the original SQL statement.

Both cases have a severe impact. Whether
• The ActivateField() method is used incorrectly, or
• The ActivateField() method causes the specified field to be included in the SQL statement for the subsequent ExecuteQuery() method call. A call to ActivateField() is relevant only if followed by a call to the ExecuteQuery() method.

Retrieving and updating fields using BC.GetFieldValue() or BC.SetFieldValue() methods before a query has been executed will not work as expected. If the script calls GetFieldValue before a field has been properly activated and retrieved, GetFieldValue will return a runtime error will occur for the use of GetFieldValue or SetFieldValue where a field has not been activated.

While working with the Siebel Data Server from an external VB/Java application, for example, the Siebel Data Server is not aware of any applet definitions and, therefore, will not include the fields defined on an applet. Script must use the ActivateField method to retrieve the desired fields in a query in this case. This is also true when interacting with the Siebel Database using the Siebel Business Objects Interface Type Library.

Let’s wait for more on ActivateField().

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

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 – InvokeServiceMethod() on Calculated Fields InvokeServiceMethod() is used to invoke Business Services and take values...

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

Siebel Assets List view – Performance issue / Cannot display records

Himanshu Bajpai — Tue, 14 Apr 2009 08:00:57 +0000

Assets Screen Load is a major problem in Siebel, and a major pain area for the concerned developer. I am sure many of you would have come across it in one implementation or the other.

If there are more than 10,000 records in Assets screen, vanilla Siebel Application will not load the screen.

Application will hang for some time and after that it will show an error message similar to the following -

“There were more rows returned than can be shown on the screen. Please ask the System Administrator for support.”

In a typical CRM software, Order Management cycle, we start from an opportunity, and proceed to Quote, Order and finally a billable Asset in that Order. Then Asset to Opportunity, and the cycle repeats itself.

Assets are end results and in all probability, Assets are in million of numbers.

The problem being discussed is that the user has to see All Assets or some cases At least All Asset headers.

Approach 1-

If User can restrict his search, we can go in for a PDQ that return lesser number of records (<10000). This will ensure at least the first load is quick. However, on Blank Query it will again return the same error described above.

Approach 2 (Preferred Approach) -

So, if the developer needs a permanent solution to this problem, he can follow the steps below to show millions of assets without any error-

Login Siebel Tools>

Query for Asset Mgmt – Asset List Applet Applet.

Go To Applet User prop>search for “Disable Buscomp Hierarchy”.If it is set to “FALSE”, make it “TRUE”. After compilation Assets screen will show millions of records without any error. Voila! Problem solved.

This property would be even more helpful for performance if used to show Asset Headers Only.

Please put in your comments. Feel free to add your solution, in case you have come across a different one.

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

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

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

Login Failed in Dedicated Web Client : MVF Issue Recently I have met with the Problem in form of...

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