Siebel EIM – Nomenclature of Custom Column
by Himanshu BajpaiPrevious 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 – Left, Right and from the Middle Extracting a sub string from a lengthy string in Siebel....
- Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...