SiebelGuide.com/siebelblogs

Siebel Blogs, News, Events, Tips and Tricks
Adding Extension Column to Siebel Table - Made Easy
Filed under All, Configuration

There are often times when we need to extend the Siebel data model. One of them is to add an extension column to the existing Siebel tables. In this blog I have listed a simplified version of steps required to add an extension column. But before you create an extension column make sure that the existing columns provided by Siebel don’t meet your requirements. You should create extension columns only if necessary. There is also a way you can avoid creating this extension column by using the columns under 1:1 extension tables. For example instead of extending the base table S_ORG_EXT you can use one of the columns available under 1:1 extension table S_ORG_EXT_X. The problem with using the extension table is that there will be a join that would be used each time S_ORG_EXT is accessed. This in turn would reduce performance. So normally developers tend to create extension column and is a very common practice. Below are the simplified steps on how to create an extension column.

For the purpose of this blog, I will take an example of adding an extension column X_OLD_ACC_NUM to the table S_ORG_EXT.

Steps:

  1. Login into Siebel Tools connecting to Local.
  2. Check out the corresponding project for which the table belongs to. For example S_ORG_EXT belongs to the project “Table Organization”. So checkout this project.
  3. Make a copy of your existing local database found at “C:\Program Files\Siebel\7.7\Tools\LOCAL\sse_data.dbf”. This will ensure a safe back up.
  4. Under table object select the table you want to add an extension column to.
  5. Expand the object explorer tree to view the table columns.
  6. Right click on the columns section and create a new record. Give a name for example X_OLD_ACC_NUM. The column will prefix with X_ even if you do not mention it. All extension columns are prefixed with X_.

  8. Mention the Physical type and Length of the column. This will depend on what you need. Enter some comments for future reference.
  9. Now you have created an object definition in Siebel tools. But this is not yet reflected onto your local database which is done in next step.
  10. Hit the Apply button. An input form pops up asking for more details.
  11. All you would need over here are four parameters.
    1. Tables: Select current Row
    2. Database User: SIEBEL
    3. Database Password: This is the user you used to extract the local DB. For example you are using JSMITH as your login and used this to extract the password will be JSIMITH.
    4. ODBC Data Source: Select the OBDC data source pointing to the local database. This would normally be SSD Local Db default instance
  12. Hit Apply on the window. This will take a while and message pops up confirming changes to the database.
  13. Now the extended column is available in the local database.
  14. Test locally and make sure the changes look fine and are as required. If you see anything is wrong and would like to roll back exit Siebel Tools and replace the backup dbf file from step 3 otherwise proceed.
  15. Check in the project.
  16. Now the object definitions are changed in the Server repository but this column is not yet available in the server database.
  17. Login into Siebel Tools connecting to Server.
  18. Lock the project under which the table belongs to. Ex: Table Organization.
  19. Find the table S_ORG_EXT and make sure that the extended column X_OLD_ACC_NUM is visible.
  20. Select the table and hit apply to have server changes reflect in the server database. Fill up required information similar to step 10. Here the login will be SIEBEL/<siebelpasswd> and the ODBC data source will be the one pointing to the server. Check your ODBC settings to figure this out. Normally applying schema changes in the server will be done by Siebel Administrator.
  21. After applying changes you should be able to see the new columns in the database. Login to the server database using your favorite SQL editor like TOAD and verify that the new column has been created and you are able to query on that. Now that column is available for use.

Make sure you test thoroughly before deployment.

As usual let me know if this blog has helped you. Post some comments.

Related posts(Auto Generated):

  1. Adding index to Siebel Table – Made Simple
  2. How to Enable Project Check Out
  3. Unlock a Project
  4. Siebel FAQs.
  5. Siebel Tools Setup for Debugging

Posted by Sridhar on Monday, May 5th, 2008


Page copy protected against web site content infringement by Copyscape
  • « Adding index to Siebel Table – Made Simple
    Oracle BI Free Web Demo »
    • You can follow any responses to this entry through the magic of "RSS 2.0" and leave a trackback from your own site.

    19 Responses to “Adding Extension Column to Siebel Table - Made Easy”

    Post A Comment

    Recent Posts 

    Recent Comments:

    • zenmed promo code: I understand that there are a lot of spam lately. Apparently it’s pretty difficult for people to...
    • Anupama: @Archana Whenever we use the UI to trigger a workflow use Runtime events. Use Workflow Policy whenever it is...
    • Judy Schreck - CDI Corporation: Systems Developer I-II/CRM Analytics Tech Lead (Oracle Siebel/OBIEE) CDI is seeking a CRM...
    • Moinuddin: Thank u very much. I am thankful to u for this valuable information.
    • remote support: i like this post greatly. ill be checking laterfor future readsthanks.

    Copyrighted © 2007 2008 SiebelGuide.com/siebelblogs. Powered by Wordpress and Blog Pixel Theme