Unlock Server Locked Business Component Locally (in Tools Local) using dbisqlc

You would have come across scenarios where you want to try a configuration on the business component,and unfortunately its locked on the Server. Here is the query to unlock the business component using dbislqc.

the following SQL query unlocks the 'Service Request' business component that is locked on the Server.

update siebel.S_BUSCOMP set OBJ_LOCKED_FLG='N' where NAME='Service Request';

commit;

Siebel Outbound Web Services

Extend Column of Siebel Table

Siebel 8 Task UI demo

You are considering using the ATTRIB_02 column on the S_SRV_REQ_X table and you want to determine which, if any, business component field is already using this column. What would you do?

A.Use Search Repository, select Column as the Type and enter ATTRIB_02 as the value.
B.Use the Flat tab, select the Field type, and search the Column property for ATTRIB_02 and the Join
property for S_SRV_REQ_X
C. Use the Flat tab, select the Column type, and search the Name property for ATTRIB_02.
D. Use the Types tab, search for Service* business components, inspect each of their Single Value Fields.
E. Use the Types tab, select the Service Request business component, then Single Value Field, and search the Column property for ATTRIB_02.


Highlight here for Answer: B

Best Practices: Modifying/Configuring Siebel Vanilla

• If a Siebel Vanilla field has Immediate Post Changes, Force Active or Link Specification set to TRUE DO NOT change this property as it would be used in the underlying C++ code for that BC.
  
  
• If you clone (copy) a BC consider if the BC really does need to be cloned, there is usually a lot of fields, MVL, user properties on an existing BC, is it possible to create the BC from scratch only using the Fields, MVLs, user properties that are required? This may be better performance that cloning the entire BC.
  
  
• If the cloned BC has a class other then CSSBCBase ask yourself why you are cloning the BC, if you are not requiring any specialized class functionality then change the class of the cloned BC to CSSBCBase. CSSBCBase class allows user properties (such as Named Method N) to be invoked which other BC classes can not.
  
  
• Dont inactivate or delete any standard vanilla fields - the specialized C++ code for the BC class may require these fields and could cause runtime error.
  
  
• Dont change the column or join on standard vanilla fields. The vanilla fields have been mapped to those joins/columns by siebel and may be used in the C++ code associated to the class of that BC. Also consider that Siebel have baselined and performance tested their product with the vanilla out of the box BC fields/columns. Changing the underlying columns on vanilla fields could adversely affect performance as appropriate indexes may not be used any longer.
  
  
• If you need to create a new custom extension column you are usually better off creating this on the base table (eg. S_CONTACT) rather than using the 1:1 extension table (eg. S_CONTACT_X). When updating and saving records having fields on the extension table will result in additional INSERT or UPDATE statements required for the extension table. Also we just finished a Siebel upgrade and found complications where some of the extension columns (ATTRIB_XX) were now mapped to Siebel fields in the new Siebel version. Therefore we had to re-map our existing fields on these columns.

Disable CopyRecord

Usage: Disable CopyRecord Y/N

Name: Disable CopyRecord

Value: Y

Named Method

Usage : Named Method 1:Method based on an Button on Applet

Name:  Named Method 1: BackToCart

Value: 'INVOKE', 'GotoView', '"Current Quote View (eSales)"'

Oracle Siebel Data Quality

Oracle Siebel Data Quality (SDQ) is built to accomplish two main objectives—to maintain high-quality data and to prevent bad data from entering the application. The two product modules available for performing data quality functions within the Siebel enterprise are the Oracle Siebel Data Quality Universal Connector and the Oracle Siebel Data Quality Matching Server.

Oracle Siebel Data Quality Universal Connector

The SDQ Universal Connector allows companies to leverage their existing data quality investments. It enables third-party integration with Oracle Siebel applications including Siebel Call Center, Siebel Marketing, Siebel Sales, Siebel Service, and Siebel Universal Customer Master. In addition to supporting updates in both real-time and batch mode, SDQ Universal Connector is Unicodeenabled,providing support for several languages that contain multibyte characters.With SDQ Universal Connector, organizations can leverage the capabilities of data quality vendors that best meet their needs and integrate into Siebel through a highly scalable, flexible interface that reduces the total cost of ownership of the solution.

The Siebel Data Quality Matching Server

The SDQ Matching Server identifies duplicate accounts, contacts, or prospects within the Siebel application. It employs complex algorithms and fuzzy logic that take into account common errors that occur with long names and addresses, taking into consideration variations found in certain geographic regions. By supporting multiple languages and double-byte character sets, the SDQ Matching Server allows Oracle Siebel Data Quality to be used with Oracle Siebel CRM solutions almost anywhere in the world. The SDQ Matching Server comes embedded with rebuilt matching rules that make for easy deployment, while simultaneously ensuring high accuracy. It provides prebuilt, specialized matching rules for data, and monitoring the data. Siebel Data Quality offers capabilities to address each of these functions.

Prevent Bad Data

Oracle Siebel Data Quality prevents bad data from entering the system by using fuzzy query and interactive data matching, and with list import.Oracle Siebel Data Quality enhances Siebel queries by retrieving not only accounts/contacts that are exact matches, but also potentially misspelled, phonetically similar names as well. The interactive matching is performed when a contact is being added to the database, through the user interface and/or list import. Oracle Siebel Data Quality, through the SDQ Matching Server, checks to see if the contact already exists in the database, and if it does, then it warns the user of potential duplicates through a pop up, thereby preventing the creation of a new record. For example, if a new contact called “John Jackson” was being added, Oracle Siebel Data Quality applies the matching rules and finds Jon Jackson or John A. Jackson as possible duplicates. The user can then make a decision as to whether John Jackson is an existing contact or a new contact by picking an existing account from a list or proceeding to create a new contact.

Cleanse Customer Data

Cleansing customer data ensures standardization of name and address postal formats and ensures that customer information is stored and displayed in a consistent format. This functionality is provided through bestof- breed partners who interface to Oracle Siebel Data Quality through the SDQ Universal Connector. Cleansing can be performed in real-time or in batch mode.Incoming addresses are matched against postal directories to accomplish standardization. For example, if an incoming address looks like “145 mission street south, Corex Incorporated,” it is cleansed to “145 S. Mission St., Fl. 7, Corex, Inc.”

Match/Merge Records

Siebel Data Quality provides data matching in batch mode and enables the data steward to merge information from duplicate records into one complete record. Oracle Siebel Data Quality merge offers configurable conflict resolution and updates of sparse fields by allowing the data steward to define the sequence of the merge operation. Merging also preserves relationships by re-parenting the child objects from the records being lost to the surviving record. The DUNS number and date fields are included as standard matching elements to improve match rates and to resolve questionable matches.

Key Features

• Prevents duplicate creation in the source systems through fuzzy query and interactive matching
• Provides country-specific “Quick Start Rules” for data matching
• Provides out-of-the-box “Quick Start Rules” for account, contact, and prospect data
• Standardizes names/addresses and validates addresses using postal directories through third-party tools
• Enhances customer information with data from external sources such as D&B(Dun &
Bradstreet) to ensure completeness and accuracy
• Provides central enforcement of data management rules using leading data quality tools, resulting in lower data management costs
• Allows data stewards to configure data quality rules quickly and easily through a flexible user interface
• Provides ability to track corporate data quality effectiveness such as data accuracy, data completeness, and data
uniqueness
• Supports batch mode data quality tasks for maintaining high data quality
• Provides prebuilt integration to leading data quality vendors through the Siebel Universal Connector
• Ensures suitability for mission-criticaldeployments by providing enterpriseclass performance and scalability

Siebel Repository Migration/Deployment

a) Perform a full compile to get an SRF file to be deployed. If you dont know how to do this then look it up in the Siebel Bookshelf.
b) Perform a repository export to get a repository dump file. This can be done using the repimexp tool. Here is an example of how to export the repository using repimexp:

repimexp -a e -c siebsrvr_siebel -u sadmin -p sadmin -d siebel -f c:\Siebel_Repository.dat -l c:\Siebel_Repository_Export.log

Where:

-a - this is e for export
-c - is the odbc source
-u and -p - these are the credentials for the sadmin user
-f - this is the siebel repository export file
-l - this is the log file

The deployment process is outlined as such:

1. Stop the Siebel Servers.
2. In Siebel Tools, rename the current Siebel Repository to another name. In the Object Explorer go to Repository and rename the current Siebel Repository to something like: Siebel Repository Pre v1.1. The current repository needs to be renamed so that you can import the new repository with the name: Siebel Repository.
3. Import the repository using the repimexp tool. Here is an example of how to import the repository using repimexp:

repimexp -a i -g ALL -c siebsrvr_siebelsystest -u sadmin -p sadmin -d siebel -r "Siebel Repository" -H 2000 -f c:\Siebel_Repository.dat -l c:\Siebel_Repository_Import.log

4. Perform a DDLSYNC to apply database level DDL operations to be in sync with the new repository. To do this run the following commands in order:

ddldict -u sadmin -p sadmin -c siebsrvr_siebelsystest -d siebel -f ../schema.ddl -e y -a y -l ../DDLDICT.log -n "Siebel Repository" -T DCIR

ddlimp -u siebel -p siebel -c siebsrvr_siebelsystest -g SSE_ROLE -f ../schema.ddl -e n -B SIEB_TBLSPC -X SIEB_INDX -R Y -s Y -l ../ddlsync1.log

ddlimp -u siebel -p siebel -c siebsrvr_siebelsystest -g SSE_ROLE -f ../schema.ddl -e y -B SIEB_TBLSPC -X SIEB_INDX -R Y -s Y -l ../ddlsync2.log

5. Deploy files to the Siebel Servers. These files include the SRF, web templates, image files, configuration files, etc.

6. Generate browser scripts using genbscript. Something like this if you navigate to the bin directory on the siebel servers:

genbscript ./siebel.cfg ../webmaster

6. Start up the Siebel Servers.

7. Activate any new or updated workflows in the Administration - Business Process > Workflow Deployment view.

8. Compile any new or updated PLSQL procedures or packages.

9. Deploy master data changes. This would include any changes required to LOVS, runtime events, state models, assessment templates, etc. All master data changes.

10. Restart the Siebel Servers.

11. (Optionally) Execute any data updates through EIM and/or business service. If these data updates are quite large involving changes to a lot of data then you would most likely want to regenerate the database statistics through consultation with a DBA.

How Do You Send Email via Siebel Scripting or Object Interfaces Using Outbound Communication Manager?

The Communications Outbound Manager processes outbound communications, for email, fax, wireless message, or page channels. It also supports outbound capabilities for Siebel Email Response and for the Send Email, Send Fax, and Send Wireless Message commands.

Here is the eScript sample code:

//instantiate the business service and the propertysets

var bs = TheApplication().GetService("Outbound Communications Manager");

var inputs = TheApplication().NewPropertySet();

var outputs = TheApplication().NewPropertySet();

//Communication profile to be used - must be a current profile defined in the application

var CommProfile = "MyProfile";

var MsgToList = "siebelsupport@blogspot.com";

var MsgBody = "Hello testing hello! How are you today?";

var MsgSubject = "Testing Message";

//Where C:\ on the Siebel Server or the Siebel Client file system?

//Or where in a remote client?

var AttachFileList = "c:\\test.txt";

inputs.SetProperty("CommProfile",CommProfile);

//for web client use 'Remote' instead of 'Local'

inputs.SetProperty("ProcessMode","Local");

inputs.SetProperty("MsgToList",MsgToList);

inputs.SetProperty("MsgBody",MsgBody);

inputs.SetProperty("MsgSubject",MsgSubject); inputs.SetProperty("AttachFileList",AttachFileList);    bs.InvokeMethod("SendMessage",inputs,outputs);

inputs = null;

outputs = null;
bs=null;

//----end