28
Oct
2009
CRUD
by Nitin JainNo, I am not referring to the Billiards game here. While browsing the Internet, I keep coming across a plethora of new technical terms everyday.
One such term I came across recently is ‘CRUD’. If you already know what it is, this post is not for you!! 
For those who don’t, CRUD is a general terminology for Create, Read, Update and Delete.
These are some of the typical operations that one performs on a set of data in a Database or any other Persistent Storage.
Creation refers to creation of new records in the Database, typically the Database Insert Operation.
Read is the reading of the records from the Database. Typically the view operations.
Update would be the usual updation of some particular data in some existing records.
Delete would mean the data is no longer available in the Database. Better be careful here!!
Question: How is this relevant to Siebel or CRM which is the current theme on GeeksBlogging@dotCOM?
Answer: Lots!
We work with CRM systems all the time. Now, that means creation of huge chunks of data. If this is an indication, Siebel CRM system houses 4500 tables in its Database! Just imagine the kind of data that would be there in the system. I recall coming across the 50-100 GB Database sizes quite frequently.
With so much of data flowing around, all the operations on every record are equally important. A small goof-up could easily mess up thousands of records, just to start with, in a very small span of time.
[Update] I also came across an interesting differentiation from Graham. Let’s talk about VBCs and EBCs in Siebel. Following is the text from Graham himself:
“.. As long as the data is only being used to read then an EBC on a view will be a good solution, it has a “short” path to the database and so will give a good level of performance. However, updating or creating records through this route will not be supported by Oracle.
If a full CRUD solution is needed then you’ll be forced into the VBC route, as you then have the control (within script or any other technology you use to implement the background logic) in order to implemented your business rules and logic so that the database integrity is maintained.
This technical solution needs backed up by a careful functional analysis though. Why do the two BCs need combined? How will updates be handled? What are the relationships? Often exploring these sort of questions uncovers that a carefuyl structuring of the view and the applets within it are all that are really needed to solve the business requirement; remember that by creating an EBC or VBC to meet the requirement you are implying an ongoing maintenance cost for the life of the implementation, an operational cost that the business will not necessarily have considered when they wrote the requirement!
.. ”
Following alternative definitions for CRUD are available on Wikipedia:
ABCD: add, browse, change, delete
ACID: add, change, inquire, delete — though this can be confused with the transactional use of the acronym ACID.
BREAD: browse, read, edit, add, delete
VADE(R): view, add, delete, edit (and restore, for systems supporting transaction processing)
QDIM: query, delete, insert, modify
SAID: show, alter, insert, delete
VEDAS: view, edit, delete, add, search
SCUD: select, create, update, delete
Related posts:
- Siebel – Automating Merge Records by script – II I call this Part II, as I have already introduced...
- Siebel – Looping Multiple Records – III Looping through multiple records is a requirement we come across...
- Siebel – Looping multiple records – Query and Process In my last post, I discussed as to how we...
- Siebel – Merge Records Functionality How many times have we realized that there are multiple...
- Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...
- Siebel – Autosave Opportunity data – The concept Requirement: System should have capability to automatically save opportunity(RFPs) data...
- Siebel – Merge Records – Checklist I call this Part III, and concluding part of a...
