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.
It’s a very basic concept explaining how we can generate EIM mapping for custom columns. You need to follow some steps as mention in the post below.
This topic was a Tutorial Request from one of the associates on GeeksBlogging@dotCOM. The associate had asked as to how do we map the custom columns created in the BC to the EIM tables.
1. In object explorer select “Table” and query for base as well as for corresponding EIM table. For example here I am taking example of S_ORG_EXT and corresponding EIM table EIM_ACCOUNT. Lock both these tables.
In my last post, I discussed as to how we can query and update multiple records in Siebel Database. You can find it in the link below:
Siebel – Looping multiple records – Update.
Today, let’s see if there are some good ways to loop through multiple records in Siebel in Query mode, and process the data in each of the records one by one. Let’s assume the requirement statement is, “To query for these multiple records and send them to external interface one by one”.
We often come across a requirement where we need to loop through multiple records satisfying a certain search spec on a particular BC.
Let’s assume a simple search spec, for eg. to update the Status of all Sales Orders to Submitted which have their Account as “Nitin Test Account”.
SRF or the Siebel Repository File as it is more commonly known, is the binary representation of data in Siebel Tools. Siebel Application refers this file for many of the objects and data in Siebel. This greatly helps performance as the data is already available in compiled form to the runtime instance at the time of execution. On the other hand, there are many other objects or data houses in Siebel which don’t form a part of the SRF, and are compiled at runtime. And thus, are slower. For eg. Client side Business Scripts.
“Every now and then, there comes about a thought powerful enough, to make me sit straight in my chair and start hitting the keyboard!!” – Nitin Jain
I was making a fresh install of Siebel yesterday, when something very strange happened. I could not launch my Local Client. This was even more strange because:
1) I could successfully launch my Sample Client
2) I could successfully launch my Local Client when invoking it in Debug mode from within Siebel Tools!