Validation on Work Phone #, Work Fax are due to field Type "DTYPE_PHONE". One way to remove the validation is to chnage the type to "DTYPE_TEXT" and bring in Validation using eScripts or Validation Administration.
P.S. Formating of phone numbers will be affected by chnage of type from DTYPE_PHONE to DTYPE_TEXT.
Wednesday, June 27, 2007
Tuesday, June 19, 2007
Creating Multiple users for Local Database
Log on to local db from command prompt
dbisql55 -c UID=DBA;PWD=SQL;DBF=c:\\local\sse_data.dbf
Create Users in local
grant connect to SSE_ROLE
grant connect to MADHAVidentified by MADHAV
grant group to SSE_ROLE
grant membership in group SSE_ROLE to
Create Employee Record in Using Siebel UI for the user you have created with proper responsibility and position
*p.s. Password and User Id sud be upper case
dbisql55 -c UID=DBA;PWD=SQL;DBF=c:\
Create Users in local
grant connect to SSE_ROLE
grant connect to MADHAV
grant group to SSE_ROLE
grant membership in group SSE_ROLE to
Create Employee Record in Using Siebel UI for the user you have created with proper responsibility and position
*p.s. Password and User Id sud be upper case
Thursday, June 14, 2007
Tool - Local Database initialization - Killing it
You have started the local database extract and then at half way you feel you do not need it. You will stop the extract delete local databse.
You will try to open the tools.
Patak seee extact will restart.... Is there a solution apart from uninstalling Siebel and Reinstalling it ??
Yes !!! Search for upgrade.ucf (ucf = upgrade config file).. delete it. You are all set. Your tools will behave normal.
You will try to open the tools.
Patak seee extact will restart.... Is there a solution apart from uninstalling Siebel and Reinstalling it ??
Yes !!! Search for upgrade.ucf (ucf = upgrade config file).. delete it. You are all set. Your tools will behave normal.
Tool - Local Database initialization
When you are running the local database initialization using an upgrade wizard you can stop the local database extract half way through. When you log-on to Siebel tools the next time local database extract starts from nearest point where it had stopped.
Local Database Extract keeps loging the status of local database in state.log under Upgrade folder hierarchey. Local database extract is divided into different item.
Exmple of State.log
[Item 0]Status = Complete$TblOwner2 = SIEBELPause = 0
[Item 1]Status = CompleteItem Name = File Copy Entry 0
[Item 2]Status = CompleteItem Name = Sql File Entry 1SQL Statement Prefix = RUN_SQL_SQL Statement Number = 0SQL Statement Status = Success
[Item 3]Status = CompleteItem Name = Sql File Entry 2SQL Statement Prefix = RUN_SQL_SQL Statement Number = 5SQL Statement Status = Success
[Item 4]Status = CompleteItem Name = Sql File Entry 3
[Item 5]Status = CompleteItem Name = Sql File Entry 4SQL Statement Prefix = RUN_SQL_SQL Statement Number = 1SQL Statement Status = Success
[Item 6]Status = ErrorItem Name = Import DML Entry 5Table Name = S_BUTable Index = 118Row Index = 0Imported Row Index = 763402
[Item 7]Status = InComplete
[Item 8]Status = InComplete
[Item 9]Status = InComplete
[Item 10]Status = InComplete
Local Database Extract keeps loging the status of local database in state.log under Upgrade folder hierarchey. Local database extract is divided into different item.
Exmple of State.log
[Item 0]Status = Complete$TblOwner2 = SIEBELPause = 0
[Item 1]Status = CompleteItem Name = File Copy Entry 0
[Item 2]Status = CompleteItem Name = Sql File Entry 1SQL Statement Prefix = RUN_SQL_SQL Statement Number = 0SQL Statement Status = Success
[Item 3]Status = CompleteItem Name = Sql File Entry 2SQL Statement Prefix = RUN_SQL_SQL Statement Number = 5SQL Statement Status = Success
[Item 4]Status = CompleteItem Name = Sql File Entry 3
[Item 5]Status = CompleteItem Name = Sql File Entry 4SQL Statement Prefix = RUN_SQL_SQL Statement Number = 1SQL Statement Status = Success
[Item 6]Status = ErrorItem Name = Import DML Entry 5Table Name = S_BUTable Index = 118Row Index = 0Imported Row Index = 763402
[Item 7]Status = InComplete
[Item 8]Status = InComplete
[Item 9]Status = InComplete
[Item 10]Status = InComplete
SRF reference by Workflow Process Manager
When you connect to server via a dedicated client, and a call to Workflow process Manager is made via a Workflow Policy. Workflow Process Managers on the server will be fired and it will use the SRF on the Server not the one on your local machine.
During such situations make sure the SRF is recycled on the server too.
During such situations make sure the SRF is recycled on the server too.
Siebel - Using Sleep in eScript on a Windows Machine
SElib.dynamicLink("kernel32.dll", "Sleep", STDCALL, 2000)
STDCALL is Standerd Call
2000 is milliseconds
SElib is trys to use the windows kernal32.dlls sleep function and sleeps the execution of the code for specified milli-seconds.
STDCALL is Standerd Call
2000 is milliseconds
SElib is trys to use the windows kernal32.dlls sleep function and sleeps the execution of the code for specified milli-seconds.
Subscribe to:
Posts (Atom)