GeeKs Blogging @ dotCOM » Business Component

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 – SIS OM PMT Service

Madhvi Arora — Sat, 20 Mar 2010 07:26:37 +0000

There are lots of vanilla business services available in Siebel which can be used to configure any process and this helps in avoiding scripting.

One of these services I came across is “SIS OM PMT Service”.

People who have worked on Order Mangement module must be aware of this service.

This service is extensively used in Order Management Process. Both its methods as well as its user properties are utilized in Order Creation Process.

But this service can be used in other modules as well.

It has various methods which can be used are:

Get Profile Attribute

Invoke BC Method

Refresh Business Component

Set Profile Attribute

In this post, I will discuss method “Refresh Business Component” of this service.

As clear from its name, it is used to refresh the Business Component.

In most of scenarios if we update some field or insert new record, UI is not refreshed with that data. We explicitly need to fire blank query either in our script or on UI to refresh UI. Instead of doing this we can use this Method to do so.

The required input arguments to this service are:

Business Object Name—> The name of the BO in which this data needs to be refreshed

Business Component Name—>The name of the BC where refresh is required.

This can be used in both script as well as workflow.

I will discuss the example of workflow:

WF_01

This is a sample workflow which is used to update account status.

The detail description is as follows:

Query For Record: Siebel Operation Step with operation Query is used. Here row_id has been passed in Object Id.

Record Found: Decision Box is used to check the record which needs to be updated exists in system or not .Here check is made with the help of Process Property “Siebel Operation Object Id”. If record is present, then Siebel Operation Object Id will not be null.

Update Account Status : Siebel Operation Step with operation Update is used. Here row_id has been passed in Object Id.

Refresh Record: This step uses BS “SIS OM PMT Service” with method “Refresh Business Component”.

Since here I am updating Account Status in Account Screen, the values of input arguments are:

Input Argument Type Value

Business Object Name Literal Account

Business Component Name Literal Account

Try this it will work.

Please share your valuable comments.

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

Siebel – SIA BC Utility Service – Invoke BC Method I had discussed about the vanilla Business Service, “SIA BC...

Siebel – FINS Industry XML Query Service “Extracting values from a tag deep down in the Hierarchy.”...

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 – Run Case Insensitive queries

Nitin Jain — Mon, 17 Aug 2009 09:41:15 +0000

This is a nice tip I ran across. All the Siebel Developers use Siebel Tools and Siebel Web Client extensively. And, each one of us run over a hundred queries daily. However, when querying for some data, for eg. a Business Service Name in Tools, Siebel generally demands we enter the correct case. To streamline the process and improve productivity, I continuously keep making minor modifications in my environment settings.

Method 1:
Open your corresponding CFG file in Edit mode (for Tools or for the Client). Navigate to the corresponding section for the Datasource, Sample, Local, Server or some other custom section. Search for the following parameter and update the value from FALSE to TRUE.

CaseInsensitive = TRUE

This parameter is available in both the Siebel Tools and the Siebel Client CFGs, both on the Local and on the Server.

Method 2:
This method will work on the Server.

In the Siebel Web Client, login with Server Admin priviledges. Navigate to the following path:
Sitemap -> Administration – Server Configuration -> Profile Configuration (tab)

Query for the ‘Profile’ with the name, “Server Datasource”.
From the bottom-most applet, search for the parameter with Alias, “DSCaseInsensitiveFlg”. The parameter would have the ‘Name’, “Database Case Insensitive Flag”. Set the value to TRUE.

And you are ready to go.

Warning:
There is a field level setting that makes the query on that particular field Case Sensitive or Insensitive. It appears as a property with the name “Use Default Sensitivity” corresponding to every Business Component field.

Siebel Help says it would work with only the Id fields, and only those Id fields which are exposed corresponding to the Business Fields. We cannot set this for eg. for the field, ‘Id’, corresponding to ROW_ID in the Database Column. However, in practice, this property seems to work for all the Varchar type fields.

Ensure the flag in this field is ticked, such that this value is always, TRUE.

Be fast, be more productive, Outperform!!

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

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

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

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 – Left, Right and from the Middle

Nitin Jain — Wed, 12 Aug 2009 09:04:28 +0000

Extracting a sub string from a lengthy string in Siebel. What is the best solution you can think up for this typical problem? I know, I know, you and you colleagues have done this thousands of times before. But, have you ever successfully done it without using a single line of scripting?!!

Now, it becomes interesting!

Not that I am saying, it’s entirely possible only by configuration. At the very least I don’t know how it’s possible that way.

Let’s assume a test string:
var strng = “abcdefghijklmnopqrstuvwxyz1234567890″;

Requirement : Take the first 5 characters from the above string in another substring
Solution 1:
var sub_strng = strng.substr( 0,5 );

Output:
abcde

Solution 2 : Using Left() function.
Take it in a Calculated field. Use the expression,
Left( strng, 5 )

Output:
abcde
I have noticed that at times, this does not work within eScript. Should work with VB and in Calculated Expressions.

Requirement : Take the last 5 characters from the above string in another substring
Solution 1:
var sub_strng = strng.substr( (strng.length – 5),5 );

Output:
67890

Solution 2 : Using Right() function.
Take it in a Calculated field. Use the expression,
Right( strng,5 )

Output:
67890
I have noticed that at times, this does not work within eScript. Should work with VB and in Calculated Expressions.

Requirement : Take the middle 5 characters from the above string in another substring (assume ‘cdefg’)
Solution 1:
var sub_strng = strng.substr( 2,5 );

Output:
cdefg

Solution 2 : Using Mid() function.
Take it in a Calculated field. Use the expression,
Mid( strng,2,5 )

Output:
cdefg
I have noticed that at times, this does not work within eScript. Should work with VB and in Calculated Expressions.

Using Calculated Expressions where these are very commonly required, does save scripting at times.

Trust me, this really works!!

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

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

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

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

Siebel – EAI Siebel Adapter Search Spec Hi, I can bet that for anybody who has worked...

Siebel 7.x – Party Model Changes

brijesh — Wed, 20 May 2009 20:40:24 +0000

After introduction of party model, the table structure (as far as EIM is concerned) have changed tremendously. The largest data model change involves the Party model, which I think is basis of post siebel 7 releases. Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all party entities and are the logical extension table of S_PARTY and they all have the corresponding entry in S_PARTY base table and the data is brought into the business components through an implicit join (PLEASE NOTE THEY ARE NOT EXPLICIT JOINS).

Some of the major data model changes are also related to this new model. Employees and Contacts have been combined into the same table (S_CONTACT) and similarly, internal and external Organizations have been combined into one table (S_ORG_EXT), in pre 7 releases of siebel employees and internal organizations are stored in S_EMPLOYEE and S_ORG_INT respectively means there tables have gotten obsolete.

The S_PARTY table is the primary table and is the single entity to store all party types – organization units (both external and internal), positions, access groups, user lists, households, contacts, and employees.

So in nutshell following are the new tables or we can say modified functionality tables in siebel:
• S_USER (For siebel Users)
• S_CONTACT (contacts, employees)
• S_ORG_EXT organizations (internal, external)
• S_POSTN (positions)
• S_ORG_GROUP (Households)
• S_PARTY_GROUP (Access Groups: To implement data security one of the major changes)
• S_USERLIST (user lists)
• S_BU (Internal Organizations)

Non-person party entities will have directly or indirectly ralation with employees and contacts.

Data Migration Changes:

All relation based tables have changed in post 7 releases the following tables have gotten obsolete:

Old Table (pre 7 release) New Table (post 7 release)

S_ORG_REL S_PARTY_REL
(hold relationships between account and party entities)

S_CONTACT_REL S_PARTY_REL
(hold relationships between contact and party entities)

S_PER_ORG_UNIT S_PARTY_PER
(hold relationships between account and party contact etc. or more generic it stores the ralationship between party and person)

S_ORG_INT S_ORG_EXT
(For both internal and external organization.)

S_EMP_POSTN S_PARTY_PER

S_EMPLOYEE S_CONTACT

S_POSTN_RPT_REL S_PARTY_PER

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

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

Siebel EIM – USING SYNONYMS Performance is always a major issue in most of the...

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

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

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 – 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...

Input Argument	Type	Value
Business Object Name	Literal	Account
Business Component Name	Literal	Account

Old Table (pre 7 release)	New Table (post 7 release)
S_ORG_REL	S_PARTY_REL (hold relationships between account and party entities)
S_CONTACT_REL	S_PARTY_REL (hold relationships between contact and party entities)
S_PER_ORG_UNIT	S_PARTY_PER (hold relationships between account and party contact etc. or more generic it stores the ralationship between party and person)
S_ORG_INT	S_ORG_EXT (For both internal and external organization.)
S_EMP_POSTN	S_PARTY_PER
S_EMPLOYEE	S_CONTACT
S_POSTN_RPT_REL	S_PARTY_PER