From time to time and for various reasons, we must be able to identify a record in a Siebel database as either belonging to the ever-growing set of Siebel seed data or as having been created by the customer.
Probably the easiest way to identify a record as seed data is to use the ROW_ID value. For example, let's go to the Product Administration view and run a query such as the following.
If you - for whatever reason - use URL-based authentication to load Siebel CRM application content in a browser or iframe then you should strongly consider reading Oracle Support Document 1496603.1 (Removing URL-Based Authentication in Siebel CRM).
After discussing the features and options of the elusive dataexp command line utility, we today talk about dataimp, which obviously serves in the reverse process of importing data from a flat file into Siebel tables.
Before we begin, let's reiterate the words of caution from our last article:
Sometimes I am overwhelmed by feeling totally privileged of working with so many brilliant people. Last week, fellow book author and Oraclean Duncan Ford published the Siebel Open UI Code Template Generator.
Here at Siebel Essentials, we are always on the watch for interesting developments around Siebel CRM. A few weeks ago, a new company - Siebel Private Cloud - appeared on the internet. They offer Siebel CRM in the cloud, ranging from sandboxes to full production scale deployments without the hassle of installing, maintaining and securing a Siebel server environment.
We have come a long way from Siebel Analytic Applications, the grandfather of OBI Apps to Oracle BI Apps 11g. The former became Oracle BI Apps 7.9.x and - as most of my readers will be aware - uses Informatica products for ETL.
When it comes to getting data out of and into a Siebel database, usually the first tools that come to mind are Siebel EAI business services like EAI Siebel Adapter or Enterprise Integration Manager (EIM). While EIM and EAI provide the richest functionality and are popular for good reason, sometimes we just need to transport some records in a table from one Siebel database to the other.
Such scenarios are often found when it comes to working with non-production environments, such as test instances where we quickly want to establish test records and the like.