Table 3. Terminology
Term
|
Description
|
Metadata
|
Data that describes data. For example, the term datatype describes data elements such as char, int, Boolean, time, date, and float.
|
Siebel business object
|
A Siebel object type that creates a logical business model using links to tie together a set of interrelated business components. The links provide the one-to-many relationships that govern how the business components interrelate in this business object.
|
Component
|
A constituent part of any generic object.
|
Siebel business component
|
A Siebel object type that defines a logical representation of columns in one or more database tables. A business component collects columns from the business component's base table, its extension tables, and its joined tables into a single structure. Business components provide a layer of abstraction over tables. Applets in Siebel applications reference business components; they do not directly reference the underlying tables.
|
Field
|
A generic reference to a data structure that can contain one data element.
|
Siebel integration component field
|
A data structure that can contain one data element in a Siebel integration component.
|
Siebel integration component
|
A constituent part of a Siebel integration object.
|
Integration object
|
An integration object of any type, including the Siebel integration object, the SAP BAPI integration object, and the SAP IDOC integration objects.
|
Integration object instance
|
Actual data, usually the result of a query or other operation, which is passed from one business service to another, that is structurally modeled on a Siebel integration object.
|
Siebel integration object
|
An object stored in the Siebel repository that represents some Siebel business object.
|
Integration message
|
A bundle of data consisting of two major parts: header information that describes what should be done with or to the message itself, and instances of integration objects, that is, data in the structure of the integration object.
|
