Applies to:
Product Release: V7 (Enterprise)Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server
This document was previously published as Siebel SR 38-1507541094.
Symptoms
SBL-DAT-00368Hello,
we are unable to delete position through the UI.
using either:
- our
custom srf against our oracle db
- the 7.7.1 vanilla srf against our oracle db
- the 7.7.0
vanilla srf against a 7.7.0 sample db (on a test upgrade machine we kept)
Can you please
help?
Kindly find attached a log of the error we experience.
Thanks.
Solution
Message 1
For the benefit of others:The customer was unable to delete a position through the Siebel application UI.
When trying to delete the position, they were getting the error:
“[1] An error occurred while deleting the record
Please try to delete again (SBL-DAT-00236)
[2] Column “” not defined in table ‘<?>.(SBL-DAT-00368)”
This issue could be reproduced against the standard application and the Change Request # 12-OY8PZR has been logged to address this issue.
Also as mentioned in the Security Guide for Siebel eBusiness Applications > Configuring Access Control > Planning for Access Control > Planning for Positions, we do not recommend deleting positions.
This is an excerpt from the Security Guide:
"CAUTION: Do not delete a position. This can cause unexpected and negative results. For example, if you delete a position that is primary for an account, and you do not select a new primary position for that account, Assignment Manager may not be able to assign resources to activities for that account. "
Please review the Security Guide for Siebel eBusiness Applications for additional information.
Enhancement Request #12-OZ290E has been logged to request disabling the delete button on the Position List Applet since we do not recommend deleting positions.
Keywords – delete, position, error, disable, button
Applies to:
Siebel Tools - Version: 7.8.2 [19213]z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 9.2.0.0
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 5.6
This document was previously published as Siebel SR 38-3133574891.
Symptoms
The issue is that Accounts cannot be deleted.The user will select Delete from the menu, Ctl-Alt-D, or clicked the Button, everything seems to work fine until the user steps off the record. Once the user steps off the record, a message pops up:
--------------------------------------------------------------------------
[1] An error has occurred while deleting this record.
Please try to Delete again (SBL-DAT-00236)
[2] Column "not defined in table '<?>' (SBL-DAT-00368)
--------------------------------------------------------------------------
Cause
"Organization Id" field in Service Agreement business component has a wrong configuration as follows;Multi Valued : FALSE
Multi Value Link : Organization
Column : null
Since "Organization Id" field is a MVF, Multi Valued property has to be TRUE.
Solution
Set Multi Valued property of "Organization Id" field to TRUE and the end user can delete account records with no problem.Applies to:
Siebel Tools, SPE - Version: 8.0.0.5 SIA [20420] - Release: V8Information in this document applies to any platform.
Symptoms
After upgrade from 7.5.3.15 Siebel application to version 8.0.0.5 in a development environment, the following error message appears when trying to access some customised views and applets within the “Batch Administrion” screen
SBL-DAT-00368: Column 'LANG_ID' not defined in table 'CX_INTGR_REF'.
Cause
Oracle consultant, working on-site found the issue arises because the 'Translation Table Name' property for some of the columns have been set to 'CX_INTGR_REF'.
The property is not needed as the columns are not MLOV enabled.
Solution
Proposed solution:
Remove the value from table user property 'Translation Table Name' or set it to S_LST_OF_VAL or null as BookShelf recommends.
BookShelf reference Siebel Object Types Reference > Siebel Object Types > Column, Translation Table Name property allowed values are S_LST_OF_VAL and NULL.
Setting this property to S_LST_OF_VAL will not cause any error as this table does have a LANG_ID column.
Enhancement request 12-1RRC6RV has beed raised to avoid the check of 'Translation Table Name' when LOV Type is null and LOV Bounded set to FALSE.
In general, when an enhancement request is logged, it is reviewed, prioritized, and may be fixed in a future release.
No comments:
Post a Comment