Upgrading and Migrating Siebel Janna Applications > Interoperability Case Study > Transaction Zone—Implementation Details >

Determining the Siebel Janna Data Object Key Field Names

Some of the properties of the Siebel Janna Data Object will be Key Fields that act as foreign keys to other tables or as a primary key for the table the Siebel Janna Data Object maintains. There are a few ways to determine which properties of the Siebel Janna Data Object represent these key fields. Consult the Siebel Janna Tools, the extension technical documentation, or client extension technical documentation for the names of the key fields on each Siebel Janna Data Object.

In the absence of the appropriate technical documentation, there are still methods to determine which fields are key fields. The first, and most accessible, is to examine the database table or view for foreign key constraints and uniqueness constraints. The columns attributed with these kinds of rules are key fields.

Without access to the database schema, the next reliable method to determine the key fields on a Siebel Janna Data Object is by examining its corresponding Siebel Janna Service Object source code and the client source code for the Siebel Janna Service Object and Siebel Janna Data Object pair.

Finally, if the source is not available, and the database schema cannot be examined, then most often Siebel Janna Data Object properties that contain GUID values represent primary keys and foreign keys on a Siebel Janna Data Object.

The following field names must be present: ContactGUID (FK—UserProf), EditUserGUID (FK—UserProf), ViewUserGUID (FK—UserProf), GUID (PK), and Ticker (FK—Ticker Data).


 Upgrading and Migrating Siebel Janna Applications
 Published: 18 April 2003