Siebel Business Rules Administration Guide > Reference Topics for Siebel Business Rules >

Siebel Object Model Mapping to the HaleyAuthority Semantic Role Model


Siebel Object Importer generates HaleyAuthority objects and relations to represent the Siebel objects that are imported and their inherent relationships. Table 16 describes how Siebel objects and relationships are mapped to HaleyAuthority objects and relations by Siebel Object Importer.

A HaleyAuthority concept in Table 16 is represented as its position in the concepts hierarchy, where a colon separates the levels in the hierarchy. For example, assume value: date, specific day is the HaleyAuthority Concept entry for a Siebel field type. Value is a type (or child) of concept, and date, specific day is a type of value.

Table 16. Siebel Object Model to HaleyAuthority Mapping
Siebel Object
HaleyAuthority Concept
Explanation

Business Component

entity

 

Field of Type DTYPE_BOOL

value: boolean

 

Field of Type DTYPE_CLOB

 

Not mapped, and not available to choose in the Object Importer.

The length of CLOB can exceed HaleyAuthority's string limit.

Field of Type DTYPE_CURRENCY

entity: currency value

 

Field of Type DTYPE_DATE

time: period of time: specific period of time: date, specific day

and

value: date, specific day

 

Field of Type DTYPE_DATETIME

Not available to choose in the Object Importer

Not mapped, and not available to choose in the Object Importer.

DTYPE_DATETIME fields are not UTC time. HaleyAuthority stores all time as UTC time, so these fields cannot be used in predicates.

Field of Type DTYPE_ID

value: string

 

Field of Type DTYPE_INTEGER

quantity: number: decimal number: integer

and

value: number: decimal number: integer

 

Field of Type DTYPE_NOTE

value: string

 

Field of Type DTYPE_NUMBER

quantity: number: decimal number: real number

and

value: number: decimal number: real number

 

Field of Type DTYPE_PHONE

value: string

 

Field of Type DTYPE_TEXT

value: string

 

Field of Type DTYPE_TIME

time: point in time: recurrent point in time: time of day

NOTE:  A DTYPE_TIME field can be a point in time, like the time for an activity to begin, or an interval of time, like the duration of a phone call. Object Importer maps all fields of this type to the time of day concept.

 

Field of Type DTYPE_UTCDATETIME

time: point in time: instant, specific point in time

and

value: instant, specific point in time

 

Calculated Field of Type NULL

Not available to choose in the Object Importer

Object Importer imports all the currencies currently in the Master Repository into HaleyAuthority.

Currency

unit of money

 

Multi-value field (MVF)

 

Instead of modeling a multi value field as a field of its parent business component, it is instead modeled as its destination business component and the corresponding field.

For example, in the case of Primary Bill To Last Name field of Account, the Contact business component and its field Last Name are automatically imported. Concepts are created for Contact business component, primary contact, and Last Name field. Relations are created between:

contact and last name

account and contact

account and primary contact

Link

 

one-to-many relation: parent business component, child business component

One-to-Many relation.

A many-to-many relation between business components is represented as two links in Siebel. It is mapped to two relations in HaleyAuthority.

Multi-value group (MVG) link

(Traditional multi-value link with Primary Id Field property specified)

A concept is created for a kind of destination business component (the primary).

A one-to-one relation is created: root business component, concept described above.

Map only when the Primary Id property is not null, because the main purpose is to model the Primary field value.

For example, for the Bill To Contact field of the Account business component, the following concepts are created:

Concept primary bill to contact as a kind of contact entity

relation between account and primary bill to contact

Rules Runtime must determine the primary so that it can assert the data correctly.

 

MVG link

(Traditional multi-value link with Primary Id Field property unspecified)

No concepts or relations are created.

 

MVG link

(Indirect multi-value link with Primary Id Field property specified)

 

Relation: parent business component, destination business component

A concept is created for a kind of destination business component (the primary).

One-to-one relation is created: root business component, concept described above.

In this case, need to treat the indirect multi-value link as a link between this business component and the destination business component. For example, Account Issue Action business component has an indirect multi-value link Contact whose destination link is Action\Contact. The one-to-many relationship between Account Issue Action and Contact is only kept in this indirect multi-value link, and not in the destination link as with a traditional multi-value link.

MVG link

(Indirect multi-value link with Primary Id Field unspecified)

 

Relation: parent business component, destination business component

 

Siebel Business Rules Administration Guide Copyright © 2007, Oracle. All rights reserved.