Applies to:
Error Message Area:Data Manager - DATVersion:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00278: The ability to delete records is not available in this screen or applet.
Scope
This document is informational and intended for any user.
SBL-DAT-00278: The ability to delete records is not available in this screen or applet.
Explanation
1. The No Delete property may be set to TRUE for one of the following repository objects; business component, applet, MVL, Link.2. The record may be set to read-only by the business component user properties.
3. For business components that have the state model activated, the No Delete parameter may be set to TRUE for the corresponding State Model under Administration - Application > State Models > States.
Corrective Action
1. Confirm or set the No Delete to FALSE for the following repository objects; business component, applet, MVL, Link. Test whether this suppresses the error message.2. Deactivate the business component user properties especially those described in Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Configuring Business Components > Configuring Data-Driven Read-Only Behavior. For more information on user properties, refer to Siebel Bookshelf version 7.7 > Siebel Developer's Reference.
3. Set the No Delete parameter to FALSE for the respective State Model and test whether this suppresses the error message.
Refer to FAQ 1305 for details on how to enable a Business Component for State Model functionality.
Applies to:
Product Release: V7 (Enterprise)Version: 7.8.2.3 [19221] Life Sci
Database: Oracle 10.2.0.1
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1
This document was previously published as Siebel SR 38-3233398641.
Symptoms
SBL-DAT-00278, SBL-DAT-00498In the application administration -- > Smart Calls, when a new smart call record is created,
all the fields became read-only immediately, preventing the data input. Therefore, Smart call
record could not be saved. When we tried to undo the record, an error message was displayed:
-
- -
The ability to delete records is not available in this screen or
applet.(SBL-DAT-00278)
- - -
So we are left with no option but to kill the application.
This error occurs only in our DEV server. The same doesn't happen in local db or in another
environment. We used the same srf in all the 3 environments.
We found the same problem
being discussed in another SR (# 38-941920856).
I tried with the following:
1. As
per SR 38-941920856, in the DEV server, I checked the LOV type EVENT_STATUS and checked for the
value "Submitted" and it is present already.
2. I applied the vanilla srf in the DEV server
and tried to create a smart call, but still the same error occurred.
3. I copied the DEV
server srf into my local and tried to create a smart call. This works fine.
Note: Some
Organization records were deleted.
Solution
Message 1
For the benefit of other readers:# Issue:
In the application administration -- > Smart Calls, when a new smart call record is created, all the fields became read-only immediately, preventing the data input. Therefore, Smart call record could not be saved. When we tried to undo the record, an error message was displayed:
- - -
The ability to delete records is not available in this screen or applet.(SBL-DAT-00278)
- - -
So we are left with no option but to kill the application. This error occurs only in our DEV server. The same doesn't happen in local db or in another environment. We used the same srf in all the 3 environments.
We found the same problem being discussed in another SR (# 38-941920856).
I tried with the following:
1. As per SR 38-941920856, in the DEV server, I checked the LOV type EVENT_STATUS and checked for the value "Submitted" and it is present already.
2. I applied the vanilla srf in the DEV server and tried to create a smart call, but still the same error occurred.
3. I copied the DEV server srf into my local and tried to create a smart call. This works fine.
# Solution:
In posting 38-941920856 on SupportWeb the cause of the issue is a missing LOV value with Type = EVENT_STATUS and Language Independent Code = Submitted.
[...]
Message 2
[...]Please note that there are other specific values that absolutely need to exist and be active in the EVENT_STATUS LOV. This matter is discussed in posting 38-1070652371 on SupportWeb where it is mentioned that the following values should not be inactivated:
1. Done
2. Not Started
3. Cancelled
4. In Progress
7. Scheduled
8. Assigned
9. Unassigned
10. Accepted
11. Unscheduled
12. Submitted
13. Auto-Created
14. Planned
15. Booked
16. Synchronized
17. Billed
18. Open
NOTE: Documentation Enhancement Request 12-HU4CWP was logged to include a complete list in the Bookshelf.
The customer found that the "Synchronized" value was inactive in their DEV environment. The issue was resolved once this value was made active.
Silvere Torre
Oracle Technical Support
Applies to:
Siebel Tools - Version: 8.0.0.3 [20416] - Release: V8Information in this document applies to any platform.
Symptoms
We get this error when deleting revenue records from Revenue BC.--
Error running ANS 'Opportunity Renewal BS' workflow, with the following errors: Error setting opportunity values: The ability to delete records is not available in this screen or applet.(SBL-DAT-00278)(SBL-EXL-00151) Error setting opportunity values: The ability to delete records is not available in this screen or applet.(SBL-DAT-00278)(SBL-EXL-00151)(SBL-EXL-00151)
The error is not occuring on the UI.
We have a business service script that copies Opportunities.
When it copies the opportunities, it copies revenue records with it because Deep Copy User property. But we do not want the revenue records copied. So once it is copied we are trying to delete the revenue records and that is not allowed and we got the above error message.
Cause
=== ODM Cause Determination ===There was a revenue record always created with summary flag = 'Y'. The sales rep position for this record was not the SADMIN that customer was logging in to delete.
As the owner delete property was set on the revenue record, it never could delete this record.
Solution
For benefit of other readers:After customer query for the revenue records to delete, customer adds another search spec Summary = "N".
This search spec eliminated the summary record and the script was able to proceed further and delete the other revenue records.
Thank you,
Oracle Siebel CRM Support
No comments:
Post a Comment